Hello, is there a timeline for when all the advertised features will be implemented?
Which specific features are you wondering about?
Pretty much all of the features have been available via WLR mode since the hardware came out.
It took a bit longer for all these features to be added in TDD/PtMP mode, but I think they’ve got everything covered at this point and working pretty well… so you’ve got e1k/e2k/e3k backwards compatibility, QoS/QoE/DPI, beamforming, MU-MIMO, asymmetric uplink, jumbo MTU’s, etc.
What else where you looking for?
UL MU-MIMO/Beamforming I believe was mentioned in the early presentations and has not been implemented yet. Beyond that I cannot think of anything else missing.
On second thought I do have one more feature that is still not working quite right. DMZ.
DMZ still has the bug where if you enable DMZ you cannot SNMP poll the device as the SNMP port is forwarded to the DMZ. I believe I was told it would be fixed in 5.11 firmware?
Have you tested to see if port forwarding rules will override the DMZ? For example, forwarding UDP/161 back to the radio IP address?
Hi @scracha,
we are reworking DMZ feature right now. There is no workaround for the mentioned issue.
It should work properly in 5.11.0.
Thank you!
Hi Andrii. Same issue with DMZ (SNMP & SSH not accessible unless using separate management IP) in 5.11Rc57.
In 5.11RC54 DMZ works fine for me with SNMP polling the radio just fine. Have not tested SSH. Did something change in RC57?
SM in router/NAT mode with management IP being the WLAN IP address of SM.
Hmm. Odd. Thanks for the update. Can’t be SNMP settings as it worked straight away when I setup management IP. Maybe that forces a radio reboot or something. Depending how chaotic my day is tomorrow I’ll do some more testing over F300 and F4545l and see what I’ve messed up 
. Will be fantastic if Cambium have finally nailed this.
Hi @scracha,
Could you please clarify whether SNMP and SSH access to the WAN interface fails when the Separate Wireless Management Interface is enabled or when it is disabled?
If you are attempting to access SNMP/SSH via the WAN interface while the Separate Wireless Management Interface is enabled, this is expected behavior. By design, SNMP and SSH access are handled through the Separate Wireless Management Interface when it is enabled.
If the issue occurs in any other scenario, that would be unexpected behavior, as we are not able to reproduce it in our lab.
Hi @Vladyslav_Sapeha . I have an open ticket 465219 where your team has full access to my setup for this beta plus as it’s NZST you’re not going to disrupt my users.
Do you want me to reply with details of the DMZ with SNMP/SSH problems in that ticket or createa new one? I already highlighted another bug when there’s brackets in the Device Name.
I would appreciate it if you could open a new ticket for the DMZ issue. This will help us track and manage it more efficiently.
Hi Vladyslav. I’ve done a bit more testing and it appears OK on the AX stuff but the AC subs (F300-25 etc) still have the issue. Also I’m using a non default SSH port on my configurations.
Hi @scracha,
Behavior on AX and AC platform could be different cause in since 5.10.1 release Separate Management Wireless interface logic was changed on AX platform but same changes will be ported on AC in the future release.
To ensure the behavior is not related to another feature or issue, please Raise a Ticket so we can investigate it in more detail.