I did some tests with CoA and 802.11r and came to a different conclusion compared to what is stated in the documentation *and* on the dashboard.
In my network (MR 31.1.5.1), I have an SSID that is configured with 802.1X and both CoA and 802.11r.
The dashboard states that 802.11r would be disabled:
![KarstenI_0-1737993792253.jpeg KarstenI_0-1737993792253.jpeg](https://community.meraki.com/t5/image/serverpage/image-id/41653iE7D1D57394AEB4E8/image-size/medium?v=v2&px=400)
And the documentation states that 802.11r gets disabled:
![KarstenI_1-1737993859108.jpeg KarstenI_1-1737993859108.jpeg](https://community.meraki.com/t5/image/serverpage/image-id/41655i7F569CE3691B60E4/image-size/medium?v=v2&px=400)
But in reality, 802.11r is still announced:
![KarstenI_2-1737993969031.jpeg KarstenI_2-1737993969031.jpeg](https://community.meraki.com/t5/image/serverpage/image-id/41656iDD99CCAA4F8C206B/image-size/medium?v=v2&px=400)
And Roaming is done based on 802.11r:
![KarstenI_3-1737994567180.jpeg KarstenI_3-1737994567180.jpeg](https://community.meraki.com/t5/image/serverpage/image-id/41657iAACD6EF11B4A778A/image-size/medium?v=v2&px=400)
In the RADIUS capture, I only see the initial communication but no further exchange when roaming.
CoA is indeed not working as it should:
- It works when the Client is connected to the AP that made the initial connection (also after a roam back).
- It doesn't work on other APs. When the client is connected to a different AP, the original AP gets the CoA request and answers with CoA-NAK, "Session-Context-Not-Found".
The misleading statements in the dashboard and the documentation should be corrected. Or even better, CoA should be implemented in a way that it works. 😉
If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.