ePMP Release 3.2.2 is now available

Hello all! Found little bug: after firmware update "from box" to 3.2.2 release and reboot - i do restore configuration from previous saved txt-format (*.json) file, then save and reboot. But after reboot i see empty Prefered APs table on my Force 180 device (a config file contain this section with my AP), other data in normal. A 3.2.1 release don't have this problem.

Im getting this bellow when trying to loging while upgrading AP w GPS

Maximum number of users reached


@Spookie wrote:

I upgraded a ePMP 1000 AP module  to this version along with its Subscriber modules

and noticed that the statistics numbers are frozen in time until a clear the counters then they are stuck again.

is this a known bug with the APs  ?

SM Modules appear to be fine and working as expected.


Hi,

Thank you for your feedback.

We will check it.

Will keep you updated.

Thank you.


@FASINFO wrote:

Hello all! Found little bug: after firmware update "from box" to 3.2.2 release and reboot - i do restore configuration from previous saved txt-format (*.json) file, then save and reboot. But after reboot i see empty Prefered APs table on my Force 180 device (a config file contain this section with my AP), other data in normal. A 3.2.1 release don't have this problem.


Hi FASINFO,

Sounds like a defect.

Will check it.

Thank you for reporting this.

Thank you.




@Spookie wrote:

I upgraded a ePMP 1000 AP module  to this version along with its Subscriber modules

and noticed that the statistics numbers are frozen in time until a clear the counters then they are stuck again.

is this a known bug with the APs  ?

SM Modules appear to be fine and working as expected.


Hi,

We cannot reproduce described issue in our Lab.

Could you please tell whether issue is reproducible only with one particular device or with every ePMP device?

Thank you.

I have since downgraded the devices back to 2.6.2.1 and the issue is gone.

Still getting DFS hits on numerous AP's in various locations using 3.2.2. Rolling back to 2.6.2.1 eliminates the issues.

Hi,

Ever since version 3.x came out, we have had lots of issues with not being able to login through the GUI to GPS APs.  We keep trying with each new iteration and same results.

We have called support and they keep saying next version, next version.

as of 3.2.2, the issue still remains.  I have to wonder how are people actually using these later versions?  We wanted to install Elevate and test, but that is on hold also.

I understand things happen, but this been more than a couple months on this issue.

Any update?

Paul

Hi,

SNMP daemon issue has been found in 3.2 and 3.2.1 Releaes.

In 3.2.2 reproducibility rate was significantly reduced and not all customers are affected with 3.2.2 Release now.

We appologize if you still see this issue in your network with 3.2.2 Release.

It is supposed to be totally fixed in 3.3 Release.

We are going to deliver 3.3 Beta release in the nearest future.

And we would be really appreciate it if you could to participate in Beta program and verify whether issue will not be reproducible with 3.3 Beta release.

Thank you.

When restoring a backup config the following error is received.

cambiumSYSAccountsHash:

error: Password hash contains illegal chars

When I manually edit the config file and take out the illegal charters it will then take it but not allow me into the unit with with the admin account.

Hi Now,

It is known issue in 3.2.2 release. It was discussed in another topic.
Issue appears when you are trying to restore configuration file with disabled user account(admin, installer, home or readonly).
It is already fixed in 3.3 Release.

Thank you.

I will have to upgrade about 100 cpe. What 's the fastest way without using the web interface of each of them?

You can use management systems - cnMaestro, CNUT or CNS.

Thank you.

Thanks, I'll try to use cnut.

Few bugs:

1) At the bridge table, you can not mark and copy the MAC address.

2) If you skip by a tab key into a field and quickly fill gateway or IP address. The field is cleared.

3) When you enter preferred AP and/or password pressing an enter key is need for each field, otherwise it is reported as an error. Cannot confirm by the mouse.

1 Like

@Pavel wrote:

Few bugs:

1) At the bridge table, you can not mark and copy the MAC address.

2) If you skip by a tab key into a field and quickly fill gateway or IP address. The field is cleared.

3) When you enter preferred AP and/or password pressing an enter key is need for each field, otherwise it is reported as an error. Cannot confirm by the mouse.


Hi Pavel,

1. I can assume it depends on browser you are using.

I've checked with Chromium and it works well.

2. It is known issue and it will be fixed as soon as possible.

3. You just need to click somewhere outside the field you are entering.

We will take a look how we can improve usability fir this.

Thank you for your feedback.

Thank you.

1 Like

Using Radius on Wireless Security, and choosing on "GUI User Authentication" option "Remote RADIUS Server and Fallback to Local".

When try to loggin to AP, it success. You can loggin with radius user. But, when try to loggin to SM registered with user in radius, who try request authentication to Radius Server is SM, not the AP. And the Radius Server rejects because it tries from unknown client NAS.

With Canopy PMP it works as expeted.

Maybe its a bug in the GUI User Authentication when using Radius on the SM ?

Hi Roberto,

ePMP uses User-Name and User-Password parameters from RADIUS server for GUI Authentication.

I am sorry if I didn't understand you description correctly and I would be grateful if you could specify your issue.

Thank you.

Hi Fedor,

The Radius Server is correctly configured, as we use it with PMP, and now it works also for ePMP AP. But when we try to loggin to a SM, fails because Radius Server receives the authentication directly from the SM, not from the AP. The AP is a valid NAS on the Radius Server, but SM not because it's unusable putting all new SM as a NAS on Radius.

On PMP, when you loggin to a SM, Radius Server receives the authentication request from the AP, not from the SM.

Sorry if I not explain correctly in english.

Thanks.

1 Like

Thank you for explanation, Roberto.

Today this functionality operates in way you have described.

But we have already opened improvement to implement same with PMP solution.

Hope it will be delivered in next releases.

Thank you.