I have come across numerous posts and external pages discussing the support for 802.11r, and most of them suggest that it has not been implemented yet. Is this accurate, and if so, why?
I find this confusing since the chip in this router actually supports it.
Thank you for your assistance in advance.
If you go to our documentation:
https://help.mikrotik.com/docs/display/ROS/WifiWave2
@normis those standards are working only on one AP? When we will see those standrds working between more AP?
When will you support 800.11 v?
Development never stops, we are constantly working on improvements and updates in all areas.
As business never sleeps … I couldn’t resist 
Roaming between devices is already supported, if you use CAPsMAN.
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 manual
Hello @normis, Roaming between devices is a “new” feature introduced by the WifiWave2 CAPsMAN?
Any particular condition needed or following the config example will enable Roaming between Router and APs?
https://help.mikrotik.com/docs/display/ROS/WifiWave2#WifiWave2-CAPsMAN-CAPconfigurationexample:
in capsman set these settings:
ft=yes. ft-over-ds=yes
That’s great. I thought CAPSMANv2 is “just” to distribute configuration. This is great news while my brand new ax3 on my table now 
Hi Normis,
is this setting working without capsman?
For example I have 2 hap AX2 and when I set those settings on both AX2 will it help with roaming?
if you have multiple devices and need fast roaming, you need capsman. completely unrelated devices can’t teach your client to roam.
The documentation could be MUCH clearer that distributed system = capsman, but thanks for the tip.
edit: this is an incorrect assumption
Just to clarify: FT over Distribution System (ft-over-ds) ≠ CAPsMAN
The guide seems clear enough to me:
https://help.mikrotik.com/docs/display/ROS/WifiWave2#WifiWave2-SecurityProperties
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
In my case (1x hAP ax3 as CAPsMAN and 2x hAP ax2 as cAPs) FT works perfectly even without DS option actived (FT Over-the-Air), the important thing is that the cAPs, and not local wifi interface, are managed by the same instance of RouterOS with CAPsMAN.
Are you sure your ax3 is being managed by capsman? My understanding is that local radios aren’t supported.
Probably it’s not managed by CAPsMAN. But: docs say “APs need to be managed by the same instance of RouterOS” … which is true if CAPsMAN (managing remote wifiwave2 radios) runs on same ROS as local wifiwave2 interface.
CAPsMANv2 does two things, which are only loosely tied together: 1) radio interface provisioning and 2) mobility management (802.11 r/k/v/…) . Item #1 is what already CAPsMANv1 does for legacy wireless devices. Item #2 is done in conjunction with locally running instance of wifiwave2 driver (hence need for wifiwave2 driver on CHR which often doesn’t have local wireless interfaces) and CAPsMANv2 more or less provides only means of signalling between local and remote instances of wifiwave2.
Maybe MT can clarify what of 802.11r they have implemented.
Managed by one system, is not part of 802.11r AFAIK.
See other brand docs …
In need of more guidance from MT. Things like: https://www.networkcomputing.com/wireless-infrastructure/wifi-fast-roaming-simplified
Yes clarification would be good. Now that I’ve read further into it DS != capsman for sure. ft-over-ds may even make transitions slower than with just ft enabled due to the check back to the old AP.
Sorry, I said that badly… but I never wrote that hAP ax3 local wifi interfaces are managed by capsman!
I wrote that CAPsMAN is active in the hAP ax3, local interfaces are managed by the ax3 locally and CAPsMAN is used for remote cAPs.
http://forum.mikrotik.com/t/capsman-wave2-802-11r-fast-roaming-info/165034/1
The problem maybe is that you still don’t understand how CAPsMAN works for wave2, don’t worry… it works differently but it’s very simple.
I hope that @normis makes a video on this too
Create one or more configurations to use for all wifi interfaces.
Yes @mkx, that’s exactly what happens.
On hAP ax3 with CAPsMAN active all interfaces will be managed locally, remote CAP configuration is automatic thanks to the provisioning
While in remote cAPs, in my case hAP ax2, they will be managed by CAPsMAN
On hAP ax3 apply the same configuration for all interfaces, obviously for caps managed you have to use provisioning instead for local interfaces you can apply the configuration created before.
Summing up…
CAPsMAN active on hAP ax3
And CAP enabled on cAPs
With Registration menu you can see all the devices connected to the caps
As already mentioned, I can confirm that FT works perfectly.
Is that not just two capsman manages caps and a standalone wifi AP? Are you sure ft works between the capsman managed devices and the separate wifi AP?
Sorry I don’t understand what you mean…
Yes FT works, all wifi interfaces are managed by the same instance of RouterOS.