The Wireless Link Test could not be started from cnMaestro.
ACG-16325
All
The SNMP client could be turned off after upgrading to the latest version, even though non-default community strings were configured.
ACG-16323
All
The Bridge Table could display incorrect or incomplete data.
ACG-16106
All
Stability improvements related to GPS chip operations.
AXG-13034
All
MIB/OIDs did not return SFP statistic values.
AXG-12181
All
The STP/RSTP BPDU Ethernet size changed after passing through the ePMP link, which could cause BPDU drops on certain switches.
AXG-13362
All
The crash with the signature tdd_arqtx_completion (kernel BUG at tdd_txwindow.c:389!).
AXG-11835
All
Uplink traffic was limited to 35 Mbps when MIR was enabled.
AXG-9030
All
SNMP did not operate when the DMZ was enabled.
AXG-8886
All
Watchdog actions were not logged to the syslog on the GUI.
AXG-10658
All
DHCP Option 66 did not operate when enabled on the GUI.
AXG-9038
All
DNS server IP addresses, IPv6 WAN addresses, and separate Management WAN IPv6 addresses obtained from the DHCP server were not displayed on the GUI when operating in NAT mode.
AXG-3613
All
The Globe Internet Connectivity icon appeared grey when the Management VLAN was enabled.
AXG-8308
F4525/F4518/F4625/F4616
Spontaneous performance drops occurred on SMs under heavy bidirectional UDP traffic on an 80 MHz.
AXG-12200
F4525
SM did not reconnect after reboot when RADIUS authentication was enabled.
AXG-11349
ePMP4600
The Wireless Link Test reported low throughput when background traffic was running to multiple SMs.
AXG-12651
All
The SM reconnection took a long time after disconnection with Reason 42 (STA DISASSOC REASON PPPOE LCP LOST) when the PPPoE client was enabled.
AXG-13433
All
GPS issue caused by an invalid GPS signal was observed between January 8 and 11, 2026.
AXG-12955
All
Performance degradation that could occur over time in ePMP 4500 deployments was addressed.
AXG-13583
All
The Web UI was updated to replace CMM options with Cambium Sync.
AXG-13582
All
An issue where link-local packets were incorrectly counted as dropped on the Ethernet interface was corrected.
AXG-13386
All
An issue where SFP modules could not negotiate in Manual 1 Gbps mode was corrected.
Was there not a few issues with the Beta that included low speeds and scaling issues when more than a certain amount of subs were connected to the AP? I’m assuming now the stable version is out that all of those problems have been fixed in this release?
The scaling issues have not been resolved in this 5.11. They needed to release 5.11 to better support the recently released F4518 and F4616 radios. The scaling issues will hopefully be addressed in 5.11.1 or 5.12, as soon as possible.
We’re reviewing the reports and working closely with Eric to address the issue. Version 5.11 delivers a set of performance improvements along with new features aimed at enhancing the user experience on both 6 GHz and 5 GHz networks, and we chose not to delay the release.
Compared to 5.10.4, version 5.11 includes substantial enhancements. Overall sector capacity has increased, especially in deployments with a high number of SMs. PPS numbers have also been improved for F4625/4525 and ePMP 4600, leading to better handling of small packets and improved performance with 80/160 MHz bandwidths.
The scenario currently under investigation involves running a throughput test to a single SM while many SMs are connected to the AP, with a relatively small amount of high-priority background traffic distributed across multiple or all SMs. In this situation, the measured throughput may not reach the sector’s maximum capacity.
This is not a regression introduced in 5.11 and was not considered a release blocker. That said, we are treating it as a high priority and expect to include additional improvements in the 5.11.1 or 5.12 release.
Guys please, please prioritise the issue where randomly some CPEs stop replying ping on the management interface. It is driving me crazy here!! ticket 474679.
Anyone else see performance regression on 5.11 vs 5.10.1 with 4500/4525 equipment?
Upgraded AP and SM from 5.10.1 to 5.11 and cnMaestro reports around a 2-3% increase in UL retansmission %. Also, single and multiple SM Link Tests are lower by 20% on Single and 30-40% on multiple-SM.
Seems to be AP side as I installed a new SM yesterday on this 9 client AP and the SM was running 5.11 but the AP was still 5.10.1. Link test and speedtests were 320M+ (40mhz channel). After the upgrade early this morning this SM now only shows around 250-285M.
Here is an example of the degradation in UL Capacity/MCS before and after the AP upgrade. AP upgrade was 2am.
We upgraded a Force 4625 point-to-point link from version 5.10.4 to this new version 5.11.0, and the link’s throughput dropped from 650 Mbps to 326 Mbps. We had to revert to the previous version.
Did you happen to notice if your signals dropped during that time on 5.11 as well? There have been some reports of people seeing their RX signals on the slave side lower on some links.
I didn’t notice any decrease in the RX Signal with version 5.11.0.
The modulation was the same, but the traffic the link could handle was significantly lower, almost exactly 50% worse. It sounds like this new version introduced some problem with MU-MIMO in this scenario, perhaps.
I would like to further investigate your case. Could you please upgrade your link once again to version 5.11.0, perform the Wireless Link Test three times, and then download and share the tech support files on both versions with me?
Afterward, if the performance remains unsatisfactory, you may downgrade to the previous version.
We’d also like to understand what type of traffic is being carried over the link—for example, whether it’s MPLS, PPPoE, EoIP, or something else.
I seem to be seeing similar. New AP with its first SM and with either the AP or SM or both on 5.11 I get around 200M less than if I have both SM and AP on 5.10.4 on 20s WLT.
If AP is 5.10.4 with 5.11SM things are a little better but not as good as with all on 5.10.4.
And it’s frustrating that Cambium decided to abandon compatibility, so that we can’t use our existing stable 3000APs with 4525 series SMs. Yes, I know I’ve already vented about this before, but that’s just such a mess, and it’s killing us.
All my links are updated and rock stable, performing better than ever, with the improvements to MIMO helping vastly during peak times.
No need to be melodramatic.
