ePMP Release 4.3.2.1 is now available

ePMP Release 4.3.2.1 is now available
 

 

ePMP Release 4.3.2.1 is now available at https://support.cambiumnetworks.com/files/epmp/

Any update on when QoS/MIR will be available?

ACG-5855 - DFS channels are now available on the ePMP3000 AP, but not yet on the Force 300.  Any idea when that may come through?

Thanks,

A note on ePMP1000's, eDetect is now causing the SM to drop off the panel during the scan

Performance appears to have completely tanked on my test sector with this latest update.  I'll revert to the prior beta I was running to confirm.

Running 4.3.2-RC15 performance is back to where it was before (not exceptional, but totally usable).  Nothing else has changed.

Another item of note - Running 4.3.2-RC15 the AP will request a DHCP lease using the ethernet mac address.  On 4.3.2.1 the DHCP request comes from the wireless mac address on the AP.


@MBSI WAV - Ryan wrote:

Any update on when QoS/MIR will be available?


QoS for PTP and MIR is supposed to me introduced in scope of 4.4 FW.

Thank you.


@Jacob Turner wrote:

Running 4.3.2-RC15 performance is back to where it was before (not exceptional, but totally usable).  Nothing else has changed.

Another item of note - Running 4.3.2-RC15 the AP will request a DHCP lease using the ethernet mac address.  On 4.3.2.1 the DHCP request comes from the wireless mac address on the AP.


Jacob,

Thank you for your feedback.

Could you please provide more details regarding perormance 4.3.2-RC15 vs 4.3.2.1?

Thank you.

Fedor, my testing hasn't been the most scientific, but 4.3.2.1 produces about 1/3 the throughput on my test link of 4.3.2-RC15, and jitter and packet loss are notably worse.   The environment I'm testing in is rather noisy in the available bands (no DFS bands yet), the ambient noise floor is about -75 with peaks into the -50 range across the band.

In this specific case, 3000 is performing about identical to 1000 gear.   I can test more methodically over the weekend.  Once DFS bands are available I can actually test apples-apples with the UBNT AC and Mimosa gear at the same location.

Thanks,


@Jacob Turner wrote:

Another item of note - Running 4.3.2-RC15 the AP will request a DHCP lease using the ethernet mac address.  On 4.3.2.1 the DHCP request comes from the wireless mac address on the AP.


What ePMP devices has been tested?

ePMP always sends DHCP requests from Wireless Mac address.

We test 4.3.2.1 and 4.3.2-RC15 with ePMP2000 and it works as expected.

Thank you.

The 3000 AP always requests a dhcp lease on the ethernet mac on the RC firmware, and the wireless mac on 4.3.2.1.

I'm happy to report that I've been able to move frequencies around at my testing site and while things are still noisy, I'm seeing much better results than before.

8285872244

This is pretty typical on the new cleaner channel.  This is a 20Mhz channel BTW.  The only issues I've had since making the cleaner channel available are backhaul related.  A 300Mbps backhaul link isn't enough for this site anymore.

2 Likes

Upgraded last night and had strange problems during the day. 

Using ePMP 2000 sectors and Forse 180 CPE's.

Both sector and CPE have errors come up when logged in to gui of connection loss aprox every 30 seconds. CPE's also ar enot detecting the internet connection. All CPE's obtain IP via PPPoE from main router, have tried changing DNS server settings but still the same.

Clients have complained of loss of connection for periods of time.

Will be revertingback to 3.5.6 tonight.

1 Like

I work for a small WISP and we have ePMP2000 sectors and mixed SM's with Force 190 and PowerBeamM5 running elevate software. I did a test with upgrading one AP and all the SM's to 4.3.2.1, but encountered strange issues. All the clients except one (randomly chosen most likely) have been disconnected from AP at some point. Every time AP reboot brought them back online, but since this started to happen 3-4 times a day, we decided to go back to 3.5.6.

The other thing i noticed is when the AP was running 4.3.2.1 and SM's any firmware before that, download RSSI readings for all the SM's from sector were at -88, but E-align from SM was showing the value the radio had before this upgrade. After I downgraded AP firmware, RSSI readings were back to correct ones. GPS firmware was updated the same moment as the sector. When SM's got updated to 4.3.2.1, sector (running 4.3.2.1) had correct readings again. 

So far, i am not impressed, as it caused me more problems than benefits, so i would pass this version for now.

Another weird bug seems to have gotten introduced. We have one AP on 4.3.2.1, the rest on 3.5.6. The 4.3.2.1 device reports, when I use my choice of browser with its native identity string,

Browser not supported. Please use the latest version of Chrome, FireFox, Safari, Edge or Internet Explorer. Your current version number is "undefined undefined", minimum expected version - "undefined N/A".

It works when I tell the browser to disguise itself as Firefox. No, it is not a browser you've heard of, but it is highly standards-compliant. There is no reason for a product to enforce an oligopoly on browsers by demanding that a known browser be used. If it doesn't know what the browser is, it should continue to default to standard HTML. 3.5.6 works just fine on an unknown but compliant browser; 4.3.2.1 broke it for no reason, and I don't think it was documented.  Hence it's a bug, not a feature.

Oh, and as I mentioned elsewhere, it no longer reports in Monitor Radio the SM's received RSSI where it should; it instead seems to put the previous SNR there. So I don't know from the monitor tab what RSSI the SM is getting. cnMaestro does get the right value.

Hey man, would you have a file for the frimware 4.3.2.1 or if I could download it? The company I help out with thier clients always have problems with thier antennas. And the company won't send me an attachment or anything for that. Would be useful if I had the file with me so I can help out my community with thier disconnection issues.

Older firmware is available in the Cambium support portal under ePMP -> Previous ePMP Files -> Archive.

I would not recommend using the 4.3.2.1 firmware. I had strange issues with it, and since there is already newer, improved firmware 4.4, I would go with that one.