WiFi Roaming Protocols Explained: 802.11r, 802.11k, and 802.11v

Walk from your kitchen to your home office while on a video call and you may notice a brief freeze, a stutter, or a dropped connection. That interruption is almost never your ISP’s fault — it’s the moment your device slowly realizes it should switch from one access point or mesh node to another. Three WiFi standards were designed to make that handoff nearly invisible: 802.11r, 802.11k, and 802.11v. Together they’re often called the “WiFi roaming trio,” and understanding what each one does explains a lot about why some mesh systems feel seamless while others stutter.

The Problem: Sticky Clients and Slow Roaming

In a standard WiFi network, your device — not the router — decides when to switch access points. Devices tend to be conservative, clinging to the access point they originally connected to even as the signal weakens. This “sticky client” behavior means a phone might be associated with the downstairs node while standing five feet from the upstairs node, getting a poor signal when a much better one is available.

When a device finally does decide to roam, the standard authentication process is slow. Without fast-roaming amendments, a device must perform a full 802.1X or WPA2 four-way handshake with the new access point, which can take 500–800 milliseconds or more. For most web browsing that’s invisible, but for a VoIP call, a video conference, or a competitive game session, it’s a noticeable glitch. See our related guide on WiFi roaming basics for a broader overview of how devices decide when to switch.

802.11k: Giving Clients a Map

802.11k, ratified in 2008 and rolled into the base 802.11 standard in 2012, solves the problem of a client not knowing where to roam to. Before 802.11k, a device that decided to roam had to scan every channel on every supported band to find neighboring access points — a process that takes time and means the radio is off its current connection while scanning.

With 802.11k, your access points share Neighbor Reports — structured lists of nearby APs including their BSSID, channel, and signal strength — directly with connected clients. Instead of scanning blindly, your device consults this map and immediately knows which APs are available and on which channels. This dramatically reduces the time between “I should roam” and “I am connected to the better AP.”

Think of 802.11k as the GPS that tells your device where other access points are. Without it, roaming is like navigating without a map: possible, but slower and less reliable.

802.11v: Letting the Network Steer Clients

802.11k helps clients make better decisions, but 802.11v goes further by giving the network a voice in those decisions. The 802.11v amendment, also called BSS Transition Management, allows an access point to send a client a polite suggestion (a BSS Transition Management Request frame) to move to a different AP.

This is particularly useful for load balancing. If one mesh node is overloaded with 20 devices and a neighboring node has only three, the overloaded node can use 802.11v to nudge clients toward the quieter node. It’s also used when a client is holding onto a weak signal: the AP can detect that the client’s RSSI is degrading and suggest a handoff before the connection deteriorates further.

Crucially, 802.11v requests are just suggestions — clients can ignore them. In practice, most modern operating systems honor these requests, but older or poorly implemented drivers may not. This is one reason enterprise-grade mesh systems with centralized controllers tend to roam more predictably than consumer gear: the controller can be more aggressive about 802.11v steering.

802.11r: Making the Handoff Fast

Once a device decides to roam and knows where to go, 802.11r — known as Fast BSS Transition (FT) — dramatically reduces the time the handoff actually takes. Without 802.11r, roaming requires a full re-authentication from scratch, including exchanging the Pairwise Master Key (PMK) and completing a new four-way handshake. The entire sequence can take 500–800ms, long enough to drop a VoIP call or cause a video call to freeze.

802.11r pre-distributes the necessary key material across all access points in the same Mobility Domain — a group of APs that share the same SSID and roaming infrastructure. When your device first authenticates to the network, a master key (the R0 Key) is generated. Derivatives of that key (R1 Keys) are pushed to all neighboring APs. When you roam, the new AP already holds the key it needs, and re-authentication is reduced to a two-step “abbreviated handshake” that completes in under 50 milliseconds — a ten-fold improvement.

FT Over the Air vs. FT Over DS

802.11r has two operational modes. FT Over the Air performs the abbreviated handshake directly between the client and the target AP over the wireless link. FT Over DS (Distribution System) routes that exchange through the wired backhaul controller, reducing RF airtime during the handoff but requiring reliable low-latency backhaul between APs. Most home mesh systems use FT Over DS when wired backhaul is present, and FT Over the Air when nodes are wirelessly connected.

How They Work Together

The three protocols are designed to be complementary:

• 802.11k gives the client a neighbor map so it knows which AP to target.
• 802.11v lets the network push the client toward the right AP at the right time.
• 802.11r makes the actual transition fast once the decision is made.

A network running all three can hand off a device from one AP to another in under 50ms, with no visible interruption for voice or video applications. A network without any of them may take several seconds to complete a roam — if it ever completes one before the call drops.

Which Home Routers Support 802.11k/v/r?

Support varies significantly across consumer hardware, and marketing claims don’t always reflect what’s actually implemented in firmware.

• Eero (Amazon): Solid 802.11k/v/r implementation. One of the better consumer mesh systems for seamless roaming, according to independent wireless testing.
• TP-Link Deco: Most Deco models advertise all three protocols. The Deco M9 Plus was observed making heavy use of 802.11k neighbor reports in testing, though 802.11v steering behavior can be inconsistent.
• ASUS AiMesh: Varies by model and firmware version. Some ASUS routers (including certain XT8 configurations) lack full 802.11r support, meaning neighbor reports and BSS steering may operate but without the fast key pre-distribution that makes handoffs truly fast.
• Netgear Orbi: Orbi supports fast roaming through its Orbi-proprietary backhaul, with 802.11r enabled on the client-facing radios on most current models.
• Google Nest: Supports 802.11r and 802.11k; 802.11v implementation is present but Google does not expose details of its steering logic.

For most home users, the key question is whether the mesh system or multi-AP setup uses a single SSID with the same passphrase across all nodes. If each AP has a different network name, 802.11r cannot function at all — FT requires all APs to operate as part of the same Mobility Domain. Our guide on mesh systems vs. standalone access points explains how the management architecture affects roaming behavior.

Checking and Enabling Fast Roaming on Your Router

Most consumer mesh systems enable 802.11k/v/r automatically with no user action required. On routers running custom firmware like OpenWrt or on enterprise-grade access points (Ubiquiti UniFi, TP-Link Omada), you can verify or enable these protocols in the wireless interface settings:

• Look for “Fast Roaming,” “Fast BSS Transition,” or individual checkboxes for “802.11r,” “802.11k,” and “802.11v” in the wireless SSID settings.
• On UniFi, navigate to WiFi → [SSID] → Advanced and enable Fast Roaming. This activates all three protocols simultaneously.
• On OpenWrt, the hostapd configuration file controls each protocol with ieee80211r, ieee80211k, and bss_transition options.

If you’re troubleshooting sticky-client behavior on a Mac specifically, our guide on fixing sticky WiFi on macOS covers the client-side settings that complement these AP-side protocols.

Do Client Devices Need to Support These Protocols?

Yes. 802.11r and 802.11k require matching support on the client side. A device with an older WiFi 5 chip that predates 802.11k will not request or receive neighbor reports. An older WPA2-only device may have trouble with 802.11r in some deployments because a small number of older drivers mishandle FT frames, causing connection failures rather than fast handoffs.

All modern smartphones (iPhone 7 and later, Android phones from 2017 onward), MacBooks (2017+), and Windows laptops with WiFi 6 chips support all three protocols. If you experience devices that fail to connect after enabling 802.11r on a home router, the most reliable fix is to run a separate SSID without FT for legacy devices rather than disabling it globally.

The Bottom Line

802.11r, 802.11k, and 802.11v are the engineering answer to sticky clients and slow handoffs. A home network built on a mesh system or multiple access points that supports all three will hand off your phone between nodes in under 50ms — fast enough that a phone call or video conference continues without a hiccup. A network without these protocols may take ten or twenty times longer to complete the same handoff, which is why moving between rooms while on a call sometimes causes problems even when coverage looks adequate on paper. If seamless whole-home roaming is a priority, look for explicit fast-roaming support when evaluating your next mesh system or access point upgrade.