The Hidden Node Problem and RTS/CTS

The hidden node problem occurs when two wireless clients can each reach the same access point (AP) but cannot hear each other’s transmissions — so both may transmit at once, and their frames collide at the AP. It’s a failure of the “listen before you talk” rule that Wi-Fi depends on: you can’t defer to a transmission you physically cannot detect. The standard remedy is the Request to Send / Clear to Send (RTS/CTS) handshake, which uses the AP — the one device everyone can hear — to referee the channel.

Why Wi-Fi is vulnerable to this in the first place

Wired Ethernet’s historical collision handling (CSMA/CD, Carrier Sense Multiple Access with Collision Detection) detected collisions as they happened. Wireless radios can’t do that — a transmitting radio is deafened by its own signal and cannot listen at the same time. So 802.11 uses CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance) instead: before transmitting, a station listens to the channel, and if the channel is busy, it waits a randomized backoff period and tries again. Collisions aren’t detected; they’re inferred when an expected acknowledgment (ACK) never arrives, triggering a retransmission.

CSMA/CA’s carrier sense comes in two forms:

• Physical carrier sense: the radio literally listens for RF energy on the channel.
• Virtual carrier sense: stations read the Duration field in overheard 802.11 frames and set a countdown timer called the NAV (Network Allocation Vector). While the NAV is nonzero, the station treats the medium as busy without even listening.

Both mechanisms share one assumption: that a station can receive the frames of other stations competing for the channel. The hidden node problem is what happens when that assumption breaks.

Anatomy of a hidden node scenario

Picture an AP in the middle of a large space, with client A on one side and client B on the other. Each client has a clean link to the AP. But A and B are separated by too much distance — or by an RF-opaque obstacle like a run of metal shelving in a warehouse — so neither can decode, or even detect, the other’s transmissions. From A’s perspective, B does not exist. A and B are hidden nodes relative to each other.

Now both clients get data to send at a similar moment. Each performs carrier sense, each hears a quiet channel, each transmits. The two signals arrive at the AP overlapped and the AP can decode neither — a collision. No ACK comes back, both clients back off, retry, and quite possibly collide again. The visible symptoms are elevated retransmission rates, shrinking effective throughput, and rising latency in a cell where every individual client’s signal to the AP looks perfectly healthy.

Distance is only one cause. The classic exam setups are:

• Physical obstruction: two handheld scanners on opposite ends of a metal shelving unit — each reaches the AP fine, neither hears the other. Metal, concrete, elevator shafts, and coolers are the usual walls.
• Cell geometry: clients at opposite edges of a large cell, both at the fringe of each other’s radio range but comfortably inside the AP’s.
• Mismatched power: an AP with a high-gain antenna hears clients that are far too weak to hear one another.

RTS/CTS: making the AP the referee

The mechanism that specifically addresses hidden nodes is the RTS/CTS (Request to Send / Clear to Send) exchange. It works because of an asymmetry in the topology: the clients can’t all hear each other, but every client can hear the AP.

The sequence:

1. A station with data to send first transmits a short RTS frame to the AP, announcing how long it needs the channel (the duration covers the data frame plus the ACK).
2. The AP replies with a CTS frame that repeats that duration.
3. Every station that hears the CTS — including nodes hidden from the original sender — sets its NAV for the announced duration and stays silent.
4. The original station sends its data and receives its ACK inside the reserved window.

The CTS is the trick: even though hidden node B never heard A’s RTS, B does hear the AP’s CTS and defers via virtual carrier sense. The channel reservation reaches everyone in the cell because it’s broadcast from the cell’s center.

RTS/CTS isn’t free — every data exchange gains two extra control frames of airtime overhead, which is why it’s not on for every frame by default. Instead, clients use an RTS threshold: only frames larger than the threshold trigger the handshake. Lowering the threshold applies RTS/CTS to more traffic, which is precisely the tuning move in a cell suffering hidden-node collisions. (A related lightweight option, CTS-to-self, protects transmissions in mixed-mode environments but doesn’t solve hidden nodes, since it’s the sender transmitting the CTS.)

Beyond RTS/CTS, real-world mitigation can also mean fixing the topology: adding an AP so the shelf’s two sides land in different cells, repositioning the AP, or adjusting cell sizing during a wireless site survey so clients in one cell can generally hear each other.

Hidden node vs. exposed node

The N10-009 exam focuses on hidden nodes, but knowing its mirror image sharpens the distinction:

	Hidden node	Exposed node
Situation	Two stations can’t hear each other, both reach the same AP	A station hears a neighboring cell’s transmission and defers unnecessarily
Failure mode	Collisions at the AP	Wasted airtime — station stays silent when it could safely transmit
Effect on network	Retransmissions, throughput loss, latency	Reduced throughput without collisions
Fix	RTS/CTS, lower RTS threshold, re-survey cell layout	Better channel planning between cells

Inter-cell deferral of this kind is the territory of co-channel interference — same-channel cells sharing airtime by design rather than by accident.

How the N10-009 exam tests this

• Name-the-mechanism: two stations in one cell are in range of the AP but out of range of each other, causing collisions at the AP — which mechanism specifically addresses this? → RTS/CTS. Distractors like CSMA/CA alone, channel bonding, or band steering don’t solve it: CSMA/CA is the thing that’s failing.
• Name-the-condition: a scenario describes two devices separated by a metal obstruction, each able to reach the AP but unable to detect one another, with collisions rising at the AP — what is this called? → the hidden node problem. The metal shelving detail is the giveaway; it’s an RF barrier between peers, not between client and AP.
• Symptom-pattern questions: high retry/retransmission counters and poor throughput in a cell where every client shows good signal to the AP — suspect hidden nodes rather than coverage or interference.
• Tuning questions: which adjustment invokes protection for more frames? → lowering the RTS threshold.

The setup repeats across N10-009 practice questions — after a few passes, “metal shelving” reads as “hidden node” on sight.

Quick reference

• Hidden node = two clients that reach the same AP but can’t detect each other; their frames collide at the AP.
• Root cause: CSMA/CA’s carrier sense only works against transmitters you can hear.
• Caused by distance, RF-blocking obstacles (metal shelving is the exam’s favorite), or asymmetric power.
• Fix: RTS/CTS — the AP’s CTS reservation is heard by all stations, including ones hidden from the sender.
• NAV = the virtual carrier-sense countdown timer set by overheard Duration fields, including those in CTS frames.
• RTS threshold controls which frame sizes use the handshake; lower it to protect more traffic.
• Symptoms: retransmissions and throughput collapse despite good per-client signal readings.
• Exposed node is the opposite condition — needless deferral, wasted airtime, no collisions.