Is it possibly to configure CAPsMAN v2 and the local wireless interface (in CAP mode) on the same device ? I issued a CAP reconnection loop on the device. Any suggestion or any the same problem ? Thx.
yes, you can make such configuration - it will work.
tried to do it on rb493ah but capsmann did not recognise the interface as cap. it does ok for other devices on the network but not for the interface on same board.
configure the built in wireless CAP menu to use capsman address 127.0.0.1
no react after 127.0.0.1 what discovery interface should be?
Make sure that you allow connections to ports 5246,5247/UDP.
You can specify any local interface in the discovery but the capsman address setting with 127.0.0.1 should be working.
Please enable the caps,debug and check the logs why it doesn’t connect to the CAPsMAN.
Hi, I have the same problem.I have a hAP ac lite and i want to connect two mAPs to it for my home. And i like the centralized management, so i wanted to configure CAPsMAN and begun by configuring hAP ac first. I wanted to enable CAP and CAPsMAN on it. After i put CAPsMAN address 127.0.0.1 on the CAP setting for the 2.4GHz antenna, it doesn’t work. When i go to firewall settings , i have a rule from the default configuration that says to drop anything not coming from LAN. LAN is an interface list that has my router’s bridge and that bridge contains all interfaces, wireless included. So why doesn’t it work correctly? I mean since the firewall rule contains all local interfaces, i shouldn’t need to create a rule for CAPsMAN UDP ports. When i disable the default rule it works correctly. After i re-enable it, it still works ok. Any clues?
Did you find the solution?
I have the same problem. If I disable the firewall rule “defconf: drop all not coming from LAN” then CAPS activate the wlan, but with the rule activated it does not work.
regards
I think I can reply myself.
As described here http://forum.mikrotik.com/t/defconf-drop-all-not-coming-from-lan-really-needed/123578/12 the rule is there to prevent access from internet to the router management. But it prevents also access from wlan as is is set as “drop from !LAN”. So changing it to “drop from WAN” instead solves the problem.
regards