I'm trying to decide whether to turn on fast roaming across my APs, and I can't tell if it's a free win or a way to break the cheap smart plugs.
My understanding so far, so correct me where I'm wrong:
- 802.11k gives the client a list of nearby APs, so it doesn't have to scan blindly.
- 802.11v lets the AP suggest that a client move. It's a suggestion, and the client can ignore it.
- 802.11r speeds up the key handshake when moving between APs. This is the one I hear most often about breaking older devices that choke on the extra fast-transition info in the beacon.
What I haven't found is a clear answer on whether the problem is 802.11r itself or just how a given vendor implements it. Some firmware has a mixed or adaptive mode, and I'm unsure whether that really protects the old stuff or just moves the failure somewhere harder to see.
The other half is verification. "It feels faster" isn't data. My plan is to watch the connected BSSID from a Linux laptop while pinging something, then walk between APs:
while true; do
date +%T
iw dev wlan0 link | grep -E 'Connected|SSID'
sleep 1
done
In another terminal I'd run a continuous ping to the gateway and count the dropped replies at the roam. That only tells me about the laptop, though, not about phones or IoT.
So, two questions. Did turning on r/k/v break any old devices for you, and if so, which ones? And how do you check roaming from the phone side, or do you just trust the AP logs?