/interface wireless cap
set bridge=Bridge caps-man-addresses=192.168.76.254 caps-man-names=CapsMan discovery-interfaces=Bridge enabled=yes interfaces=wlan1,wlan2 static-virtual=yes
All device are in the same network (test enviroment)
In the CAP device log I see it use the MAC connection
CAP connected to CapsMan (DC:2C:6E:9E:FD:0A/7/0), CommonName ‘CAPsMAN-DC2C6E9EFD09’
CAP joined CapsMan (DC:2C:6E:9E:FD:0A/7/0)
In CapsMan Device log I see the same
[B8:69:F4:3A:04:1E/12/d055,Join,CAP-B869F43A041E] joined, provides radio(s): B8:69:F4:3A:04:20,B8:69:F4:3A:04:1F
In CAP log:
CAP selected CAPsMAN CapsMan (::ffff:192.168.76.254:5246)
CAP connected to CapsMan (::ffff:192.168.76.254:5246), CommonName ‘CAPsMAN-DC2C6E9EFD09’
CAP joined CapsMan (::ffff:192.168.76.254:5246)
In log on Capsman side:
[::ffff:192.168.76.1:34056,Join,CAP-B869F43A041E] joined, provides radio(s): B8:69:F4:3A:04:20,B8:69:F4:3A:04:1F
I assume as the MAC based communication is prefered, if the Discovery Interface is set the CAP will use the MAC based communication, If it is not set the CAP pick up the CapsManAddess and connect via IP
I have found an other “Feature” If on the DHCP server the CAPs Manager is set The CAPs able to pick up the IP via this parameter and even don’t need to configure the CapsManAddess