CSMA/CD: Carrier Sense Multiple Access with Collision Detection
Ethernet Usage — CSMA/CD's Legacy
Read aloud is unavailable in this browser.
The Protocol That Built the Internet
CSMA/CD is inextricably linked with Ethernet—the most widely deployed local area network technology in history. The collision detection protocol we've studied in detail was the foundation upon which Ethernet was built, enabling the shared-wire networks that connected the first generations of personal computers.
Today, Ethernet connects billions of devices in homes, offices, data centers, and industrial installations. Yet modern Ethernet operates fundamentally differently from its CSMA/CD origins. Understanding this evolution—from shared coaxial cable to switched full-duplex—illuminates why CSMA/CD mattered and why it eventually became obsolete.
This page traces CSMA/CD's journey through Ethernet's history, explains its role in different Ethernet standards, and clarifies when and where the protocol is still used today (spoiler: almost nowhere).
By the end of this page, you will understand how CSMA/CD enabled original Ethernet, when and why switches eliminated the need for collision detection, which Ethernet standards still support half-duplex CSMA/CD, and the lasting impact of CSMA/CD on network design principles.
Origins: Ethernet and CSMA/CD
The story of CSMA/CD and Ethernet begins at the Xerox Palo Alto Research Center (PARC) in 1973, where Robert Metcalfe and David Boggs invented Ethernet.
The ALOHA Inspiration:
Metcalfe was inspired by the ALOHAnet system developed at the University of Hawaii, which used radio waves to connect computer terminals across Hawaiian islands. ALOHAnet's "transmit and hope" approach had limited efficiency (~18% for pure ALOHA), but it demonstrated that multiple stations could share a single channel.
Metcalfe's key insight was that wired networks could do better because:
- Stations could sense the carrier before transmitting (reducing collisions)
- Stations could detect collisions during transmission (enabling immediate recovery)
- The shared medium was more controllable than radio
| Protocol | Era | Maximum Efficiency | Key Innovation |
|---|---|---|---|
| Pure ALOHA | 1971 | 18.4% | First wireless packet network |
| Slotted ALOHA | 1972 | 36.8% | Synchronized time slots |
| CSMA (carrier sense) | 1973 | ~50-80% | Listen before transmit |
| CSMA/CD (Ethernet) | 1973 | ~90%+ | Collision detection and recovery |
The Original Ethernet (Experimental):
- Date: 1973 at Xerox PARC
- Speed: 2.94 Mbps
- Medium: Coaxial cable
- Protocol: CSMA/CD
- Name: "Ethernet" (inspired by the luminiferous ether of 19th-century physics)
DIX Ethernet and IEEE 802.3:
In 1980, Digital Equipment Corporation (DEC), Intel, and Xerox collaborated to publish the DIX Ethernet specification (10 Mbps). This was formalized by the IEEE as 802.3 in 1983.
Ethernet Timeline:
1973: Original Ethernet (Xerox PARC) - 2.94 Mbps
│
1980: DIX Ethernet v1.0 - 10 Mbps (DEC, Intel, Xerox)
│
1982: DIX Ethernet v2.0 - refined specification
│
1983: IEEE 802.3 - international standard
│
1985: 10BASE2 - thin coax (cheaper)
│
1990: 10BASE-T - twisted pair (star topology with hubs)
│
1995: 100BASE-TX - Fast Ethernet (still uses CSMA/CD)
│
1998: 1000BASE-X - Gigabit Ethernet (half-duplex defined but rarely used)
│
2002: 10GBASE - 10 Gigabit (full-duplex only, NO CSMA/CD)
│
Today: 100GBASE, 400GBASE - All full-duplex, CSMA/CD irrelevant
Metcalfe chose 'Ethernet' as a reference to the 'luminiferous ether'—the hypothetical medium through which 19th-century physicists believed light propagated. Just as the ether supposedly pervaded all space, Ethernet's shared cable pervaded all connected computers. The name stuck even as the ether theory was disproven.
CSMA/CD Across Ethernet Media Types
Ethernet has used many physical media over its history. Each medium implements collision detection differently, though the MAC-layer protocol remains consistent.
10BASE5 (Thick Ethernet / "Thicknet"):
The original standardized Ethernet used thick coaxial cable:
- Topology: Bus (single cable, stations tap in via transceivers)
- Maximum segment: 500 meters
- Stations per segment: Up to 100
- Collision detection: Voltage level monitoring on cable
- Installation: Complex, requires specialized tools ("vampire taps")
10BASE2 (Thin Ethernet / "Cheapernet"):
A more affordable variant using thinner RG-58 coaxial cable:
- Topology: Bus (daisy-chain with BNC connectors)
- Maximum segment: 185 meters
- Stations per segment: Up to 30
- Collision detection: Same principle as 10BASE5
- Installation: Easier, but still shared medium
10BASE-T (Twisted Pair):
The breakthrough that democratized Ethernet:
- Topology: Star (all stations connect to central hub)
- Maximum segment: 100 meters per cable
- Collision detection: Hub-based (combines all signals)
- Installation: Uses phone-style RJ-45 connectors, easy to manage
10BASE-T Star Topology with Hub:
┌────────────────────────────────────────────┐
│ HUB │
│ (repeats all signals to all ports, │
│ creating a logical shared medium) │
└─────┬──────┬──────┬──────┬──────┬─────────┘
│ │ │ │ │
│ │ │ │ │
[PC1] [PC2] [PC3] [Server] [Printer]
All devices share the same collision domain.
CSMA/CD is essential—collisions are normal operation.
| Standard | Cable Type | Topology | Segment Length | CSMA/CD |
|---|---|---|---|---|
| 10BASE5 | Thick coax (RG-8) | Bus | 500 m | Required |
| 10BASE2 | Thin coax (RG-58) | Bus | 185 m | Required |
| 10BASE-T | Cat 3/5 UTP | Star (hub) | 100 m | Required |
| 10BASE-F | Fiber optic | Star (hub) | 2000 m | Required |
100BASE-TX (Fast Ethernet):
Fast Ethernet scaled up to 100 Mbps while maintaining CSMA/CD compatibility:
- Speed: 100 Mbps
- Slot time: Still 512 bit times (but now 5.12 μs instead of 51.2 μs)
- Network diameter: Reduced to ~250 m to maintain timing
- CSMA/CD: Supported in half-duplex mode
- Reality: Most deployments used full-duplex switches, not hubs
1000BASE-X (Gigabit Ethernet):
Gigabit Ethernet defined half-duplex mode for backward compatibility, but with severe compromises:
- Carrier extension: Minimum transmission extended to 512 bytes
- Frame bursting: Send multiple frames in one transmission slot
- Network diameter: Limited to ~25 m for half-duplex
- Reality: Virtually all Gigabit Ethernet is full-duplex with switches
Although 10/100/1000 Mbps Ethernet standards define half-duplex CSMA/CD operation, finding actual half-duplex installations in modern networks is rare. Even by 2000, most new networks used switches for full-duplex operation. Today, half-duplex is effectively a legacy mode kept for backward compatibility.
The Switch Revolution: End of CSMA/CD
The introduction of Ethernet switches fundamentally changed how LANs operate, eventually making CSMA/CD obsolete.
From Hubs to Switches:
Hubs (multi-port repeaters) maintain a single collision domain:
- All traffic is visible to all ports
- Collisions are normal
- CSMA/CD is essential
- Bandwidth is shared among all stations
Switches (learning bridges) create separate collision domains:
- Traffic is directed only to destination ports
- Collisions are eliminated (in full-duplex)
- CSMA/CD becomes unnecessary
- Each connection gets full bandwidth
- •Physical layer device (Layer 1)
- •Repeats all signals to all ports
- •Single collision domain
- •Half-duplex operation only
- •CSMA/CD required
- •Shared bandwidth (10 Mbps total)
- •No address learning
- •Data link device (Layer 2)
- •Forwards frames only to destination
- •Each port is separate collision domain
- •Full-duplex capable
- •CSMA/CD unnecessary
- •Dedicated bandwidth per port
- •Learns MAC addresses dynamically
How Full-Duplex Eliminates CSMA/CD:
In full-duplex mode:
- Separate TX/RX paths: Each station has dedicated transmit and receive pairs
- No shared medium: Transmissions don't interfere because they're on different wires
- Simultaneous communication: Stations can send and receive at the same time
- No collisions possible: Without collisions, collision detection is meaningless
- No CSMA needed: Without a shared medium, carrier sensing is pointless
Full-Duplex Switch Connection:
[Station A] [SWITCH] [Station B]
│ │ │
TX ────────────────────► RX RX ◄──────────────── TX
RX ◄──────────────────── TX TX ────────────────► RX
│ │ │
└── Pair 1 (A→Switch) │ └── Pair 1 (B→Switch)
└── Pair 2 (Switch→A) │ └── Pair 2 (Switch→B)
No collision possible - completely separate paths!
| Metric | 10 Mbps Hub | 10 Mbps Switch | Improvement |
|---|---|---|---|
| Total bandwidth | 10 Mbps (shared) | 10 Mbps × N ports | N× more |
| Per-port bandwidth | 10/N Mbps avg | 10 Mbps each | N× more |
| Collision rate | High at load | Zero | 100% reduction |
| Latency | Variable (backoff) | Predictable (microseconds) | Consistent |
| Full-duplex | No | Yes | 2× per link |
| Security | All traffic visible | Unicast isolated | Much improved |
When switches first appeared in the early 1990s, they were expensive—a 10-port Fast Ethernet switch might cost thousands of dollars. But Moore's Law worked in networking's favor. By 2000, switch prices had dropped dramatically. Today, a 24-port Gigabit switch costs less than $50, making hubs economically irrelevant even for the smallest networks.
CSMA/CD in Modern Ethernet Standards
Let's examine which modern Ethernet standards still define CSMA/CD and which have abandoned it entirely.
Standards with CSMA/CD (Half-Duplex Mode):
- 10BASE-T and variants: CSMA/CD defined and sometimes used with hubs
- 100BASE-TX: CSMA/CD defined for half-duplex hub connections
- 1000BASE-T (Gigabit): CSMA/CD defined but rarely implemented
Standards without CSMA/CD (Full-Duplex Only):
- 10GBASE (10 Gigabit): No half-duplex mode defined at all
- 25GBASE, 40GBASE, 50GBASE: Full-duplex only
- 100GBASE, 200GBASE, 400GBASE: Full-duplex only
The IEEE 802.3 working group made a decisive break with 10 Gigabit Ethernet—CSMA/CD was not included in the standard.
| Standard | Speed | Year | CSMA/CD Status |
|---|---|---|---|
| 802.3 (original) | 10 Mbps | 1983 | Required (half-duplex) |
| 802.3u | 100 Mbps | 1995 | Supported (half-duplex optional) |
| 802.3z | 1 Gbps (fiber) | 1998 | Supported (with carrier extension) |
| 802.3ab | 1 Gbps (copper) | 1999 | Supported (with carrier extension) |
| 802.3ae | 10 Gbps | 2002 | NOT SUPPORTED (full-duplex only) |
| 802.3ba | 40/100 Gbps | 2010 | Not supported |
| 802.3bs | 200/400 Gbps | 2017 | Not supported |
Why 10 Gigabit and Beyond Don't Need CSMA/CD:
-
Physics limitations: At 10 Gbps, a 64-byte frame transmits in 51.2 nanoseconds. Light travels only ~15 meters in this time. Half-duplex would limit networks to a few meters.
-
Universal switching: By 2002, switches were the standard. No one used shared media at high speeds.
-
Simplified design: Removing CSMA/CD simplifies hardware and eliminates a class of potential problems.
-
Full-duplex benefits: Without collision overhead, efficiency approaches 100%.
Modern Ethernet Reality:
Today's Ethernet frames never collide in normal operation:
- All links are switched and full-duplex
- Each cable is a point-to-point connection
- The CSMA/CD state machine in NICs is present for backward compatibility but never triggered
- Collision counters on switch ports should always read zero
Modern NICs still contain CSMA/CD logic for backward compatibility with older hubs and for potential half-duplex scenarios (like auto-negotiation failures). However, in properly configured networks, this code path is never executed.
Where CSMA/CD Still Matters Today
While CSMA/CD is largely obsolete for Ethernet, understanding it remains valuable in several contexts:
1. Legacy Network Troubleshooting:
Older networks and equipment may still use hubs or have inadvertent half-duplex connections:
- Industrial control systems with decades-old infrastructure
- Some embedded systems with 10 Mbps Ethernet interfaces
- Duplex mismatches causing half-duplex fallback
When a modern NIC connects to a hub (or through a duplex mismatch), CSMA/CD activates. Understanding the protocol helps diagnose the resulting performance problems.
- •Certification exams: CCNA, CompTIA Network+, and academic courses cover CSMA/CD extensively
- •Protocol family understanding: CSMA/CA (WiFi), CSMA (industrial networks) derive from CSMA/CD concepts
- •Network design principles: Collision domains, slot time, and minimum frame size affect all shared media systems
- •Historical context: Understanding networking evolution helps explain current design choices
- •Troubleshooting skills: Recognizing collision symptoms helps diagnose duplex mismatches
2. Related Protocols:
CSMA/CD concepts appear in other networking technologies:
| Technology | Protocol | Relationship to CSMA/CD |
|---|---|---|
| WiFi (802.11) | CSMA/CA | Uses carrier sense, but collision avoidance instead of detection |
| CAN Bus | CSMA/CR | Bitwise arbitration prevents collisions rather than detecting them |
| HomePlug | CSMA/CA | Similar to WiFi, adapted for power line communication |
| Industrial Ethernet | Various | Some field buses use CSMA variants |
3. Academic and Certification Importance:
CSMA/CD remains a cornerstone of networking education:
- It demonstrates fundamental protocol design principles
- The efficiency analysis teaches quantitative network performance evaluation
- The timing constraints illustrate physical layer constraints on protocols
- It provides historical context for understanding Ethernet's evolution
The most common modern sighting of CSMA/CD behavior is during duplex mismatches. If auto-negotiation fails and one side operates in full-duplex while the other is half-duplex, the half-duplex side will detect 'collisions' that are actually the full-duplex side's normal simultaneous transmission. This causes dramatic performance degradation—often falling to 10% or less of expected throughput.
The Lasting Legacy of CSMA/CD
Although CSMA/CD is no longer used in practice, its influence on networking is permanent.
Architectural Contributions:
CSMA/CD established design principles that persist today:
-
Frame structure: The Ethernet frame format, including the 64-byte minimum, persists in all modern standards
-
MAC addresses: The 48-bit MAC address format standardized with Ethernet is universal
-
Speed auto-negotiation: The mechanism for negotiating link parameters descends from CSMA/CD-era specifications
-
Inter-frame gap: The mandatory quiet period between frames remains (though somewhat reduced at high speeds)
Why Ethernet Won:
During the 1980s and 1990s, Ethernet competed with several alternative LAN technologies:
| Competitor | Fate | Why Ethernet Won |
|---|---|---|
| Token Ring (IEEE 802.5) | Obsolete | Simpler, cheaper, faster evolution |
| FDDI (Fiber) | Obsolete | Ethernet scaled to fiber while being cheaper |
| ATM (for LANs) | Obsolete | Too complex, Ethernet captured the market |
| LocalTalk (Apple) | Obsolete | Slower, proprietary |
Ethernet's success factors:
- Simple protocol: CSMA/CD was straightforward to implement in hardware
- Low cost: Ethernet NICs and cables were less expensive than alternatives
- Speed scaling: Ethernet successfully evolved from 10 Mbps through 400 Gbps
- Installed base: Once dominant, network effects reinforced Ethernet's position
- •Binary exponential backoff — The algorithm developed for CSMA/CD is used in many collision-prone systems (WiFi, etc.)
- •Minimum frame size concept — The idea that frames must be long enough for protocol timing is fundamental to many systems
- •Collision domain thinking — Understanding broadcast domains, collision domains, and segmentation remains essential
- •Efficiency analysis methods — The 'a' parameter analysis is applicable to many shared-resource systems
- •Protocol state machines — The CSMA/CD state machine is a teaching example of protocol design
CSMA/CD's obsolescence isn't a failure—it's a success story. The protocol enabled widespread LAN adoption, and the ecosystem it created driven the development of switches that made it unnecessary. Ethernet evolved, and CSMA/CD's job was done.
Modern Practical Considerations
For modern network practitioners, CSMA/CD knowledge translates into practical skills.
Diagnosing Duplex Problems:
The most common CSMA/CD-related issue today is duplex mismatch:
| Symptom | Likely Cause | Solution |
|---|---|---|
| High collision count on switch port | Half-duplex forced on one end | Configure matching duplex settings |
| Late collisions > 0 | Duplex mismatch or cable too long | Check duplex settings; verify cable |
| FCS errors increasing | Duplex mismatch or physical problem | Check duplex; inspect cables/connectors |
| Very slow transfers (10× slower than expected) | Half-duplex with high collisions | Force full-duplex on both ends |
| Runts on switch statistics | Collisions (shouldn't happen in full-duplex) | Investigate configuration |
1234567891011121314151617181920212223242526272829303132
#!/bin/bash# Script to check for duplex-related issues on Linux echo "=== Network Interface Status ==="interface="eth0" # Change as needed # Check current duplex settingecho "Interface $interface settings:"ethtool $interface | grep -E "Speed|Duplex|Link detected" # Check for collision statisticsecho ""echo "=== Collision Statistics ==="cat /sys/class/net/$interface/statistics/collisions # If collisions > 0 on a switched network, investigate!collisions=$(cat /sys/class/net/$interface/statistics/collisions)if [ "$collisions" -gt 0 ]; then echo "WARNING: Collisions detected ($collisions)" echo "This should not happen on full-duplex switched network!" echo "Check: 1) Duplex settings 2) Switch configuration 3) Cable quality"else echo "OK: No collisions detected (expected for full-duplex)"fi # Check for errors that might indicate duplex mismatchecho ""echo "=== Error Statistics ==="echo "RX errors: $(cat /sys/class/net/$interface/statistics/rx_errors)"echo "TX errors: $(cat /sys/class/net/$interface/statistics/tx_errors)"echo "RX dropped: $(cat /sys/class/net/$interface/statistics/rx_dropped)"echo "TX dropped: $(cat /sys/class/net/$interface/statistics/tx_dropped)"Best Practices for Modern Networks:
-
Always use switches, never hubs — Hubs should be museum pieces, not network equipment
-
Configure full-duplex explicitly — Don't rely solely on auto-negotiation for critical links
-
Monitor collision counters — Any non-zero collision count on a switched network indicates a problem
-
Match duplex settings on both ends — When forced full-duplex on one side, force it on the other
-
Use link aggregation for bandwidth — Group multiple full-duplex links rather than trying to avoid collisions on shared media
-
Update legacy equipment — If you still have hubs, replace them with switches
If one side of a link is forced to full-duplex while the other is set to auto-negotiate, the auto-negotiate side will fall back to half-duplex (since it doesn't see auto-negotiation from the partner). This creates a duplex mismatch—one of the most insidious network problems because basic connectivity works but performance is terrible.
KEEP LEARNING
Keep learning for free.
Read the complete lesson, save your notes and pick up where you left off with a free account. No card needed.