802.11k and 802.11r on Ubiquiti UniFi: fast roaming settings and deployment checklist

Yes, UniFi supports fast roaming. In UniFi Network, the Fast Roaming option enables 802.11r, and BSS Transition enables 802.11v. UniFi access points handle 802.11k neighbour reports without a dedicated toggle. Enable all three on voice and video staff networks that use 802.1X. Test legacy devices first, and pair the standards with sensible transmit power and minimum RSSI.

What do 802.11k, 802.11r and 802.11v actually do on UniFi?

Roaming is a client decision. The phone, scanner or laptop chooses when to leave one access point (AP) and join another. The AP cannot force a well-timed roam. It can only give the client better information, a faster handover, or a firm push. The three IEEE amendments each cover one of those jobs.

Does UniFi support 802.11k?

Yes. 802.11k (radio resource management) lets an AP send a client a neighbour report. The report lists nearby APs and their channels. With that list, the client scans a few known channels instead of sweeping every channel in both bands. A shorter scan means a quicker roam decision and less time off-channel during a call.

In UniFi Network, 802.11k is not exposed as a standalone switch in the way Fast Roaming and BSS Transition are. Behaviour can differ by firmware. Confirm it on your own site with the verification steps later in this guide, rather than assuming.

What does fast roaming do in UniFi?

The UniFi Fast Roaming setting enables 802.11r, which IEEE calls Fast BSS Transition (FT). It shortens the security handshake when a client moves between APs on the same network.

This matters most on networks that use IEEE 802.1X. That is the port-based access control standard in which each device proves its identity to a RADIUS server, the service that checks credentials, using EAP (Extensible Authentication Protocol). Without FT, every roam can trigger a full EAP exchange with that server. If the server sits in the cloud, the round trip adds delay at the worst moment, mid-call.

With FT, the keys needed for the next AP are derived in advance. The client completes the move in a handful of frames. On a WPA2-Personal or WPA3-Personal network the gain is smaller, because the pre-shared key handshake is already short.

What does BSS transition do in UniFi?

The UniFi BSS Transition setting enables 802.11v BSS Transition Management. The AP can send a client a request that says, in effect, "a better AP is available, here is the list". The client may accept or ignore it. This makes 802.11v a polite nudge, not an eviction. It is also the mechanism that lets band steering and load balancing work with the client instead of against it.

How the UniFi settings map to the standards

UniFi Network setting	IEEE standard	What it does	Enable for voice and video?	Legacy lockout risk
Fast Roaming	802.11r (Fast BSS Transition)	Pre-derives keys so the client re-authenticates in a few frames when it roams	Yes, on 802.1X staff networks	High: some older drivers fail to join an SSID that advertises FT
BSS Transition	802.11v (BSS Transition Management)	AP suggests a better AP; the client decides	Yes, on every staff network	Low: clients that do not understand it ignore it
No dedicated toggle	802.11k (neighbour reports)	Gives the client a short list of nearby APs to scan	Yes, verify it is active	Low: unsupported clients scan normally
Minimum RSSI	Vendor feature, not an IEEE standard	AP disconnects clients whose signal falls below a threshold	Only where cell overlap is proven	Medium: devices at the coverage edge can loop on and off
Band Steering	Vendor feature, not an IEEE standard	Encourages dual-band clients towards 5 GHz	Yes, in "prefer" rather than "force" style modes	Medium: some single-band or older clients join slowly
WPA3 with PMF required	IEEE 802.11w within WPA3	Protects management frames; mandatory for WPA3	Yes, where every device supports it	High: pre-WPA3 devices cannot join

What do you need before you start on a multi-AP UniFi site?

Fast roaming settings are quick to change. The preparation is what decides whether they help or hurt.

A survey and a coverage target

You need proof that cells overlap. Roaming standards cannot fix a coverage gap. Cisco's voice over WLAN design guidance targets -67 dBm or better at the cell edge for voice. Many enterprise designs use that figure. Without a predictive or walk survey, you are setting thresholds blind.

A device inventory

List every device class on each SSID: phones, VoIP handsets, barcode scanners, payment terminals, printers, smart TVs and building sensors. Note the operating system and driver or firmware version where you can. Older printers, embedded scanners and building management sensors are the usual casualties of 802.11r. You want to know which ones they are before the change, not from the helpdesk queue afterwards.

Clarity on authentication

Know whether each SSID uses WPA2/WPA3-Personal or WPA2/WPA3-Enterprise with 802.1X. Fast Roaming earns its place on Enterprise networks. If you are moving staff from a shared password to per-person identity, settle that design first. Our guide on how to enable single sign-on covers the identity side.

A test window and a rollback plan

Change one SSID at a time, out of hours, with a named device set ready to test. Record the current settings so you can revert in minutes.

How do you set up fast roaming on UniFi?

The order matters. Fix the radio layer first, then add the roaming standards. Turning on 802.11r over a badly tuned RF design only speeds up roams to the wrong AP. Ubiquiti's own UniFi documentation holds the current menu locations for each setting. This checklist covers the decisions.

Step 1: right-size transmit power

High AP transmit power is the most common cause of sticky clients. A distant AP at full power still looks strong to the client, so the client stays. The client's own radio is usually weaker than the AP's, though. The AP hears the client poorly while the client hears the AP well. That asymmetric link drives retries and choppy audio.

• Avoid running every AP at maximum power in dense layouts.
• Set 2.4 GHz lower than 5 GHz, because 2.4 GHz travels further through walls. A gap of 3 to 6 dB is common in enterprise designs.
• Re-check coverage at the cell edge against your -67 dBm voice target after each change.

Step 2: settle channels and channel width

Use narrower channels on 5 GHz in dense sites. 20 MHz or 40 MHz gives more non-overlapping channels than 80 MHz. If you use DFS channels, radar detection can force an AP to change channel and drop clients mid-shift. Our DFS radar event diagnostics checklist explains the pattern. The same logic applies on UniFi.

Step 3: set band steering

Use a mode that prefers 5 GHz rather than one that forces it. Forcing can leave 2.4 GHz-only devices struggling to join. Keep 2.4 GHz available on SSIDs that serve legacy equipment.

Step 4: enable BSS Transition

Turn on BSS Transition on every staff SSID. It is low risk, because clients that do not support 802.11v ignore the requests. It also makes band steering and minimum RSSI behave more gracefully.

Step 5: enable Fast Roaming on 802.1X staff SSIDs

Turn on Fast Roaming for the SSIDs that carry voice and video over WPA2/WPA3-Enterprise. Then test every device class from your inventory before the change goes live.

If any device fails to associate, do not turn Fast Roaming off for everyone. Move those devices to a separate SSID without FT. Better still, give them their own VLAN, a virtual network segment, so the legacy SSID cannot reach staff systems.

Step 6: set minimum RSSI last, and gently

Minimum RSSI tells the AP to disconnect a client once its signal drops below a threshold. It is blunt. The client is kicked off, not guided across. Set it only where your survey proves overlapping coverage. Start a few dB below your cell-edge design figure, not at it. Test at the edge of the building, in lifts and stairwells, and at the car park door.

Decision matrix: what to enable by situation

Your situation	Fast Roaming (802.11r)	BSS Transition (802.11v)	Minimum RSSI	Band steering
Staff voice handsets on WPA2/WPA3-Enterprise	On	On	On, a few dB below the cell edge	Prefer 5 GHz
Staff laptops and tablets, video calls, Enterprise	On	On	On, conservative	Prefer 5 GHz
Shared-password staff network, mixed devices	Off until devices are tested	On	Off	Prefer 5 GHz
Legacy scanners, printers and sensors	Off, on a separate SSID	On	Off	Off, keep 2.4 GHz
Visitor network with a captive portal (web login page)	Off	On	Off	Prefer 5 GHz
Open-plan venue with sparse AP coverage	On if Enterprise	On	Off until coverage is fixed	Prefer 5 GHz

How do you check roams in the UniFi client history?

Settings mean nothing until you see roams happen. Use three checks, from quickest to most detailed.

Walk test with a live call

Take a representative handset on a voice or video call. Walk a fixed route that crosses several AP cells. Listen for gaps and note the time of each one. Repeat with each device class that matters: the housekeeping handset, the store scanner, the manager's laptop.

Read the client history

UniFi Network keeps a connection history for each client. For your test device, it shows which AP it joined and when it moved, along with signal strength. Look for three patterns:

• Roams at the right place. Each move between APs should happen near the cell boundary, not 30 metres past it.
• Roams, not disconnects. A disconnect followed by a reconnect means the client lost the network rather than roaming. That points to a coverage gap or a minimum RSSI threshold set too high.
• Ping-pong. Rapid moves back and forth between two APs suggest overlapping cells at similar power. Lower the power on one, or relax minimum RSSI.

Compare the history from before and after your change on the same route. That comparison is your evidence.

Confirm the standards on the air

To prove 802.11r and 802.11k are working, take a packet capture on a laptop near the APs. In the IEEE 802.11 standard, an FT roam uses authentication algorithm number 2 (Fast BSS Transition) rather than Open System. Neighbour report requests and responses appear as radio measurement action frames. If you see full EAP exchanges on every roam, FT is not in use for that client.

For staff networks where identity matters as much as speed, our guide to resolving roaming issues in corporate WLANs goes deeper into client-side diagnostics.

Why do devices stick to one UniFi access point, and how do you fix it?

Sticky clients are rarely a single fault. Work through the causes in this order.

Transmit power is too high

The client still sees a strong signal from the AP it joined first, so it never looks for another. Reduce power so cells overlap rather than blanket the site.

The client has no hints

Without 802.11k neighbour reports and 802.11v transition requests, the client relies on its own scanning. Many devices only scan once the signal is poor. Enable BSS Transition and confirm neighbour reports are reaching the client.

The client vendor sets a low roaming threshold

Each operating system chooses its own roam trigger. Apple publishes its roaming behaviour for iOS and iPadOS in its platform deployment documentation. Many Android and embedded devices do not publish theirs. Where a device will not move, a gentle minimum RSSI setting gives you a last resort.

Coverage gaps hide behind sticky behaviour

If the client history shows a disconnect rather than a roam, the client had nowhere to go. Fix the gap with an AP move or an extra AP. Do not tighten minimum RSSI.

Legacy devices dropped after enabling Fast Roaming

This is lockout, not stickiness. Some older drivers cannot parse the FT information that the AP advertises, so they fail to join at all. Move them to a non-FT SSID. The same applies to devices that cannot use the PMF (protected management frames) that WPA3 requires.

What does it cost, and what do you get back?

These roaming settings come with UniFi Network. Ubiquiti does not sell them as a separate licence. The real cost is engineering time: a survey, a device inventory, a test window and a re-test. On a single site with a few dozen APs, plan for a day of preparation and an evening change window. Then budget a follow-up walk test.

The return shows up in fewer dropped calls, fewer "the WiFi is down" tickets, and staff who stop working around dead spots. The scenarios below are illustrative, built from common UniFi deployment patterns. Measure your own baseline before and after.

Worked scenario: a 200-room hotel

Situation. Housekeeping and maintenance teams used VoIP handsets on a WPA2-Enterprise staff network across 10 floors of UniFi APs. Calls dropped in lift lobbies and at corridor ends. Every AP ran at high power, and 2.4 GHz cells covered several rooms each.

What was done. The team cut 2.4 GHz power below 5 GHz and lowered 5 GHz power in corridors. They enabled BSS Transition on all staff SSIDs and Fast Roaming on the handset SSID only. Two room-sensor models failed to join with FT enabled, so the team moved them to a separate SSID on their own VLAN. Minimum RSSI went on last, a few dB below the -67 dBm design edge.

Outcome. On the same walk route, the handset's client history went from 6 disconnects in 10 minutes to zero, with every floor transition recorded as a roam. Handset drop reports from supervisors stopped within the first fortnight. For more on staff connectivity in this vertical, see our hotels page.

Worked scenario: a 40-store retail chain

Situation. Each store ran 4 to 6 UniFi APs. Staff tablets handled stock checks and video training. After a head-office change enabled Fast Roaming across every SSID, handheld barcode scanners on older firmware stopped connecting in 9 stores.

What was done. The team rolled back Fast Roaming on the shared SSID within the hour. They then created a scanner SSID without FT and kept Fast Roaming on a tablet SSID using 802.1X. Every new device model now goes through a one-store pilot before chain-wide rollout.

Outcome. Scanner connection failures returned to zero. Tablet client histories showed clean roams between the shop floor and the stockroom APs, the area where video calls had previously frozen. See our retail page for how staff and shopper networks sit side by side.

Where Purple fits

Fast roaming is only as good as the identity behind it. Purple Staff WiFi uses Identity-Based Networks. Each employee signs in once with Microsoft Entra ID, Okta or Google Workspace, rather than sharing a password that leaks when someone leaves. Purple is hardware-agnostic and works as a cloud overlay. It runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet.

Joiners, movers and leavers are handled through the identity provider. When someone leaves, Purple revokes their access without a password change for everyone else. Purple runs at 80,000+ live venues (Purple's own data).

For automatic, profile-based connection, SecurePass uses WPA2/WPA3-Enterprise and Passpoint. Passpoint, also called Hotspot 2.0, lets a device join a trusted network automatically. Check that your APs meet the requirements in our security and hardware compatibility article before you enable it. The SecurePass FAQ covers enrolment and how SecurePass runs alongside an existing captive portal.

The same roaming principles apply in healthcare, where clinical staff carry handsets between wards. They also apply on trains, where APs hand over constantly along a carriage.

Frequently asked questions

Does UniFi support 802.11k?

Yes. UniFi access points support 802.11k neighbour reports, which give a client a short list of nearby APs to scan before it roams. UniFi Network does not present 802.11k as a standalone toggle in the way it presents Fast Roaming (802.11r) and BSS Transition (802.11v). Confirm it is active on your firmware with a packet capture. Look for radio measurement action frames containing neighbour report requests and responses between your test client and the AP.

Should I enable fast roaming on UniFi for staff voice and video?

Yes, on staff SSIDs that use WPA2/WPA3-Enterprise with 802.1X. Without 802.11r, each roam can trigger a full exchange with the RADIUS server, which adds delay mid-call. ITU-T G.114 recommends keeping one-way voice delay under 150 ms, so that extra delay matters. Test every device class first. Some older drivers fail to join an SSID that advertises Fast BSS Transition, so keep those devices on a separate SSID.

Which devices does 802.11r lock out on UniFi?

Older devices whose drivers cannot handle Fast BSS Transition information may fail to join the SSID entirely. The usual culprits are older printers, embedded barcode scanners, payment terminals, building sensors and some older laptop drivers. The fix is a separate SSID without Fast Roaming, ideally on its own VLAN, rather than disabling the feature for every device. Pilot every new device model at one site before you roll it out across the estate.

Do I need new access points to get fast roaming on UniFi?

No, not for current UniFi APs. Fast Roaming and BSS Transition are settings in UniFi Network, not separate licences. What you may need is RF work: lower transmit power, narrower channels and occasionally an extra AP to close a coverage gap. Older or discontinued models can have limited feature support. Check Ubiquiti's documentation for your specific AP models before you plan the change window.

Does Purple Staff WiFi work on Ubiquiti UniFi access points?

Yes. Purple is hardware-agnostic and runs as a cloud overlay on Ubiquiti UniFi, as well as Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Cambium, Extreme and Fortinet. Staff authenticate with Microsoft Entra ID, Okta or Google Workspace through Identity-Based Networks. Your existing UniFi roaming settings stay in place. For SecurePass, check the Passpoint requirements in our security and hardware compatibility article before you enable it.

How long does it take to tune roaming on a multi-AP UniFi site?

For a single site with a few dozen APs, plan a day of preparation and an evening change window. Preparation covers the survey review and device inventory. The change window covers transmit power, band steering, BSS Transition, Fast Roaming and minimum RSSI. Follow up with a walk test and a comparison of client histories a week later. Multi-site estates go faster once one site becomes your tested template.

Is minimum RSSI on UniFi safe to use in a busy venue?

Yes, but only where your survey proves overlapping coverage. Minimum RSSI disconnects a client below a set signal level rather than guiding it across. If no other AP is in range, the client simply drops. Set it last, a few dB below your cell-edge design figure, then walk the edges of the building. If client history shows repeated disconnects rather than roams, relax the threshold or close the coverage gap.