CAPsMAN dont see IP addressess of remote-cap

RouterOS General
1

My CAPsMAN is not displaying IPs of remorte-cap’s. On occasion it can display IP but it will go after reboot or re-provision

[admin@urbinek_CRS305] > /caps-man/remote-cap/print detail 
 0 state="Run" name="[C4:AD:34:40:7A:D7]" base-mac="C4:AD:34:40:7A:D7" board="RBcAPGi-5acD2nD" version="7.2rc3" identity="urbinek_RBcAPG" radios=2 address=C4:AD:34:40:7A:D7/15102
 1 state="Run" name="[E4:8D:8C:CC:F2:DE]" base-mac="E4:8D:8C:CC:F2:DE" board="RB951G-2HnD" version="7.2rc3" identity="urbinek_RB951G" radios=1 address=10.10.10.2/56143
 2 state="Run" name="[CC:2D:E0:C5:1C:74]" base-mac="CC:2D:E0:C5:1C:74" board="RB962UiGS-5HacT2HnT" version="7.2rc3" identity="urbinek_RB962UiGS" radios=2 address=CC:2D:E0:C5:1C:76/59404

Is this somewhat a problem?

2

This is by design. If the CAPs contact the CAPsMAN via L2, which is preferred by default, CAPsMAN is not interested in their IP address, so it doesn’t keep it in its local context data.

3

Okay, so there is no point in forcing it to use IPs as it would introduce additional payload?

4

Only sniffing can give an answer here. But I assume Mikrotik have their reasons to prefer L2 when available - it may be not just a matter of the packet size itself but also of the associated CPU load (the IP and UDP headers have to be added and stripped).

5

Yeah, i am generalising.

Any way, l2 answer works for me, thanks

6

Hello, I had the same problem - solution is disable discovering in CAP settings - use request certificate and lock to capsman. It works!