Skip to content
BytePath v0.0.35

WLAN Fundamentals

Networking path · Step 12Available

Plan and troubleshoot wireless networks by separating radio conditions, airtime, client behaviour, and the wired path.

Difficulty
Intermediate
Time
55 min
Practice
Measure local WLAN throughput
Assessment
Knowledge check

Before you start

Who is this for?

For learners who want to plan coverage, capacity, and security rather than treating Wi-Fi as invisible Ethernet.

Prerequisites

  • Basic LAN, switching, and IP concepts

What you'll be able to do

  • Distinguish SSID, BSSID, cell, band, and channel
  • Compare 2.4, 5, and 6 GHz trade-offs
  • Choose appropriate security
  • Measure local throughput reproducibly

Practical outcome

You can propose a test that separates a radio problem from an IP, Internet, or application problem.

An SSID is the network name shown to a user. A BSSID identifies a specific radio interface, usually by its MAC address. Multiple APs can advertise the same SSID, but the client generally decides when to roam. An AP bridges wireless frames to a wired LAN; it does not replace the router, firewall, or DHCP service unless those functions are integrated in the same device.

Band Strength Trade-off
2.4 GHz Longer reach and broad compatibility Few clean channels and more interference
5 GHz More channel choices and often higher capacity Shorter reach through walls
6 GHz Additional clean spectrum for supported clients Shorter practical reach and regulatory/client limits

Advertised PHY rates are not guaranteed application throughput. Distance, channel width, interference, spatial streams, airtime contention, client capability, and the wired backhaul all matter. Wider channels can increase peak rate but consume more spectrum and may perform worse in a dense environment.

Prefer WPA3 where compatible; WPA2 with AES/CCMP may be a transition choice for supported older devices. Enterprise networks can use 802.1X with central authentication. Disable obsolete WEP and WPA/TKIP. Keep AP and client software patched, use a long unique passphrase, and separate guests, IoT, clients, and management with appropriate VLAN and firewall policy.

A hidden SSID and MAC filtering are not replacements for encryption or authentication. Wireless encryption protects the link; it does not authorise every action on the network.

Clients choose when to roam, while standards such as 802.11k, 802.11v, and 802.11r can provide useful information or faster transitions. Wired AP backhaul is usually more predictable than a same-channel wireless repeater. Design cells for capacity and channel reuse, not maximum transmit power alone: the client must also reach the AP.

  1. Record location, AP/BSSID, band, channel, width, signal, time, and affected application.
  2. Compare near the AP with the actual problem location.
  3. Check channel use and client association rather than relying on signal bars.
  4. Test the gateway, then DNS, then a permitted application endpoint.
  5. Measure local throughput with an Ethernet-connected test server and iperf3.
  6. Change one variable—location, band, width, or AP—at a time.
  7. Compare repeated median results and document the conclusion.

A public speed test includes the AP, router, provider, Internet path, and remote server. A local test isolates the WLAN more effectively.

  • Treating PHY rate as usable throughput.
  • Maximising channel width in a crowded spectrum.
  • Changing several radio settings at once.
  • Blaming DNS or the Internet before testing the local gateway.
  • Using a repeater without considering its backhaul airtime.

Use two devices you own: one wired test server and one wireless client. Run repeated TCP measurements at two locations, record the variables above, and change only one factor. Explain whether the evidence points to signal, airtime, backhaul, or the wider network.

You should be able to place an AP deliberately, choose a security and segmentation strategy, and measure wireless performance without confusing radio rate with application throughput.