Asymmetric Link Visibility

The client's local view of a Wi-Fi link is not the same as the AP's view of that same link. Signal strength, data rate, and even basic reachability can be healthy in one direction and broken in the other. Most field problems that look impossible live in the gap between those two views, and they only become visible when you measure from the right vantage point.

Uplink and downlink each run their own rate adaptation algorithm. The AP picks the rate it sends to the client. The client picks the rate it sends to the AP. They do not coordinate. A client can hold a high downlink rate while its uplink collapses, or recover on one direction while the other stays stuck. Reading only the downlink rate tells you nothing reliable about the uplink, and a capture taken at one point sees only what reaches that point.

Every RSSI value in a capture is the signal strength as measured by the capture radio, sitting wherever it happens to sit. It is not what the AP heard, and not what the client heard. Put the sniffer near the client and it reads the client's transmissions strong while the AP, further away, hears them weak. Analysts who treat sniffer RSSI as ground truth for the AP's reception make confident wrong calls. The capture point is a third vantage, and you must account for where it stands relative to both ends of the link you are judging.

An AP commonly radiates around 20 dBm at 2.4 GHz and 23 dBm at 5 GHz. A laptop sits near 15 dBm. A phone or IoT device runs lower still to save battery and space. The path loss is identical in both directions, but the power launched into it is not, so the downlink arrives strong while the uplink arrives weak. This single mismatch is the most common reason a client shows good signal yet posts a low uplink rate, and it is routinely misdiagnosed as a coverage problem.

RX-SOP is a vendor knob that sets the signal level below which the AP will not bother to demodulate a frame. Raise it and the AP stops hearing weaker clients, even ones that hear the AP perfectly. The client keeps receiving strong beacons on the downlink, concludes the link is fine, and never roams, while its uplink frames fall below the AP's threshold and go unanswered. The link looks healthy from the client and is dead from the AP. This is the asymmetry made deliberate by configuration.

802.11ax OBSS_PD lets a transmitter ignore a frame from another BSS if it arrives below a raised threshold, then transmit concurrently. The decision is made at the would-be transmitter, based on what it hears from the other BSS's transmitter. But the device that actually suffers the interference is the destination station of the ongoing transmission, which may sit somewhere else entirely. The reuse decision is taken from one vantage while the consequence lands at another. Same principle: judging a link from the wrong end.

Every one of these five is the same shape: a link judged from one end behaves differently at the other. That has a direct consequence for how you troubleshoot. AP-side telemetry alone cannot reveal an uplink the AP is not hearing. Client-side status alone cannot reveal a downlink decision the client never sees. The only way to see the gap is to measure both halves, which usually means a sniffer capture taken with deliberate attention to where it sits relative to the client and the AP.

When a problem looks impossible, the question to ask first is not what is wrong with the link, but whose view of the link you are looking at, and whose view you are missing.