Skip to content

Customers and callers drop while walking between APs.

802.11k, v and r are three small standards that together make 'fast roaming'. K tells clients which neighbour APs exist, v helps steer which one to pick, r hands over without a full re-auth. For callers and people walking around with a laptop, this is the difference between a smooth day and broken calls.

Try this first

  1. 1Turn 802.11k and v on for every SSID, almost always free of side effects and helps modern clients straight away.
  2. 2Only enable 802.11r (Fast Transition) on the staff SSID, not on guest: older clients (Windows 10 with old drivers, some IoT) cannot connect once FT is on.
  3. 3On WPA2-Personal FT is sometimes flaky, on WPA2-Enterprise / WPA3-Enterprise it is solid. Pilot first on a test SSID.
  4. 4Keep all APs on identical firmware and in the same controller group, FT does not work across stand-alone APs.
  5. 5Measure roaming with a phone pinging the gateway, you can see the gap when FT is missing (1-2s) versus present (<100ms).

When to bring us in

You run push-to-talk or medical gear that demands sub-50ms roaming: 802.11k/v/r is the starting point, but you also need a measured cell-overlap design with a Wi-Fi partner.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.