I have configured an RB5009 and 2 cAPax from scratch for capsman.
Everything looks OK on the cap:
Everything also looks OK on the Capsman:
But as soon as I assign a config to the interface (no matter if manually or via provisioning) I get ‘no connection to capsman’ ?
Where am I making a mistake?
br, Richard
Hard to tell without seeing config on both ends …
Perhaps you are passing “manager=” value via CAPsMAN configuration you are trying to provision, that might cause a similar issue.
Is there a real or valid use case to pass the “manager” attribute to CAPs? If yes: I am interesed. If no: why not just prevent this mis-configuration case?
Here the configs for RB5009 + cAPax … nothing special, i am still at the beginning…
capax_wz_config.rsc (3.38 KB)
rb5009UPrS_config.rsc (14.8 KB)
As said by Guntis: your “/interface/wifi/configuration” items are full of “manager=capsman” attributes. Please remove these.
Ohhhh … OK, will check that !
br Richard
That’s it !!! Thank you very much !!!
One more question: are virtual APs in ros7 no longer displayed below the master interface, slightly offset to the right so that it can be recognised?
br Richard.
PS: I would never have thought of this misconfiguration 
Everything works except for the virtual APs. The devices see the SSID, but do not connect to any APs (no IP). I created them manually under wifi, master interface is the 2.4GHz interface. Is there anything else to consider with virtual APs under ROS7?
br Richard
you must set a slave-datapath on the caps.
just create one that just points to the default bridge. (anywhere it can find all vlans if necessary)
/interface/wifi/cap
on the caps or in capsman ?
PS: now it occurs to me: does the respective bridge-name of the caps (cAPax) or the bridge-name of the capsman (rb5009) belong in the datapath settings on the capsman (rb5009) in datapath?
On capsman.
Cap gets config from capsman.
and which bridge name … from caps or capsman … actually set from caspman and virtual APs not working :-/
Then you did something wrong.
See example, name used on datapath setting clearly is the one from capsman (which makes sense, it’s that bridge which needs to handle the VLAN stuff)
https://help.mikrotik.com/docs/spaces/ROS/pages/224559120/WiFi#WiFi-WiFiCAPsMAN
but the virtual APs (created manually) are not part of the local bridge on the CAP, perhaps that is the issue ?
When using CAPsMAN to provision a CAP, also virtual APs have to be set-up via CAPsMAN. No local configuration of wireless should be necessary (except perhaps VLANs on wifi-qcom**-ac**-driven devices).
By default, virtual APs are made members of same bridge as master interface. If you want to separate traffic from different APs (master and virtual), then you have to use VLANs … both internally to CAP and on connection towards network core (and on core router).
@OP as there are no provisioning rules in your posted configuration export, I assume you manually provisioned the CAPs. That is not the intended way to do it. Usually ones uses provisioning rules. On these rules you define the master and slave configuration. slave configuration translate to virtual SSIDs. See the docs for a simple example here.