CAPsMAN on dedicated VLAN

RouterOS Wireless Networking
1

Hi

We have to let CAPsMAN running on a dedicated VLAN (5), but the AP’s are not listed under “Remote CAP”.
The port where the AP is connected is an access port on VLAN 5, it gets an IP from the DHCP server and it is reachable from the firewall in the same subnet. So layer 3 looks fine all over.

To realize it, we defined the VLAN 5 as a new interface, gave them an IP and that interface to cap and capsman:

/interface vlan add comment="capsman vlan" interface=bridge1 name=vlan5 vlan-id=5
/ip address add address=192.168.52.66 comment="capsman ip" interface=vlan5 network=192.168.52.66
/interface wifi cap set caps-man-addresses=192.168.52.66 discovery-interfaces=vlan5 enabled=yes
/interface wifi capsman set ca-certificate=auto certificate=auto enabled=yes interfaces=vlan5

Now, the AP can ping the assigned IP.


The AP is connected to a switche on the floor, the CAPsMAN is running on the core switch.
I can see the discovery packets on the core switch:

520.488 qsfpplus1-1                    192.168.52.70:48397                                       192.168.52.66:5246           udp            66   0
520.488 bridge1                        192.168.52.70:48397                                       192.168.52.66:5246           udp            66   0
520.488 vlan5                          192.168.52.70:48397                                       192.168.52.66:5246           udp            62   0
520.488 qsfpplus1-1                    192.168.52.70:48397                                       255.255.255.255:5246         udp            66   0
520.488 bridge1                        192.168.52.70:48397                                       255.255.255.255:5246         udp            66   0
520.488 vlan5                          192.168.52.70:48397                                       255.255.255.255:5246         udp            62   0
523.823 lo                             192.168.52.66:34204                                       192.168.52.66:5246           tcp           109   0
523.823 lo                             192.168.52.66:34204                                       192.168.52.66:5246           tcp           109   0
523.825 lo                             192.168.52.66:5246                                        192.168.52.66:34204          tcp           109   0
523.825 lo                             192.168.52.66:5246                                        192.168.52.66:34204          tcp           109   0
523.825 lo                             192.168.52.66:34204                                       192.168.52.66:5246           tcp            66   0
523.825 lo                             192.168.52.66:34204                                       192.168.52.66:5246           tcp            66   0
527.977 qsfpplus1-1                    192.168.52.70:55432                                       192.168.52.66:5246           udp            66   0
527.977 bridge1                        192.168.52.70:55432                                       192.168.52.66:5246           udp            66   0
527.977 vlan5                          192.168.52.70:55432                                       192.168.52.66:5246           udp            62   0
527.978 qsfpplus1-1                    192.168.52.70:55432                                       255.255.255.255:5246         udp            66   0
527.978 bridge1                        192.168.52.70:55432                                       255.255.255.255:5246         udp            66   0
527.978 vlan5                          192.168.52.70:55432                                       255.255.255.255:5246         udp            62   0
533.826 lo                             192.168.52.66:34204                                       192.168.52.66:5246           tcp            66   0
535.818 vlan5                          192.168.52.70:38928                                       255.255.255.255:5246         udp            62   0

192.168.52.70 is the AP.

What we have to configure wrong or as additionally?

Thanks a lot for any hint.
Ivo

2

It work’s with our configuration, but our test AP is a “mAP lite” and it seems, it not works with CAPsMAN :frowning:
After we tested with an “cAP ax”, we can see them.

3

mAP Lite requires the CAPsMAN supplied with the wireless driver. If it is only for testing, you better get an AX device (or a wifi-qcom-ac supported device).

4

Thanks a lot for your answer.
Where we have to install which drivers? I tried out to find any information about, but it’s not really clear how we have to go on with it.

Thanks a lot
Ivo

5

Running newest CAPsMAN requires AX device (using wifi-qcom as only option) or AC device (using ARM processor and wifi-qcom-ac driver).

If you want to support the older CAPsMAN (ac or older devices), you have to use the wireless driver.

There are lots of topics and documentation on this topic.