Wi-Fi Drops When You Walk Between Rooms: Roaming Explained

If Wi-Fi drops when moving between rooms, you are likely seeing a roaming handoff. A phone or laptop is connected to one radio at a time, even when every router, extender and mesh node uses the same network name. The client decides when to leave, and it often waits too long.

A good handoff can take tens of milliseconds with fast roaming. A normal re-association may take 1–3 seconds; a full drop and new address can cost 5–20 seconds. That is enough to interrupt a call or podcast.

Understand the sticky-client problem#

Clients avoid scanning because it consumes time and battery. They therefore cling to the radio they first joined until signal has degraded to roughly -70 to -75 dBm, even if a closer radio is already better. The device can look connected while the old link retries repeatedly.

802.11k helps a client learn which nearby radios exist; 802.11v suggests a better one; 802.11r speeds authentication during a transition. They help only when the router system and client support them. They do not make a bad physical layout good.

Put the handoff in a usable place#

Neighboring coverage should meet around -67 dBm, not at the last usable edge. That gives the client a strong old and new link in a hallway or landing, where a short handoff is harmless. If coverage meets at -80 dBm, the device waits until failure before it has a reasonable alternative.

Place nodes with healthy backhaul first. A mesh node or extender cannot offer good roaming if its own parent link is weak. Mesh node placement covers overlap and hops; same SSID or separate SSIDs covers the network-name choice.

Use the same security settings across nodes. Keep 5 GHz available where it has enough signal, and do not solve a moving-phone problem by placing an extender deep in a dead room. An open, router-side midpoint usually creates the better boundary. The band guide explains why a busy 2.4 GHz network can make the transition worse.

Diagnose before relocating hardware#

1. Walk the usual route during a call and identify the exact point where audio breaks.
2. Toggle Wi-Fi off/on at that point. If it immediately improves, a sticky client is likely.
3. Test the same route beside a different device if possible; client behavior varies.
4. Check whether the issue follows a microwave, metal cabinet or other local interference source. Home interference sources can cause a similar event.
5. Move the second radio toward the router or raise it until coverage overlaps around -67 dBm, then retest.

If every device loses service in the same place, check a true dead zone or bad backhaul rather than only client roaming. A fixed desk or TV is often better served by Ethernet or MoCA than by optimizing handoffs.

Use Range Up to test the boundaries before relocating a node, and consult the complete Wi-Fi extender placement guide for the radio position itself.

Separate roaming from ordinary coverage loss#

Roaming requires two radios. If the home has one router and the connection simply fades as you walk away, it is not a handoff; it is a coverage problem. If the device becomes slow near a second radio but recovers immediately when Wi-Fi is toggled, it is more likely a sticky client. This distinction matters because adding a second weak radio to a one-router house can create a roaming problem without fixing the original path.

Do not make per-device roaming settings your main strategy. Phones and laptops vary widely, and some settings are unavailable. A physical overlap near -67 dBm and compatible router features are the durable solution. If a separate extender has unreliable handoffs, giving it a distinct SSID can be temporarily useful for diagnosis, but it moves the decision back to the person holding the phone.

For calls that remain poor while stationary, test jitter and loss rather than chasing roaming behavior. The video-call guide provides the router-ping test.

Check the nodes before blaming the phone.

Open the mesh or router status page and confirm that every node is connected to the parent you expect, on a healthy link. A node with a marginal wireless backhaul can create a coverage island that looks strong to the phone but stalls the moment traffic leaves it. Reposition that node toward the router before adding another node farther away.

Keep firmware current across the router and mesh units, then use the same network name, password and security mode where the system vendor recommends it. Mixed security modes, duplicate network names from an old router or separate DHCP servers can cause behavior that looks like roaming but is really failed authentication or address assignment.

Walk a deliberate test route at normal pace. Pause for a minute in each room and note whether the client switches, then make a call while crossing the intended overlap. A well-designed network may show the handoff in diagnostics yet produce no audible break. The goal is not to force a specific radio at every step; it is to keep the user experience stable.

If a particular device keeps making the wrong decision while others work, accept that client behavior varies. A temporary distinct SSID can help prove the diagnosis, but moving the coverage boundary is the scalable repair for everyone in the house.