Mac drops Wi-Fi or sticks to a far node on mesh Wi-Fi

A Mac decides itself when to move to another mesh node. The mesh system can only suggest a move. When the two disagree, the Mac drops for a moment or stays on a node far away.

Fix this with your agentCopies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: Mac drops Wi-Fi or sticks to a far node on mesh Wi-Fi. Read https://kilobat.app/guides/mac-mesh-wifi-roaming.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: macOS 14 Sonoma and later.Checked: 7 November 2026

When this helps

Your Mac drops Wi-Fi for a few seconds when you carry it to another room.
Your Mac stays on the node downstairs while the node in your room is unused.
Wi-Fi is slow in a room with its own mesh node.
The drops started when you added a node or turned on a roaming feature.

How a Mac roams

Apple says that a Mac stays on its access point until the signal drops to −75 dBm. It then looks for another access point on the same network.

The new access point must be 12 dB stronger. So a Mac at −75 dBm looks for −63 dBm or better.

macOS scores candidates by channel use, client count and signal. It prefers newer Wi-Fi standards and wider channels.

802.11k. Gives the Mac a list of nearby access points, so the roam scan is faster. Apple says that Macs with Apple silicon support it, and Intel-based Macs do not.
802.11r (Fast BSS Transition). Makes the move to the new access point faster. Apple says that Intel-based Macs do not support it, but work on networks that use it.
802.11v. Lets the network suggest another access point. Macs with Apple silicon support it. Intel-based Macs do not.

FRITZ! and TP-Link say that their steering uses 802.11k and 802.11v. Apple says that Intel-based Macs do not support these standards.

Why the Mac drops or stays on a far node

The Mac roams late. A signal of −70 dBm is still above the −75 dBm trigger. The Mac stays, although a closer node is stronger.
The router pushes the Mac off. Some systems disconnect a client with a weak signal. Ubiquiti says that devices can then refuse to join that access point.
Settings differ between nodes. Apple says that all routers and access points need the same settings. Different names or security modes make devices connect unreliably.
A fast-roaming setting the client does not handle. TP-Link says that some clients fail to connect, or disconnect, when Fast Roaming (802.11r) is on.
A changing private Wi-Fi address. Some router settings for one device use its MAC address. Apple says that the Rotating setting changes the address every two weeks.

Check how the Mac roams

Hold the Option key and click the Wi-Fi icon. Note the network name and the signal.
Open Terminal. Show the current channel, band and signal.
```
system_profiler SPAirPortDataType
```
Sign in to the mesh app. Find the Mac in the client list. Note which node it uses.
Walk to another room with the Mac. Check again after a minute.
Compare the security setting of every node. All must be the same.
Find out if your Mac has Apple silicon. Choose Apple menu > About This Mac and look at Chip.

Fix it

Install the latest firmware on the mesh system. Install the latest macOS update.
Use one network name, one password and one security mode on every node.
Use WPA3 Personal or WPA2/WPA3 Transitional. Apple recommends these modes.
Give nodes that are near each other different channels, if your system lets you choose.
Set the private Wi-Fi address of the Mac to Fixed. Choose System Settings > Wi-Fi, then click Details.
If a node's signal reaches too far, move the nodes so that they overlap less.
To test, turn off one roaming or steering feature at a time. Use the brand list below.
To keep a desk Mac on one node, use your system's setting for this, if it has one.
If the Mac stays on a far node, turn Wi-Fi off and on. The Mac then joins the strongest node it hears.

Settings by mesh system

Menus change with firmware, so names can differ slightly on your router.

TP-Link Deco. TP-Link says that Fast Roaming (802.11r) can stop some clients from connecting. Turn it off for a test. To stop one device roaming, open the device in the Deco app and turn off Mesh Technology. Some models can fix a device to one Deco with Specified Connection. See the Deco guide.
NETGEAR Orbi. On Orbi models such as the RBR50, go to ADVANCED > Advanced Setup > Wireless Settings. Clear or select Enable Fast Roaming, then click Apply. See the Orbi guide.
NETGEAR Nighthawk. Smart Connect is on by default and picks the band. To split the bands, go to BASIC > Wireless and clear Enable Smart Connect. See the Nighthawk guide.
eero. In the eero app, go to Settings > Advanced networking. Client steering is in the Wireless section. eero says that turning it off can help compatibility. See the eero guide.
Google Nest Wifi. All bands share one name, and band steering picks the band. Google gives no switch to turn steering off. See the Nest Wifi guide.
ASUS AiMesh. ASUS has a help page for Macs that drop after roaming between AiMesh nodes. It says to update macOS, add the Mac to the Roaming Block List, or turn off Smart Connect. See the ASUS guide.
ASUS Roaming Block List. Open http://www.asusrouter.com/Advanced_Roaming_Block_Content.asp, set it to Yes and add the Mac. ASUS says that the router must restart. The Mac still roams on its own.
Ubiquiti UniFi. Each WiFi network has Fast Roaming (802.11r), BSS Transition and Band Steering. Ubiquiti says that very old devices can have problems with BSS Transition. Minimum RSSI can stop devices from joining. See the UniFi guide.
Linksys Velop. In the web interface, the WiFi Settings Advanced tab has Client Steering and Node Steering. Linksys says that both are off by default. See the Linksys guide.
FRITZ!Box with FRITZ! Mesh. Mesh Wi-Fi steering needs one name for both bands. Under Wi-Fi > Wi-Fi Network, edit a device to see if it shows 11k and 11v. FRITZ! says that devices without them cannot be moved to another access point. See the FRITZ!Box guide.
FRITZ!Repeater for one device. FRITZ! suggests a separate name for a repeater when a device lacks 11k and 11v. Turn off Adopt settings enabled on the repeater, then set its own name.
Xfinity Gateway with Extenders. Xfinity says that its extenders need one network name and password. Devices then connect to the best access point automatically. See the Xfinity guide.
Verizon Fios. The Self-Organizing Network (SON) is on by default, and Verizon lists automatic band steering. In the router at 192.168.1.1, go to Wi-Fi > Primary Network to turn SON off and manage each band. See the Fios guide.
BT Smart Hub and Complete Wi-Fi. BT says that the Smart Hub 2 cannot split its network name, because it works with Complete Wi-Fi. The older Smart Hub has a Separate bands switch. See the BT guide.
Sky Max Hub with a Pod. Sky says that some devices do not switch between the hub and an extender. Turn Wi-Fi off and on, and the device joins the stronger one. See the Sky guide.

With Kilobat

List the nodes of your network, with signal and bands. The current node is marked.
```
kilobat wifi nodes
```
Give a node a name, such as Office. Use the ID from the list.
```
kilobat wifi nodes name <id> Office
```
Move the Mac to the closer node. Wi-Fi drops for a few seconds.
```
kilobat wifi reconnect
```
In the app, Health says when the Mac stays on a far node, with the signal of both nodes.
For a notification, choose Settings > Notifications in Kilobat. Turn on Tell me when the Mac stays on a far Wi-Fi node.
Show each roam with the old and new access point.
```
kilobat outages
```
Node names need the Kilobat app with Location access. macOS shows access point addresses only to such apps.

Questions

Should I turn off 802.11r?

Try it if the Mac drops right after a roam. Ubiquiti recommends Fast Roaming on. TP-Link says that some clients fail with it. Test one change at a time.

Why does my Intel-based Mac ignore steering?

Apple says that Intel-based Macs do not support 802.11k, 802.11r or 802.11v. They roam only by their own signal rules.

Does a private Wi-Fi address break mesh roaming?

Apple's Fixed setting keeps one address per network. Rotating changes it every two weeks, so router settings for that device stop matching.

Sources

Checked on 7 November 2026.