Why Your Router Isn't the Problem: The Networking Reality Behind WiFi Dead Zones

If you've ever stood in your kitchen watching a video call freeze while you had five bars in the office ten metres away, you've met a WiFi dead zone. The usual reaction is to blame the router and go buy a more expensive one. That almost never fixes it, because the router was rarely the actual bottleneck. Here's the networking reality behind dead zones, and why the fix is architectural, not "buy a bigger box." It's not about signal strength, it's about signal-to-noise and roaming A single access point radiates roughly a sphere of coverage, and that sphere gets eaten alive by physics before it gets anywhere near your back bedroom: - Standard brick veneer wall: roughly 6-10 dB of attenuation per wall - Double brick / masonry: can run 15-20+ dB - Foil-backed insulation or low-E glass: can behave almost like a Faraday cage in the 5 GHz band specifically, because the foil mesh is tuned to block wavelengths in that range Every doubling of distance from the AP costs you roughly 6 dB under free-space path loss, and every wall in the path stacks on top of that. By the time you're two rooms and a hallway away, you haven't lost "some" signal - you've often dropped below the noise floor for anything beyond basic web browsing, and gigabit-class throughput is long gone. Channel congestion is the second half of the problem Even where signal strength looks fine on a phone's little bar icon, dead zones are frequently a channel congestion problem, not a coverage problem. In the 2.4 GHz band there are only three non-overlapping channels (1, 6, 11) in most regions, and in any reasonably dense suburb you're sharing airtime with a dozen neighbouring networks all fighting for the same three channels. 5 GHz has more channels but shorter range and worse wall penetration, which is the classic trade-off. Run a WiFi analyzer (inSSIDer, WiFi Analyzer on Android, or iwlist wlan0 scan on Linux if you want to do it the hard way) and you'll often find the "dead zone" has a perfectly reasonable RSSI but terrible actual throughput because the channel is saturated. Why range extenders usually make it worse, not better The standard consumer fix - a plug-in range extender - works by receiving the signal and rebroadcasting it on the same radio. That means: - It halves your effective bandwidth, because the same radio can't receive and transmit simultaneously, so every packet effectively makes two hops on one channel. - It usually doesn't support fast roaming standards, so your devices "stick" to whichever AP they first associated with, even after you've walked closer to a stronger one - the classic "full bars but no internet" symptom. - It's a second, separate SSID or a poorly implemented same-SSID relay, and devices handle the handoff badly either way. What actually fixes it: dedicated-backhaul mesh + proper placement Real mesh systems (as opposed to a single AP plus an extender) solve this with a few specific mechanisms worth understanding if you're troubleshooting your own setup: *- Dedicated wireless or wired backhaul - * a separate radio (or Ethernet run) handles node-to-node traffic, so client bandwidth isn't shared with backhaul traffic. This is the single biggest difference between a real mesh system and a repeater. *- 802.11k/v/r - * these standards let the network (not just the client) manage roaming: .11k gives clients a neighbour report so they know what else is available, .11v lets the network suggest a better AP, and .11r (fast BSS transition) makes the handoff between APs fast enough that a VoIP call or video stream doesn't notice it happened. *- Band steering and single SSID - * clients see one network name and the system decides which radio/band each device should sit on based on real-time conditions, rather than you manually choosing a "5G" network and hoping. *- Placement that respects the physics above - * the highest-leverage fix is often not buying new hardware at all, but moving the existing AP out of a cabinet, away from a metal cabinet or fish tank, and central to the floor plan rather than jammed in a corner where the ISP's cable happens to terminate. A practical troubleshooting order Before spending money, this is roughly the order I'd check things in: - Map actual RSSI and channel utilisation room-by-room (a $0 phone app will do for a first pass). - Check AP placement against the attenuation numbers above - is it buried behind a TV unit, inside a cabinet, near a mirror or fish tank? - Check for channel congestion, not just weak signal - a "strong but useless" reading is a congestion problem, not a coverage problem. - Only then consider hardware - and if you do, prioritise systems with dedicated backhaul and 802.11k/v/r support over anything marketed purely on "boosted range." I put together a more Perth-specific, plain-English version of this - covering exactly which brick/wall types and floor plans we see causing the worst dead zones locally, and the fixes that actually work for them - in a longer guide here, if you want the non-technical version to hand to someone else in the house. Top comments (0)