CAPsMAN does not enable local wlan1 and wlan2 of the manager
Posted: Tue Nov 07, 2017 2:35 am
Greetings everyone, first post here and first experiences with Mikrotik, in a lab setup. The setup:
. 1x RouterBOARD 962UiGS-5HacT2HnT (hAP ac), serves as the CAPsMAN manager
. 1x RBwAPG-5HacT2HnD (wAP ac), serves as an AP to be managed by the manager
. hAP ac's ether1 (WAN) gets a 192.168.1.0/24 IP from the local modem
. wAP ac's ether1 port is connected to ether3 on the hAP ac
. hAP ac is on 192.168.88.1
. I configure everything by the book on the manager: enable the CAPsMAN manager, datapaths, channels, security, configuration and provisioning
. I configure everything by the book on the wAP ac: CAP enabled on the Wireless interfaces, set to both wlan1 and wlan2, discovery interface ether1
Now with this I can see that the hAP ac properly manages the wAP ac. I can see the wifi networks show up, and obviously wlan1 and wlan2 enabled and the SSID on the CAPsMAN table alongside other info there.
But... When I go on the hAP ac's *own* Wireless table, click on CAP and enable it, same settings as the wAP ac, the Wireless table now says "--- managed by CAPsMAN", but both wlan 1 and wlan2 are disabled and I can't get them to be enabled.
So it seems I can setup CAPsMAN to manage the AP on the network, but I can't seem to make CAPsMAN manage its own Wireless interfaces.
I'm sure there's something ridiculously silly that I'm overlooking, but I've been at this for days and I can't figure it out. Anyone please care to point me in the right direction?
Many thanks!
. 1x RouterBOARD 962UiGS-5HacT2HnT (hAP ac), serves as the CAPsMAN manager
. 1x RBwAPG-5HacT2HnD (wAP ac), serves as an AP to be managed by the manager
. hAP ac's ether1 (WAN) gets a 192.168.1.0/24 IP from the local modem
. wAP ac's ether1 port is connected to ether3 on the hAP ac
. hAP ac is on 192.168.88.1
. I configure everything by the book on the manager: enable the CAPsMAN manager, datapaths, channels, security, configuration and provisioning
. I configure everything by the book on the wAP ac: CAP enabled on the Wireless interfaces, set to both wlan1 and wlan2, discovery interface ether1
Now with this I can see that the hAP ac properly manages the wAP ac. I can see the wifi networks show up, and obviously wlan1 and wlan2 enabled and the SSID on the CAPsMAN table alongside other info there.
But... When I go on the hAP ac's *own* Wireless table, click on CAP and enable it, same settings as the wAP ac, the Wireless table now says "--- managed by CAPsMAN", but both wlan 1 and wlan2 are disabled and I can't get them to be enabled.
So it seems I can setup CAPsMAN to manage the AP on the network, but I can't seem to make CAPsMAN manage its own Wireless interfaces.
I'm sure there's something ridiculously silly that I'm overlooking, but I've been at this for days and I can't figure it out. Anyone please care to point me in the right direction?
Many thanks!