Wireless Fundamentals: Radio, Channels, and Media Access

What wireless networking is

Every lesson so far in this course has assumed a wired medium: a cable that carries one signal between two known endpoints. Wi-Fi (IEEE 802.11) replaces that cable with a shared radio medium that every nearby device transmits into and listens on at once. That single change has consequences that ripple through the rest of this lesson: a radio can't reliably listen and transmit on the same frequency at the same time, so it can't detect its own collisions the way Ethernet can; a device's "range" isn't a cable's fixed endpoints but a fading signal that different neighbors receive differently; and the medium is shared with everything else in the building, not just other Wi-Fi networks — microwave ovens, Bluetooth devices, and neighboring access points all compete for the same airtime.

Radio frequency bands and channels

Wi-Fi operates in three unlicensed frequency bands: 2.4 GHz (longer range, better at penetrating walls, but only three non-overlapping 20 MHz channels — 1, 6, and 11 in most regions — and heavy interference from Bluetooth, microwave ovens, and other 2.4 GHz gear), 5 GHz (shorter range, far more non-overlapping channels, and wider channel widths of up to 160 MHz for higher throughput), and 6 GHz (added by Wi-Fi 6E, with even more spectrum and no legacy devices to share it with, at the cost of the shortest range of the three). Each band is divided into channels — specific frequency ranges a radio tunes to — and two overlapping access points using the same or adjacent channels compete for the same airtime exactly as if they were one shared medium, even if they belong to different networks entirely.

Wireless network roles and topologies

An access point (AP) bridges the wireless medium to a wired network and coordinates every client associated with it; the AP and its associated clients together form a Basic Service Set (BSS), identified by a human-readable SSID (the network name shown in a device's Wi-Fi list) and a unique BSSID (the AP radio's MAC address). Multiple APs sharing the same SSID but covering different physical areas form an Extended Service Set (ESS), letting a client roam from one AP to another without changing networks. A far less common ad-hoc (IBSS) mode lets devices talk directly to each other with no AP at all, but it has no central coordinator and is rarely used outside of specialized peer-to-peer scenarios.

CSMA/CA and collision avoidance

Wired Ethernet historically used CSMA/CD (Carrier Sense Multiple Access with Collision Detection): a station could listen while transmitting and immediately detect a collision on the shared cable. A Wi-Fi radio generally can't do that — transmitting and receiving on the same frequency at the same time would mean listening for a faint incoming signal while its own transmission overwhelms the receiver, so it can't detect a collision while one is happening. Wi-Fi uses CSMA/CA (Collision Avoidance) instead: a station listens before transmitting, waits for the channel to be idle for a required interval, then waits an additional random backoff before sending — the randomness makes two stations choosing the exact same instant unlikely, but not impossible.

Interactive CSMA/CA and the hidden node problem

Step through two clients that are out of radio range of each other but both in range of the same access point — hidden nodes. Watch plain carrier sensing fail to prevent a collision between them, then watch an RTS/CTS exchange fix exactly that problem by making the AP's reply reach both clients at once.

Signal strength and interference

Wi-Fi signal strength is measured in RSSI (Received Signal Strength Indicator), typically expressed in dBm — a logarithmic scale where values closer to 0 are stronger and more negative values are weaker (-50 dBm is a strong signal; -80 dBm is barely usable). Signal strength fades with distance and is further degraded by attenuation (walls, floors, and other obstacles absorbing energy) and interference (overlapping channels from neighboring networks, or non-Wi-Fi devices like microwave ovens and Bluetooth radios sharing the 2.4 GHz band). Because the hidden node problem from the player above gets worse as physical obstacles increase — two clients separated by a wall are more likely to be hidden from each other — dense, obstacle-filled environments benefit the most from RTS/CTS, even though its extra round trip costs airtime that an open environment might not need to spend.

Inspect wireless evidence

Most operating systems expose a Wi-Fi diagnostics view (airport -I on older macOS, iw dev <interface> link on Linux, or the Wi-Fi details panel on Windows) that reports the associated BSSID, channel, and RSSI in real time — the fastest way to confirm which physical AP a client actually associated with in an ESS with several APs sharing one SSID.

Guided channel-planning practice

Work through why channel choice matters even between networks that have nothing to do with each other. Two neighboring apartments each run their own access point on 2.4 GHz. If both routers are left on their factory-default channel, there's a good chance they land on the same channel or on adjacent, overlapping ones — meaning every transmission from either network occupies airtime the other network also needs, regardless of which network a given frame is addressed to. The fix is to explicitly set non-overlapping channels (1, 6, or 11 in the 2.4 GHz band) on each AP, so the two networks' transmissions no longer collide with each other at the physical layer, even though they're still sharing the same unlicensed spectrum.

Troubleshoot wireless basics

1. Check RSSI first: a signal weaker than roughly -70 dBm commonly explains dropped connections and poor throughput that no configuration change will fix — the real problem is distance or obstruction, not settings.
2. Confirm the client and AP actually agree on a channel and band — a dual-band AP broadcasting the same SSID on both 2.4 GHz and 5 GHz can leave a client "stuck" on the weaker band if band steering isn't configured correctly.
3. Look for channel overlap from neighboring networks using a Wi-Fi scanning tool, especially in the crowded 2.4 GHz band, before assuming the problem is with the AP itself.
4. Distinguish a hidden-node-style collision problem (intermittent, worse with more clients, improved by enabling RTS/CTS) from simple congestion (consistently slow, correlated with the number of active clients, not fixed by RTS/CTS).
5. Check for non-Wi-Fi interference sources — microwave ovens, cordless phones, and Bluetooth devices all share the 2.4 GHz band and can degrade performance without showing up as another Wi-Fi network in a scan.
6. Verify physical placement: an AP mounted low, behind metal, or in a closet performs far worse than the same hardware mounted centrally and in the open, regardless of how its radio settings are tuned.

Knowledge check and summary

Pro deep dive