Yes, confirm. I set ap CAP:if ipv6 package is enabled, then use ipv6 address can connect to capsman, ipv4 address not work.
if ipv6 package is disabled, use ipv6 address can connect capsman.
/interface wireless cap print
enabled: yes
interfaces: wlan-lan
certificate: none
lock-to-caps-man: no
discovery-interfaces:
caps-man-addresses: 192.168.0.250
caps-man-names:
caps-man-certificate-common-names:
bridge: bridge-local
dec/12/2014 15:17:49 caps,debug CAP Select->Sulking
dec/12/2014 15:17:54 caps,debug CAP Sulking->Discover
dec/12/2014 15:17:54 caps,debug CAP discovery target list:
dec/12/2014 15:17:54 caps,debug ::ffff:192.168.0.250:5246
dec/12/2014 15:17:57 caps,debug CAP discovery over, no results
dec/12/2014 15:17:57 caps,debug CAP Discover->Select
dec/12/2014 15:17:57 caps,debug CAP did not find suitable CAPsMAN
Please email support output file from CAPsMAN and CAP to support@mikrotik.com with the steps how to repeat this problem.Did anything ever come out of the IPv6 problem? I am having a similar problem. Two basically clean boxes...
1 has IPv6 enabled... the other doesn't. CAPsMan won't connect between them. If I disable IPv6 it works fine. Thoughts? This is all on 6.28
Thx to Uldis! We solved this problem. CAPsMANv2 6.23 (may be earlier too) works via ipv4 address with one thing - need routes between networks in both side and opened ports on CAPsMAN 5246,5247/udp
I think it should be on wiki.
/ip firewall filter
add action=accept chain=input comment="CAPSMANAGER Discovery" protocol=udp src-port=5246,5247
add action=accept chain=input comment="CAPSMANAGER Discovery" protocol=udp dst-port=5246,5247