Wi-Fi Design and Troubleshooting

"The Wi-Fi is slow" is one of the most common complaints in any office, school, or home — and one of the least specific. Wi-Fi is a shared, half-duplex radio medium: every device on a channel takes turns, older or distant clients consume more airtime, neighboring networks interfere, and walls, people, and microwaves change conditions minute by minute. Adding more access points or more transmit power often makes things worse.

Good wireless networks are designed for capacity: enough access points at moderate power, on well-planned channels and widths, so each one serves a manageable number of clients with strong signal. Good troubleshooting separates radio problems from the many non-radio problems that look the same to users — DHCP exhaustion, slow DNS, captive portals, or a congested internet link.

TL;DR

Quick Example

Inspecting a client's connection on Linux and macOS:

Separating Wi-Fi problems from network problems in a few commands:

Typical design targets for an office network:

Core Concepts

Generations and Bands

Signal, Noise, and Airtime

RSSI measures received signal strength in dBm (−50 is strong, −80 is weak); the noise floor is the background level; SNR is the difference, and it determines which data rates a client can sustain. Lower rates take more airtime for the same data, so one distant client slows everyone on the channel. Retries and channel utilization are better indicators of trouble than signal bars.

Channels and Interference

Access points on the same channel within hearing range share airtime (co-channel contention); adjacent overlapping channels corrupt each other's frames. Plan channels so neighboring APs differ, use auto channel selection carefully, and choose channel width by density: wide channels raise peak speed but reduce the number of non-overlapping channels. In dense offices, 20 or 40 MHz on 5 GHz usually outperforms 80 MHz; 6 GHz has room for wider channels.

Placement and Site Surveys

Plan with a predictive survey using floor plans and wall materials, then validate on site with a survey measuring signal, SNR, and overlap. Mount APs on ceilings near users, not in closets; account for glass, concrete, elevators, and people. Design for the least capable important client (for example, a phone or a barcode scanner), not the laptop with the best radio.

Roaming

Clients, not APs, decide when to roam. Strong transmit power keeps clients attached to distant APs (sticky clients). Tune AP power to match client power, set sensible minimum data rates, and enable 802.11k (neighbor reports), 802.11v (BSS transition management), and 802.11r (fast transition) where clients support them — important for voice and video calls while walking.

Security

Protected management frames (802.11w, required with WPA3) block deauthentication attacks. Map SSIDs to VLANs and apply firewall policy between them; see LAN Switching, VLANs, and Segmentation. Monitor for rogue APs and evil-twin networks.

A Troubleshooting Method

  1. Scope: one user, one area, one device type, or everyone? Specific symptoms point to specific layers.
  2. Radio: check RSSI, SNR, channel utilization, retries, and which AP the client is on — is it sticking to a distant AP?
  3. Association and authentication: failures here often come from RADIUS, certificates, or passphrase changes.
  4. IP layer: did the client get an address, gateway, and DNS servers? DHCP scope exhaustion is common in busy spaces. See IP Addressing, Subnets, and IPv6.
  5. DNS and captive portals: slow resolution and portal redirects look like Wi-Fi problems. See DNS.
  6. Upstream: test the gateway and internet separately; congested uplinks affect wired users too.
  7. Capture: wireless packet captures and controller logs confirm what is happening. See Packet Capture and Network Diagnostics.

Best Practices

Design for Capacity and Clients

Count devices and applications per area, design for the weakest important client, and validate with surveys.

Prefer Lower Power and More APs

Moderate transmit power improves roaming and channel reuse compared with a few loud APs.

Keep 2.4 GHz Minimal

Use it for devices that need it, with 20 MHz channels on 1, 6, and 11, and steer capable clients to 5 and 6 GHz.

Monitor, Don't Guess

Use controller or cloud dashboards for utilization, retries, client health, and interference, and keep a baseline to compare against.

Common Mistakes

Turning Power to Maximum

80 MHz Channels in a Dense Office

Blaming Wi-Fi for DNS

FAQ

What signal strength do I need for good Wi-Fi?

Around −67 dBm or stronger with at least 25 dB SNR is a common target for voice and video; general data can work at somewhat weaker levels. Retries and channel utilization tell you more than signal alone.

Should I use 2.4 GHz, 5 GHz, or 6 GHz?

Use 5 and 6 GHz for capable clients because they offer more channels and less interference, and keep 2.4 GHz for legacy and IoT devices that need its range.

Why do my devices stay connected to a far-away access point?

Clients decide when to roam, and strong AP transmit power can make a distant AP look good enough. Lower and balance AP power, set minimum data rates, and enable 802.11k/v/r.

Is WPA3 necessary?

It is strongly recommended: WPA3-Personal resists offline password guessing, WPA3 requires protected management frames, and 6 GHz networks require WPA3. Use WPA3-Enterprise with 802.1X for organizations.

How many devices can one access point handle?

It depends on airtime: client capabilities, applications, and signal quality matter more than a fixed number. Busy offices often plan for tens of active clients per radio and add APs for capacity.

Related Topics

References