I even gave up trying to make my HapAx3 control my 16 cap-ac, after this new update things changed a little.
And for a change, I purchased HapAX3 without knowing that I would face these problems with Capsman. The solution for now, configure the 16 cap-ac by hand.
I replaced the cap's wirelles package with wifi-qcom-ac, hoping that it would provision using my VLAN configurations, but without success.
Then I found this document from Mikrotik, which buried my hopes once and for all.
Follow the link:
https://help.mikrotik.com/docs/display/ROS/WiFi
*****************************
Lost features
The following notable features are lost when running 802.11ac products with drivers that are compatible with the 'wifi' management interface
Nstreme and Nv2 wireless protocols
VLAN configuration in the wireless settings (Per-interface VLANs can be configured in bridge settings)
Compatibility with station-bridging as implemented in the 'wireless' package
And for a change, I purchased HapAX3 without knowing that I would face these problems with Capsman. The solution for now, configure the 16 cap-ac by hand.
I replaced the cap's wirelles package with wifi-qcom-ac, hoping that it would provision using my VLAN configurations, but without success.
Then I found this document from Mikrotik, which buried my hopes once and for all.
Follow the link:
https://help.mikrotik.com/docs/display/ROS/WiFi
*****************************
Lost features
The following notable features are lost when running 802.11ac products with drivers that are compatible with the 'wifi' management interface
Nstreme and Nv2 wireless protocols
VLAN configuration in the wireless settings (Per-interface VLANs can be configured in bridge settings)
Compatibility with station-bridging as implemented in the 'wireless' package
Statistics: Posted by Turbovix — Fri Mar 15, 2024 12:18 am