Why CSMA/CD Is Not Implemented in WLAN (Wi‑Fi)

CSMA/CD (CSMA/CD), a protocol designed for wired Ethernet, relies on a station’s ability to detect collisions while transmitting. WLAN (IEEE 802.11 / Wi‑Fi) does not use CSMA/CD; instead it uses CSMA/CA (CSMA/CA). The key reason is that practical 802.11 hardware and radio propagation make true collision detection during transmission unreliable or infeasible, so Wi‑Fi cannot reliably abort or retransmit based on detecting a collision at the physical layer. 2

Merely “sensing” the channel is not enough: CSMA/CD’s collision detection requires comparing what a transmitter is sending with what it can simultaneously observe on the medium. In wireless, a station transmitting typically cannot accurately receive and measure the ongoing channel state due to transmitter/receiver isolation limits and the presence of a strong self-signal (self-interference). 2

To see how this affects correctness, consider two overlapping transmissions at the receiver while a given sender is transmitting. If the sender cannot detect the overlap reliably, it cannot enforce the “collision happened—stop transmitting” rule that CSMA/CD depends on. That changes the design goal from “detect and truncate collisions” to “avoid collisions as much as possible,” leading to CSMA/CA with random backoff and acknowledgments. 2

Why “detecting collisions” fails in WLAN

In Ethernet CSMA/CD, collisions are detectable because of the electrical nature of the shared medium and because transceivers can (in typical half‑duplex Ethernet) listen closely enough while transmitting to recognize a collision condition. WLAN is different for at least three widely cited reasons:

1. Simultaneous transmit and receive is imperfect in 802.11
   A transmitting station’s own radio signal can dominate the receiver front end, making it difficult to observe the composite signal and infer that a collision occurred. This undermines CSMA/CD’s core mechanism: “while sending, detect whether another station’s transmission overlaps yours.” 2

2. Radio propagation and interference make “collision detection” ambiguous
   Wi‑Fi operates with radio waves; the receiver observes a superposition of signals. Distinguishing “your own frame corrupted by another transmitter” from “channel noise/fading” is not straightforward, especially in the presence of multipath and varying signal strengths. Therefore, the “physical-layer evidence of collision” is not reliably available at the transmitter to trigger CSMA/CD actions. 2

3. Hidden terminals break the effectiveness of collision-based logic
   Even if a station could detect collisions in some cases, Wi‑Fi’s network topology can produce hidden terminal situations where two nodes cannot sense each other but may still interfere at a third node. In such scenarios, one sender may not detect anything wrong while transmitting, yet the receiver experiences interference. CSMA/CA mitigates this with randomized backoff and mechanisms like RTS/CTS (where enabled). 2

In short: CSMA/CD assumes reliable collision detection at the transmitter; WLAN design assumes collision detection is not reliably implementable, so it prioritizes collision avoidance and recovery using MAC-layer procedures. 2

What WLAN uses instead: CSMA/CA and recovery

WLAN typically implements a form of CSMA/CA that includes:

• Carrier sensing: a node checks whether the channel appears idle before attempting to transmit.
• Random backoff: if the channel is busy (or after failed transmission attempts), the node waits a random amount of time to reduce collision probability.
• Acknowledgments (ACK): the sender relies on the receiver’s ACK to confirm successful reception; lack of ACK implies failure (which may be due to collision, interference, or fading).
• RTS/CTS (optional enhancement): used to reduce impact from hidden terminals by reserving the channel through short control frames.

These choices align with the reality that WLAN stations generally cannot do dependable collision detection like Ethernet transmitters can. 2