IEEE 802.11: the standard family behind Wi-Fi

MAC and PHY solve different problems

The PHY describes radio transmission and reception. The MAC coordinates access to the shared medium and carries frames. A fault can therefore be radio-related, such as interference, or configuration-related, such as contention or authentication mismatch.

Standards revisions are not a shopping list. Compatible modes matter, but the result also depends on channel planning, wired uplink, client drivers and active-station count.

Use an engineering vocabulary

For a survey, record band, channel, width, signal measurements and competing networks. For a change, record security method, client impact and rollback procedure. This makes observations comparable.

Radio use is jurisdictional. Rules can distinguish band, power, indoor or outdoor use and equipment authorization. Treat standards as technical context and obtain applicable local requirements before deployment.

Plan coexistence

A wireless LAN shares spectrum with nearby systems. Avoid treating a stronger signal as the only cure: poor channel choices can make neighbouring networks worse.

Use site observations to choose settings, then revisit them after occupancy or layout changes. Coexistence is an ongoing operating task, not a one-time checkbox.

Use MAC and PHY to name different failures

IEEE 802.11 separates physical-layer radio behaviour from medium-access behaviour. The PHY concerns transmission and reception over the radio path; the MAC coordinates how stations use the shared medium. This vocabulary improves diagnosis because a weak received condition, repeated contention, an access-control failure and an overloaded upstream connection are not the same problem wearing different signal icons.

Begin with the observable stage. Can the client detect the network, associate, receive the expected network configuration and reach the local gateway? Then ask whether the symptom follows a location, a client or a shared-use period. A retry-heavy radio path may point toward the PHY conditions, while a client that sees the network but cannot complete access may need a MAC or network-service check. The terms guide the next observation; they do not substitute for it.

Survey conditions instead of collecting bars

A useful wireless survey records the conditions that make a result interpretable: client type, band, channel, channel width, location, time, nearby networks and the application task. Signal bars alone do not show whether the bottleneck lies in contention, a client limitation or the wired path behind the access point. A measurement becomes more useful when another person can repeat the same setup and task.

Choose test points from real work areas, not only from the most favourable position. At each point run a task with a defined outcome, then preserve the result with the conditions. If a later change improves one room but harms another, the record reveals the trade-off instead of rewarding a single best-looking number. This also keeps a site survey from turning into a claim that all clients will receive identical performance.

Treat airtime as the constrained resource

Stations share access to the wireless medium. A high negotiated rate is therefore not a direct prediction of application throughput, especially when distance, retries or simultaneous traffic consume more airtime. A client with an unfavourable path can need more attempts to move the same useful data, reducing the time available to other clients. The relevant question is how the intended application behaves under the intended mix of clients.

Test a complaint with a stable task before and after one change. Compare the affected client near the access point and at the affected location; then compare it while the surrounding traffic differs. If the symptom follows location, investigate the path. If it follows load across several locations, look at shared use and the upstream boundary. This avoids treating a favourable one-device speed test as proof of capacity for the whole WLAN.

Inspect the wired boundary behind the access point

An access point joins the radio side to a wired network, so an apparently wireless complaint can originate beyond the antenna. Verify the expected switch connection, network configuration, gateway reachability and management path before changing radio settings. A client may have an excellent local association while the access point has no usable upstream route, or while the service behind that route is unavailable.

Use paired checks to locate the boundary. A wired endpoint that fails in the same way as the wireless client shifts attention away from the radio medium. A wired endpoint that succeeds while only a distant wireless client fails preserves the radio path as a useful hypothesis. Do not reset the access point before recording these comparisons; a reset can remove the state that distinguishes a wiring, configuration or radio condition.

Change a channel plan as a system change

Channel and channel-width choices affect the stations already using the access point and their coexistence with nearby systems. A change may improve one observation while creating a different sharing condition elsewhere. Capture a before result in the actual affected locations, make one reversible adjustment and repeat the same task with the same client. This is more informative than selecting a setting from a list and judging it by one immediate number.

Keep the technical standard and deployment decision separate. IEEE 802.11 provides MAC and PHY context; it does not approve a particular antenna, power level or outdoor use at a particular site. Local radio requirements depend on the jurisdiction, equipment and installation. The responsible conclusion after a test is narrow: what was observed under recorded conditions, which trade-off was chosen, and what remains to be confirmed before deployment.