❯ grep bridge praze.rsc | grep wifi
add bridge=bridge comment=defconf interface=wifi1
afaict wifi1 is added to the bridge.
I followed the instructions here:
https://help.mikrotik.com/docs/display/ROS/WifiWave2#WifiWave2-WifiWave2CAPsMAN
What am I missing please? Here’s my configuration https://gist.github.com/kaihendry/12ae22ddbdcb524fd37eb07f802f80bf
I haven’t got a wifiwave2 device at hand, but with the default wireless package, you have to explicitly tell the cAP that the CAPsMAN is listening on 127.0.0.1 if the wireless interface that seeks CAPsMAN control is colocated with the CAPsMAN itself on the same hardware.
I assume it’s still the case with wifiwave2, as it is related to the architecture that doesn’t allow processes running on the same hardware to talk to each other on L2 as both use the same bridge port and the bridge cannot hairpin frames back to the port it has received them from. And the auto-discovery of CAPsMAN only uses L2 frames.
Capsman for ww2 can not control a local radio.
You need to set it up locally, using more or less the same settings as capsman.
Since it will be the same ROS instance controlling the radios, everything will work smoothly.
But is this the problem here ?
The question and context is not clear to me.
Can I ask you to share a link to docs where it is written that local radios are not supported?
Just can’t find such statement.
Can not find it back in the docs but it is common knowledge around here.
Search the forum, plenty of references indicating this behavior.
Here is the first one I found
http://forum.mikrotik.com/t/hap-ax3-wifiwave2-capsman/163543/1
Search for similar posts from normis, he also mentioned it several times already.
Once again:
Local radio CAN be used but not via capsman.
You need to set it up locally ( which for 90% are the same settings as capsman)
All the rest ( fast roaming etc) will work however because of ’ the same ROS instance’.
Indeed, there is a clear statement by Mikrotik staff in the same topic: http://forum.mikrotik.com/t/hap-ax3-wifiwave2-capsman/163543/35 . Nice 
So for example, one has a wifiwave2 capable hapAC3, and some capax’s
One would setup capsman on the AC3 and have to do almost nothing on the capaxs but the wifi on the hapac3 would be a non wifiwave2 setup, in terms of vlans etc.. . Like I know how to do them via pcunite???
Experimenting a bit with that myself lately.
Especially when you have a config where base vlan <>1, cap will not get an ip address and no communication with controller which is logical since default it will not use vlan, only untagged traffic.
So nothing will work.
On cap you need to config bridge so it receives ip lease from capsman controller ( assuming it also acts as dhcp server) via the new base vlan.
And then it should work ( but that last part I still need to test myself).
OK, done.
Thinking a bit further about it, it all makes sense. There is no magic involved.
When NOT using standard base vlan with pvid=1 (as described in pcunite’s fantastic series), cap device needs to be modified to have trunk port for all possible VLANs being thrown at it but in this case also tagged to bridge since that’s where capsman will add the dynamic interfaces.
Also make sure it gets IP services from router (BASE_VLAN setup).
Access point setup for reference:
http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/4
Dynamic wifi interfaces will be added to bridge with pvid set in accordance with their config as provisioned by capsman.
Even simpler …
Standard caps mode
Add BASE-VLAN as interface to bridge
Change DHCP client to BASE_VLAN
Change CAPs discovery interface to BASE_VLAN
Seems to work as well.
Sounds very similar to this post…
The documentation available and videos are so good, there are no issues at all…
http://forum.mikrotik.com/t/what-is-the-best-spot-to-create-vlan-on-ac3/170889/8