Hi,
I have AC3 as main router and 2x AX2 as AP. I have fast roaming enabled but mobile often stuck on wrong AP. Is fast roaming better with capsman? Is still capsman for WiFiwave only in CLI? Thank you
An Access Control list that kicks devices off an AP when the signal level gets outside of a threshold, has been the STANDARD on caps-man for almost 10 years.
Hi @Rox169, I’m testing something that may be useful for you (if works), CAPsMAN without provisioning, just for Fast Transition.
Still dealing with support waiting some answers.
At the moment goal not reached but could be ROS7.10…
Capsman ww2 is not only available in CLI.
It’s (almost) completely integrated in the wifiwave2 menu structure (why almost ? Could be some minor bits and pieces are cli only for the current release but then it’s only a matter of time before they appear in webfig or winbox).
Usage of access list is not really fast transition as defined in 802.11r, it’s to “convince” devices to move over to another AP.
But yes, that should be standard setting for any AP (even when not using capsman) since it’s the client who decides to switch, so some “guiding” might be needed when they hold on for too long to a certain AP.
Can I then set up capsman 2(WiFiwave 2) in winbox? I do not need to use terminal? Thanks
Yes.
Did so for lab setup on Hex and for a customer on RB5009 (hence the lab setup).
Thank you. I still live in idea the capsman 2 is only via terminal. I have not seen any info in ROS log etc.
Could you please share more information?
For this I do not need capsman…it is in WiFi setting of each WiFi interface
If you use capsman, it should be specified on the capsman controller since the radio will be controlled there.
Actually what I’m testing is:
-
on Router:
/interface wifiwave2 capsman set ca-certificate=auto certificate=auto interfaces=(Bridge or Management VLAN) require-peer-certificate=no upgrade-policy=(none or suggest-same-version) enabled=yes -
on APs:
/interface wifiwave2 cap set caps-man-addresses=(192.168.88.1, not mandatory) caps-man-names=(Router, not mandatory) discovery-interfaces=(Bridge or Management VLAN) enabled=yes -
on Both:
/interface wifiwave2 security set [find] ft=yes ft-over-ds=yes
they must use a wired connection.
And where do you set SSID, channel, frequency, security, … ?
yes
In my case are 2/3 APs configured as “stand-alone” with all the settings.
No need to distribute the provisioned configuration.
Interesting …
So everything which capsman is able to do from the beginning (centralized configuration), you’re not using?
What is the advantage of doing this ? For what purpose ?
There is no real advantage and probably is not suggested, it’s just because APs are working with no issue (except for all the recent troubles that we are all fighting with) and I’m only interested in 802.11r (Roaming).
I’m collecting info from my tests that will be reported in a post.
Why do you not use standard capsman feature? To be honset Im only interested in fast forward over distribution system or how they call it.. FF over DS. I have only two AP so I can easily to set them up.
We are probably trying to achieve the same goal… have FT over DS working
According to the https://help.mikrotik.com/docs/display/ROS/WifiWave2, CAPsMAN is required to get roaming working, as APs need to be managed by the same instance of RouterOS:
For a client device to successfully roam between 2 APs, the APs need to be managed by the same instance of RouterOS. For information on how to centrally manage multiple APs, see CAPsMAN
With configuration according to the docs, plus ft=yes and ft-over-ds=yes, I managed to get client to successfuly roam. Checked logs, and there are following entries:
22:01:52 wireless,info 28:3A:4D:XX:XX:XX@wifi-5G roamed to 28:3A:4D:XX:XX:XX@2G-other-AP1, signal strength -38
22:07:03 wireless,info 28:3A:4D:XX:XX:XX@2G-other-AP1 roamed to 28:3A:4D:XX:XX:XX@5G-other-AP1, signal strength -61
The second roam is after DFS channel availability check was completed, and interface with 5G radio turned on.