Wi-Fi Fundamentals: Channels, Airtime, and Roaming

Wi-Fi is shared and half-duplex

A switched Ethernet endpoint normally has a dedicated full-duplex link. Wi-Fi is a shared radio system. Devices using the same channel listen before transmitting and contend for opportunities to speak. The access point, its clients, nearby APs on the same channel, their clients, and detectable neighboring networks all consume the same airtime.

A slow client can reduce performance for everyone because it occupies the channel longer to move the same payload. Airtime is also consumed by beacons, acknowledgments, probe traffic, management frames, retransmissions, and protocol overhead. The advertised link rate is therefore not the same as usable application throughput.

Choose the band intentionally

The 2.4 GHz band travels farther and penetrates common materials better, but it has limited capacity, heavy interference, and many legacy or IoT clients. In North America, channels 1, 6, and 11 are the usual non-overlapping 20 MHz choices. Forty-megahertz operation in 2.4 GHz generally consumes too much of the available spectrum.

Five gigahertz offers more channels and is the practical performance band for many commercial deployments. Some channels use DFS—Dynamic Frequency Selection—and must vacate when radar is detected. DFS can add useful capacity, but client support and the operational effect of a channel change must be considered.

Six gigahertz, used by Wi-Fi 6E and Wi-Fi 7 equipment, provides large amounts of cleaner spectrum but shorter effective coverage and weaker obstacle penetration. Only compatible clients can use it, and 6 GHz operation requires newer security such as WPA3 or Enhanced Open rather than WPA2-only service.

Wider channels are not free capacity

Common channel widths are 20, 40, 80, and 160 MHz, with additional options on newer platforms. A wider channel can give one client a higher peak rate, but it consumes more spectrum and leaves fewer independent channels for neighboring APs.

Dense offices, hotels, schools, and venues often gain more total capacity from several narrower channels than from a few enormous ones. Twenty megahertz is the sane default in 2.4 GHz; 20 or 40 MHz is common in dense 5 GHz designs; wider 6 GHz channels depend on client needs and AP density.

Nearby APs on the same channel normally hear one another and take turns, creating co-channel contention. Partially overlapping channels can corrupt frames without orderly coordination, producing adjacent-channel interference and retransmissions.

Signal bars do not measure network health

RSSI—Received Signal Strength Indicator—is commonly shown in dBm. Because the numbers are negative, -55 dBm is stronger than -70 dBm. Around -67 dBm is a common planning target for reliable roaming applications, but the required target depends on client capability, data rate, and application.

The noise floor represents background radio energy. SNR—Signal-to-Noise Ratio—compares the desired signal with that noise. A -60 dBm signal over a -90 dBm noise floor has 30 dB SNR. The same -60 dBm signal over -68 dBm noise has only 8 dB SNR and will likely perform badly despite displaying strong bars.

Clients adapt their modulation and coding scheme to conditions. Poor signal quality leads to lower negotiated rates, longer transmissions, and more retries. Commissioning should therefore review RSSI, SNR, channel utilization, negotiated rates, and retry percentages together.

The client normally decides when to roam

Multiple APs can advertise the same SSID, but the client normally chooses its AP and decides when to leave. The infrastructure can help with proper coverage overlap, transmit-power control, minimum data rates, and standards such as 802.11k neighbor reports, 802.11v transition suggestions, and 802.11r fast transition. The client still has the final vote in most deployments.

An AP can transmit more strongly than a phone, tablet, or small AV endpoint. The client hears the AP and shows several bars, but the AP may not reliably hear the client's weaker return signal. Coverage must be engineered as a two-way conversation around the weakest important client.

Correct sticky clients by shaping the RF cells

A sticky client remains associated with a distant AP even when a closer AP offers better service. Start by balancing transmit power so the old AP stops appearing attractive far outside its intended cell. Avoid running every radio at maximum power, and do not let 2.4 GHz coverage overwhelm the preferred 5 GHz cell.

Disable unnecessarily low legacy data rates so clients cannot maintain extremely slow connections from several rooms away. In a surveyed commercial environment, minimum basic rates such as 12 or 18 Mbps may be appropriate, but raising them without confirming overlap can create dead zones.

Enable 802.11k and 802.11v where supported, and test 802.11r with the actual client fleet because some older AV and IoT devices implement it poorly. Minimum-RSSI or forced-roam features can disconnect a client that refuses to move, but they should be the final nudge—not the foundation of the design.

Ruckus commonly exposes forced-roaming behavior through SmartRoam, though exact settings vary by controller and software release. A practical investigation compares the client's associated AP, band, AP-measured RSSI, negotiated rate, retry percentage, neighboring AP power, enabled roaming assistance, minimum data rates, and SSID/VLAN consistency before changing thresholds.

• Shape overlapping cells with sensible AP placement and transmit power.
• Remove legacy low rates only after verifying coverage.
• Use 802.11k/v to inform and encourage capable clients.
• Use 802.11r only after compatibility testing.
• Apply minimum-RSSI or SmartRoam thresholds cautiously.
• Keep SSID, security, and VLAN assignment consistent across roaming APs.