IPQ-4019 - qcom-ac in caps mode

RouterOS Wireless Networking
1

Hello,

We’re trying / testing out installing the newer wave2 qcom-ac driver on compatible ARM access points with the IPQ-4019 chipset. Successful installing and getting them configured with WiFi [Wave2] CAPsMan. However, not without issues.

Anyone successfully using qcom-ac drivers with multiple SSID’s and VLANS?

We manually configure the CAPS bridge interface, per MikroTik Documentation. Also configured CAPS mode to be “slaves-static=yes”.

However, even with slaves-static=yes and then the CAPsMan controller configuration set to ONLY “create enabled”. We’re experiencing issues where the CAP is provisioned more than one(1) time – the WLAN interface number keeps increasing, which breaks the bridge vlan settings…

Further – it appears the datapath VLAN ID DOES push to the CAP and successfully creates it within bridge, along with PVID… MikroTik is ALMOST there – but the CAPsMan controller complains.

Reason for all this… MikroTik stopped producting the mANTBox 52 15s [Dual band AC sector].. So we had to purchase the newer WiFi6 - mANTBox access points. These are working fine in CAPsMan.

When the qcom-ac access point is provisioned with wlan interfaces and the bridge/vlan settings are properly set. Devices register to the access point – but they are not stable. Constant reconnects. We rolled back an AP back to the regular wireless driver and all was nominal with stability. Same user devices connected.

We are now considering ditching MikroTik for Cambium for the RV Park customers. [Cant even do vouchers in Userman since RouterOS 7.0] - using third party hotspot.

2

I haven’t seen this problem (re-)appear, since all devices (capsman host and CAPs) are running on ROSv7.15.x AND Capsman Config with a minimal datapath has been created, using the single bridge - and with all bridges (Capsman host and on all CAPs) having the same local name (like “bridge” and not mixed names (“bridge” and/or bridge.local").
Uptime is only 4 weeks now…but so far, so good.

Edit: Oh, not to mention, that each CAP has been set to a distinct identity, and under capsman provisioning, each entry has a distinct name format, using the CAP-Identity, like “%I–2G” for 2.4GHz channels/SSIDs.

3

ROS 7.16 adds slave-name-format. This new config item may be useful.