Yesterday i risked an experiment and used #hermes_agent #localai #qwen36 to upgrade my #mikrotik #cAP_ac_XL from #capsman to the new #wifi stack.

I was too lazy to try but curious if providing #ssh access to both of my devices made it possible to let the agent do the work and it was a full success.

If something would have been broken i could just re-apply the #backup performed before.

Achja,

Im "neuen" Capsman (Wifi6/7) ist das Capsman forwarding wieder da (ab v7.21):

https://manual.mikrotik.com/docs/wireless/wifi/capsman#capsman-datapath

#mikrotik #capsman #wifi #WiFicAPsMAN #datapath #wifi6 #ax #be #wifi7

If anyone has a #Mikrotik Audience with the three Wifi radios, and has upgraded to RouterBoard 7.22 and found that the #CAPsMAN setup is broken, I have found the solution.

Take wifi3 on your CAPsMAN manager and set it to AP mode, choose an SSID, password and a fixed radio frequency (mine is 5500). The remote Audience, set up wifi3 exactly the same way, SSID, pass and frequency, but set it to "station-bridge" mode. This will allow the remote CAP to find the CAPsMAN manager and provision itself.

A very very important note about @mikrotik CAPsMAN.

There are two different WiFi "stacks" for RouterOS: wireless and wifi-qcom. Both provide CAP/CAPsMAN but they are not compatible. A CAP device using wireless package can't talk to a CAPsMAN device using wifi-qcom (and vice versa I guess).

For example, cAP Lite runs on wireless package and to control it from RB5009 you need to install the wireless package on the latter!

#mikrotik #capsman #wifi