Hello,

recently I set up a capsman on my router (rb750) and combined it with couple of cap acs (all using wifi-qcom-ac-7.14.3-arm.npk) so I can say I know how to do a basic capsman setup.

Now I decided to take my LTE12 router and try to set up a local capsman to manage its two wifi radios. I updated routeros/firmware to most recent (7.14.3) versions, removed wireless package and installed wifi-qcom-ac, reset it once more and tried to enable a local capsman to manage local wifi. Idea is to add cap-acs later after this thing starts working. However, when I enable cap, nothing happens with wifi interfaces. Usual case (with cap-ac) is that at that point they would became managed by capsman, but with LTE12 nothing happens.

Here's my order of operations:
- I create security profile and configuration
- in wifi tab under CAP I enable it, set discovery interfaces to all (for now), set capsman address to 127.0.0.1
- in remote CAP tab under capsman I enable it, set interfaces to all and my capsman server appears in the list
- I also enable provisioning with "create dynamic enable" action and assign a cfg1 configuration

Nothing happens so I reboot, but afterwards also nothing happens. I tried manually disabling/enabling wifi interfaces, but still nothing.

Am I missing something trivial?

Thanks,
Bruno

Interesting, can you point me to docs saying that as in official Mikrotik's YT video guy was doing exactly that? Admittedly, with previous version of capsman, but still, fundamentally there shouldn't be such a difference.
Also, if managing local interfaces by a locally running capsman isn't possible, how are we expected to utilise capsman backed roaming (fast transitions)?

Go to and use the "provision" command to provision your local radios (marked with "L" on output of /interface/wifi/radio/print"). Done

This doesn't seem to do what it's supposed to do (maybe). It did work in a sense that provision command didn't complain. My wifi interfaces got "read only", wifi network specified in configuration appeared, but without internet access. Also I didn't get a red comment in wifi interfaces about interfaces being managed by capsman.

Just for test, I took one cAP ac and connected it to router - everything worked immediately - I got two cap-wifis in the list of interfaces, bot marked as managed by capsman, I was able to conect to wifi and got internet access immediately.
It seems to me that provisioning you mentioned doesn't manifest itself in a same way as provisioning of external ap.

@ips
Is it possible but not recommended or impossible?

@bbatarelo
Maybe this?
viewtopic.php?t=203335

It seems to me that provisioning you mentioned doesn't manifest itself in a same way as provisioning of external ap.

Maybe you did not configure "datapath.bridge" to your default bridge (e.g. datapath.bridge=bridge). So your local radios may got provisioned perfectly, but not assigned to any bridge. Would at least explain what you've described by "but without internet access".

Also I didn't get a red comment in wifi interfaces about interfaces being managed by capsman.

Because - IMHO - they aren't. They are just provisioned by the same config you specified in provisioning. They are dynamic and when you change your config, it affects your caps and local radios at the same time.

Yep, the thread I posted a link to earlier:
viewtopic.php?t=203335

seems to say that it is actually possible, but no idea whether it is accurate and if it is "full control" or somehow only partial.

viewtopic.php?p=988941#p988941

When a device is running WifiWave2 CAPsMAN, it cannot set its own wireless interfaces as CAPs. This is a known limitation, due to how the driver works, there is a "hidden" (system level) provision rule for local interfaces, which makes them incompatible with local CAPsMAN.

Though you can just pass the same configuration manually for local WifiWave2 interfaces, as you would via provisioning rules - just use "/interface/wifiwave2/ set wifiX configuration=X", which could be argued that it is more simple to do, than configuring "/interface/wifiwave2/cap" and setting "configuration.manage=r" to capsman-or-local/capsman.
The end result is the same, as WifiWave2 CAP interfaces and regular WifiWave2 interfaces use the same exact system, it's not divided into separate menus as original CAPsMAN and regular wireless was.

On a separate note, make sure you don't set "configuration.manager=capsman", in the configuration profile that you assign via provisioning rules, this setting should be set on CAP device "/interface/wifiwave2 set " itself, and must not be passed to CAP that has already joined CAPsMAN.

I am sure that support team is one large "cluster of human knowledge". But many things don't get written down @ help.mikrotik.com/docs/