ePMP Release 4.6 is now available

:warning: Please see this post about a known problem with release 4.6

ePMP Release 4.6

Supported Platforms:

  • ePMP 11n and ePMP 11ac families
  • Elevated XM and XM

Sofware can be downloaded at: https://support.cambiumnetworks.com/files.

Changes in Release 4.6

  • ACG-7308: Fixed an issue for when an SM is not able to connect to an ePMP 1000/2000 Access Point with the reason “INA Retries exhausted” if there are Force 300 Subscriber Modules connected to the same Access Point.
  • ACG-7704: Fixed an issue for when Port Forwarding doesn’t work on the Separate Management interface on Force 300 Subscriber Modules.
  • ACG-7841 / ACG-8514: This release provides general stability and performance improvements for the PTP 550 model.
  • ACG-10107: Fixed an issue for when throughput degradation occurs in the ePTP mode using the ping tool.
  • ACG-10121: Fixed an issue for when Spectrum Analyzer displays error messages such as “Spectral Tools: Socket cannot be created” and “Spectral Tools: General error” post radio configuration changes.
  • ACG-10131: Fixed an issue for when ACS cannot be enabled through SNMP.
  • ACG-10159: Fixed an issue for when the PTP 550 radio disconnects in Channel Bonding mode.
  • ACG-10225: Fixed an issue for when the Smart Antenna status is displayed as “Disconnected/Power Off” when “Forced Sector” is selected on an ePMP 3000 radio.
  • ACG-10352: This release provides general stability improvements for 802.11ac Access Points operating in backward compatibility mode.
  • ACG-10398: Fixed an issue for when the Force 300-13L occasionally starts to operate with lower power than configured.
  • ACG-10416: Fixed an issue for when the Total Frame Time used is displayed incorrectly in the User Interface.
  • ACG-10431: Fixed an issue for when a software upgrade is not possible on rare occasions.
  • ACG-10487: Fixed an issue for when a Subscriber Module is not able to pass the traffic on rare occasions when the Membership VLAN setting is enabled.
  • ACG-10601: This release provides general stability improvements for the Force 300-13L Subscriber Module.
  • ACG-10639: Fixed an issue for when the User Interface does not show the Spectrum Analyzer output on the ePMP 3000MP and the Force 300-13L models.
  • ACG-10645: Fixed an issue for when crash happening in Backward Compatibility mode with the signature “camb_sn_tx_complete”.
  • ACG-10651: Fixed an issue for when it takes a long time to display the login page after an upgrade is performed on the Force 300-13L Subscriber Module.
  • ACG-10654: Fixed an issue for when a Subscriber Module’s LAN DHCP address is assigned to another Subscriber Module’s Separate Wireless Management Interface.
  • ACG-10683: Fixed an issue for when the Master occasionally switches to a channel out of the configured pool of DCS channels.
  • ACG-10714: The fix for the issue when it’s not possible to download the Tech Support file when the Spectrum Analyzer is enabled.
  • ACG-10724: Fixed an issue for when the login page displays a blank page after selecting a different language than the default one from the User Interface.
  • ACG-10726: Fixed an issue for when the Force 300 radio reboots spontaneously on rare occasions.
  • ACG-10746: Fixed an issue for when PTP 550 takes too long to start under a low temperature.
  • ACG-10754: Fixed an issue for when the grace period of Flexible Licensing is skipped when the AP is re-configured.
  • ACG-10798: Fixed an issue for when the Watchdog feature doesn’t work correctly.
  • ACG-10856: Fixed an issue for when Access Points drop all Subscriber Modules with GPFs MISS disconnect reason on the Subscriber Modules, and the COMMUNICATION LOST message on the Access Point, and Subscriber Modules are not able to re- connect until the Access Point is rebooted.
  • ACG-10859: This release provides GPS sync stability improvements.
  • ACG-10865: Fixed an issue for when the Flexible License configuration section is not displayed on the ePMP 3000MP Graphical User Interface.
  • ACG-10868: Fixed an issue for when packets with the same MAC addresses originate from Wireless and Ethernet sides.
  • ACG-10870: Fixed an issue for when the Anonymous Crash Reports pop-up message displays for the home/readonly users.
  • ACG-10908: Fixed an issue for when the power configuration on “Radio 1” causes a disconnect of “Radio 2” and isn’t able to re-establish the connection for the PTP 550 radio.
  • ACG-10949: This release provides stability improvements for disconnects.
  • ACG-10982: This release supports the updated New Zealand regulatory rules.
  • ACG-10984: The Force 300CSM now supports the FCC 4.95-4.98 GHz band ranges.
  • ACG-10986: Fixed an issue for when the Device Wireless MAC Address isn’t reflected on the Dashboard in the Graphical User Interface.
  • ACG-10970: Fixed an issue for when Force 300-13L configured as NAT/PPPoE does not try to re-establish PPPoE session after firmware upgrade.
  • ACG-11055: Fixed an issue for when the PTP 550 Radio 2 Wireless MAC address is not displayed on the Dashboard in the Graphical User Interface.
  • ACG-11098: Fixed an issue for when the ePMP 3000 MP’s Spectrum Analyzer does not display any information after the scanning is completed.
  • CAMBIUM-14552: Fixed an issue for when the IP address isn’t validated while updating the Port Forwarding table.
  • CAMBIUM-16139: Fixed an issue for when the Subscriber Module disconnects while applying changes to the Mac Filtering Table, the Tx Power, and the Transmit Receive Level parameters.
  • CAMBIUM-17139: Fixed an issue for when the user password resets to the default value after a device reboot.
  • CAMBIUM-17151: Fixed an issue for when an Elevated Mikrotik radio crashes during the software upgrade process.
  • CAMBIUM-17163: Fixed an issue for when the Elevate XM Bullet M5 isn’t able to connect with the ePMP 3000 Access Point.
  • CAMBIUM-17164: Fixed an issue for when the Elevated radios with single spatial streams are trying to operate on dual stream MCSs.
  • CAMBIUM-17217: Fixed an issue for when the multicast traffic doesn’t pass the bridge in downlink when the Management and Data VLAN settings are enabled.
  • CAMBIUM-17227: Fixed an issue for when the Subscriber Modules’s IP address on the Monitoring Wireless page on an Access Point displays 0.0.0.0.
  • CAMBIUM-17235: Fixed an issue for when it’s not possible to switch from Bridge to NAT mode due to invalid Parameters Validation on a Subscriber Module.
  • CAMBIUM-17243: Fixed an issue for when a Force 130 crashes during a software upgrade.
  • CAMBIUM-17254: Fixed an issue for when Link Capacity and Link Quality always display 0% in ePTP mode.
  • CAMBIUM-17303: Fixed an issue for when a user is not able to enable the GUI RADIUS Authentication setting on Access Points and Subscriber Modules when the WPA2 security method is enabled on the Access Point.
  • CAMBIUM-17313: This release supports a new OUI range BC:E6:7C:xx:xx:xx support for the Force 190 radio model.
  • CAMBIUM-17353: Fixed an issue for when an incorrect validation pop-up message appears for the parameters which were originally disabled on the User Interface.
  • CAMBIUM-17376: Fixed an issue for the severity of alarms that are sent by the Smart Antenna to cnMaestro.
  • CAMBIUM-17394: Fixed an issue for when an Elevate XM upgrade fails with the error message: "Executing Pre-Update CleanUp script was failed. Please try again. ".
  • CAMBIUM-17448: Fixed an issue for when the radio does not send the trap message during a soft reboot.
  • CAMBIUM-17457: Fixed an issue for when the Force 130 doesn’t allow to select any Port Speed options.
  • CAMBIUM-17466: Fixed an issue for when a user can log in to the Subscriber Module’s User Interface when the GUI User Authentication through RADIUS is enabled, but the RADIUS server responds with Access-Reject.
  • CAMBIUM-17564: Fixed an issue for when the Registered Access Point’s SSID does not display on the Subscriber Module’s eAlign page.
  • CAMBIUM-17567: Fixed an issue for when the SNMPv3 user table stays empty after adding a new user.
  • CAMBIUM-17576: Fixed an issue for when the 802.11n Subscriber Modules operating on 20MHz incorrectly display scanned Access Point’s channel bandwidth as 20MHz, against the correct value of 5/10 MHz.
  • CAMBIUM-17577: Fixed an issue for when the ePMP 1000 does not allow to set the maximum Tx power on a certain frequency range and country codes from User Interface.
  • CAMBIUM-17578: Fixed an issue when the SAVE and UNDO buttons continue to show highlighted after saving the 'wireless mac filter ’ and ‘snmpv3 user list’ tables.
  • CAMBIUM-17586: Fixed an issue for when the Save button stays highlighted after saving the changes made to the SNMPv3 users’ table.
  • CAMBIUM-17588: Fixed an issue for when a device does not respond to the snmpget query after changing the SNMPv3 Users table.
  • CAMBIUM-17646: Fixed an issue for when passwords return to the default values after rebooting on Elevated radios.
  • CAMBIUM-17663: Fixed an issue for when the Force 180 Subscriber Module does not respond to the snmpset reboot command.
6 Likes

Please put this up in cnMaestro cloud! Thanks!

3 Likes

I second that!! Please!

It will be available in cnMestro today.

Thank you.

thanks

it is good to know in detail the corrections of the new firmware

2 Likes

I am having a problem with the separate wireless management interface with new 4.6 fw.

Half of the times the Force 300 SM in NAT mode doesn’t get IP to Separate Wireless Management Interface from DHCP and the rest half of the times it gets the IP but it doesn’t get the Separate Wireless Default Gateway so I cannot access the SM from the Separate Wireless Management interface. Downgrade to 4.5.6 it works. Force 200 doesn’t have this problem.

Force300 in NAT Mode with PPPoE & Separate Wireless Management Interface (static ip) shows radio with 0.0.0.0 address. Force180/200 is fine but not Force300

Have tried several times to make it work, to no avail.

Rolling back to 4.5.6 the same configuration works

Thank you for the heads up.
The issue has been reproduced in the lab.
We are preparing the bug-fix release that will come up officially in the next few days.

Thank you.

& mine? Am i special? :slight_smile:

Looks like the same problem reported with the last several releases again.
I had previously reported this in MAY 2020, and again in OCTOBER 2020 with 4.6-RC29

Upgraded to 4.6 and SM’s show up in the list with 192.168.0.2 IP’s.

Clients seem to be working fine.
Tools → Wireless link tests work fine.
And if we know the SM’s IP, it seems we can log into them and administer fine.

I have updated a sector with 10 SMs to 4.6 and all have the IPs from our DHCP server… I have two more towers to update and I will post results.

Ours also have IP’s from the DHCP server… looking at the Server’s leases, we can see that they have IP’s, and those IP’s reply to pings, and we can log into the SM’s via those IP’s. It’s just on the AP’s ‘monitor → wireless’ list that the 192.168.x.x IP’s show up.

Strange it is random from unit to unit, one person has the issue but other does not even though same firmware and same equipment

Any news on the release of this fix? This is holding us back from upgrading to 4.6.

Anyone have any field data/evidence that the beam forming antennas are working? Bought mine at the end of 2019 and still haven’t been able to use them, love the idea/concept but man they are expensive “hood ornaments”.

Hi,

4.6.0.1 has been posted just now.

Thank you.

2 Likes

Anyone having random hard reboots with PTP 550 on 4.6?

@DigitalMan2020, I have seen some MU-downlink appear once the sector hits about 140 Mbps usage. Virtually zero below that. So I guess it works. I don’t have a lot of 300-N SM’s out there. There is a mix of F180’s plus elevated Ubiquity and some F300-16 and F300-19. 10 out of 77 are 3000 series. So I would expect more Mu-Mimo as I add newer devices. We are replacing Ubiquiti as they fail or the sub upgrades to our faster speed.