CAPsMAN v2 wifi-qcom-ac with CAPs in different IP network don't work

RouterOS Wireless Networking
1

Hello Forum,

I have CAPsMAN for WAVE2 running (wifi-qcom-ac). On my default location the APs finding it’s manager on layer 2 by discovery-interfaces=… Now I need to attach some APs from a distance IP network. For this I planed to use caps-man-addresses=192.168.89.1 on the remote CAPs to use layer 3 for caps. On CAPsMAN I can see reaching udp port 5246 packets coming from the remote CAPs, but the CAPsMAN does not answer these requests.

cAP

/interface wifi cap
set caps-man-addresses=192.168.89.1 certificate=request discovery-interfaces=bridge1 enabled=yes \
    slaves-datapath=capdp slaves-static=yes

There is no firewall on CAPsMAN master. CAP can reach IP 192.168.89.1 by ping and any other services and twice versa.
Any hints about why the master does not respond to the caps on its caps-man-addresses=192.168.89.1 ?
Regards,
David

2

Are you sure the master is receiving those requests at all ?
No incoming firewall rules blocking some things ?

3

Config on capsman controller?
capsman.png
For me it is working fine.

4

Hi, yes I am sure. Verified twice
1st by /tool/sniffer/quick interface=all ip-address=192.168.200.84 ip-protocol=udp port=5246

/tool/sniff pack pr det
 0 time=8.223 num=1 direction=rx src-mac=F8:6B:D9:43:19:F4 dst-mac=B8:69:F4:88:19:07
   interface=ether6-wan src-address=192.168.200.84:49080 dst-address=192.168.89.1:5246 protocol=ip
   ip-protocol=udp size=52 cpu=0 ip-packet-size=38 ip-header-size=20 dscp=0 identification=19766
   fragment-offset=0 ttl=64
 1 time=9.225 num=2 direction=rx src-mac=F8:6B:D9:43:19:F4 dst-mac=B8:69:F4:88:19:07
   interface=ether6-wan src-address=192.168.200.84:49080 dst-address=192.168.89.1:5246 protocol=ip
   ip-protocol=udp size=52 cpu=0 ip-packet-size=38 ip-header-size=20 dscp=0 identification=19786
   fragment-offset=0 ttl=64
 2 time=10.227 num=3 direction=rx src-mac=F8:6B:D9:43:19:F4 dst-mac=B8:69:F4:88:19:07
   interface=ether6-wan src-address=192.168.200.84:49080 dst-address=192.168.89.1:5246 protocol=ip
   ip-protocol=udp size=52 cpu=0 ip-packet-size=38 ip-header-size=20 dscp=0 identification=19873
   fragment-offset=0 ttl=64

I can only see rx packets non tx in my trace.

2nd I am able to reach IP services on caps master initiated from AP, here for example DNS using UDP:

:put [:resolve server=192.168.89.1 mikrotik.com]
159.148.172.205

Regards,
David

5

In my CAPsMAN config I have selected an interface. This is the only difference.

/interface wifi capsman
set enabled=yes interfaces=vlan1001 upgrade-policy=suggest-same-version
6

I tried this before via internet but found the same result.

Hope this can be fixed.

7

Sorry, I read incorrectly

8

SOLUTION was to unset interfaces in /interface/wifi/capsman. Having

/interface/wifi/capsman set interfaces=""

it works.