In this guide
Bands and channels
Wi-Fi operates across several radio bands. The 2.4 GHz band offers fewer non-overlapping channels and generally travels farther through obstacles. The 5 GHz band provides substantially more channel choices, while 6 GHz adds a large amount of new spectrum for supported clients and infrastructure, subject to local regulatory rules.
Channel availability is country-dependent. A professional design should use the regulatory domain supported by the deployment rather than assuming that every channel is legal everywhere.
Channel width
Wider channels can provide higher peak PHY rates, but they also consume more spectrum. In a dense environment, a narrower channel can improve overall capacity because more independent channels can be reused.
| Width | Typical trade-off |
|---|---|
| 20 MHz | More reuse and generally a strong choice for dense deployments. |
| 40 MHz | Higher peak rate but consumes twice the nominal spectrum of 20 MHz. |
| 80 MHz | Useful for high-throughput clients where spectrum permits; can reduce reuse. |
| 160 MHz | Very high peak rates, but requires substantial contiguous spectrum and suitable clients. |
RSSI and SNR
RSSI describes received signal strength, although the exact scale is vendor-specific. It is useful for judging coverage but does not directly tell you how clean the channel is.
SNR is the difference between received signal and the noise floor. A stronger signal with a high noise floor can still produce poor performance. As a practical engineering rule, aim for a healthy margin rather than designing around a single “magic” RSSI number.
When diagnosing a client, record RSSI, SNR, channel, width, band, MCS/PHY rate and retransmission behaviour together. That combination tells you much more than signal bars.
Airtime and interference
Wi-Fi is a shared medium. Devices contend for airtime rather than owning a dedicated wire. A slow client can consume disproportionate airtime because it needs longer to transmit the same amount of data.
Co-channel interference occurs when multiple cells intentionally reuse the same channel and must contend. Adjacent-channel interference occurs when overlapping channel allocations interfere with one another. In a well-designed WLAN, channel reuse and transmit power are planned together.
Non-Wi-Fi interference can also consume or corrupt airtime. Microwave ovens, poorly behaved devices and other RF sources can create local problems that are not visible simply by looking at the configured AP channel.
PHY rates and throughput
The displayed Wi-Fi link speed is a PHY rate, not application throughput. Protocol overhead, contention, acknowledgements, encryption, retransmissions and TCP behaviour all reduce the amount of useful application data transferred.
802.11 uses modulation and coding schemes (MCS) to adapt the PHY rate to radio conditions. A client that moves farther from the AP or experiences more interference may use a more robust, lower-rate MCS.
Authentication and security
Wi-Fi security can involve an open network, WPA2, WPA3, enterprise authentication or other deployment-specific mechanisms. Enterprise networks commonly use 802.1X with an authentication server such as RADIUS.
Separate authentication from association. A client first discovers and associates with an AP, then security and network-access mechanisms determine whether it can use the WLAN. DHCP occurs later and is not proof that Wi-Fi authentication itself succeeded.
Association and roaming
A Wi-Fi client normally decides when and where to roam, although the infrastructure can provide information and recommendations. 802.11k can provide neighbour information, 802.11v can help steer clients through transition management, and 802.11r can reduce authentication delay using Fast BSS Transition.
Roaming problems should be investigated as a sequence: did the client detect the target AP, decide to roam, complete authentication, obtain Layer 2 connectivity and maintain its IP session? A “roaming issue” can actually be RF coverage, authentication, DHCP, application timeout or client-driver behaviour.
Troubleshooting Wi-Fi
- Confirm whether the problem is coverage, capacity, roaming, authentication or application performance.
- Record band, channel and channel width.
- Check RSSI and SNR rather than relying on signal bars.
- Check channel utilisation and evidence of co-channel or non-Wi-Fi interference.
- Check client PHY rate, MCS and retransmissions.
- Compare the affected client with a known-good client in the same location.
- Check AP load and whether the client is associated with the expected AP.
- For authentication problems, inspect 802.1X/RADIUS events separately from DHCP.
- For roaming, record the source AP, target AP and timestamps and correlate controller/client logs.
Key takeaways
Good Wi-Fi is an RF design problem, a shared-medium capacity problem and a client-behaviour problem at the same time. Channel planning, sensible widths, healthy SNR, controlled airtime use and well-designed roaming matter more than chasing the highest possible link speed.