Loading learning content...
When you plug a network cable into your computer or connect to a wireless access point, you're utilizing technologies that have been refined over decades of innovation, standardization, and real-world deployment. LAN technologies define the physical and data link layer protocols that enable devices to communicate within a local network.
While many technologies have competed in the LAN space, one has emerged as the overwhelming victor: Ethernet. From its origins at Xerox PARC in 1973 to its current manifestations operating at hundreds of gigabits per second, Ethernet's success story is one of continuous evolution while maintaining backward compatibility—a rare achievement in technology.
However, understanding LAN technologies requires more than just studying Ethernet. The alternatives—Token Ring, FDDI, ATM, and wireless technologies—each contributed concepts and capabilities that influenced modern networking. Some specialized applications still use these technologies today.
By the end of this page, you will understand the major LAN technologies—their architectures, mechanisms, strengths, and limitations. You'll gain deep knowledge of Ethernet's evolution and operation, understand why it dominated competitors, and recognize the ongoing role of alternative technologies in specialized applications.
Ethernet is a family of wired LAN technologies standardized as IEEE 802.3. It defines physical layer specifications (cables, connectors, signaling) and data link layer protocols (frame format, addressing, error detection). Ethernet's dominance stems from its simplicity, low cost, and remarkable ability to scale from 10 Mbps to 400 Gbps while maintaining fundamental compatibility.
Historical Origins:
Ethernet was invented by Robert Metcalfe and David Boggs at Xerox PARC in 1973. The name derives from 'ether'—the hypothetical medium once thought to permeate space and carry light waves. Just as the ether was imagined as a universal medium for electromagnetic waves, Ethernet was conceived as a universal medium for data communication.
The original Ethernet operated at 2.94 Mbps over coaxial cable using CSMA/CD. It connected Alto computers—early personal workstations that pioneered graphical user interfaces. This proof-of-concept evolved into the commercial standard we use today.
The 10 Mbps Era:
The first commercial Ethernet standard (1980, later IEEE 802.3 in 1983) operated at 10 Mbps. Several physical layer variants emerged:
| Standard | Media | Max Distance | Connector |
|---|---|---|---|
| 10BASE5 (Thick Ethernet) | Thick coaxial cable | 500 meters | Vampire tap/AUI |
| 10BASE2 (Thin Ethernet) | Thin coaxial cable (RG-58) | 185 meters | BNC |
| 10BASE-T | Category 3+ twisted pair | 100 meters | RJ-45 |
| 10BASE-FL | Multimode fiber | 2 kilometers | ST/SC |
10BASE-T proved transformative. By using inexpensive twisted-pair cable (the same cable used for telephones) and standardizing on the RJ-45 connector, it made Ethernet accessible to every office. The star topology enabled by 10BASE-T also allowed switches to replace hubs, eventually eliminating the collision domain problem entirely.
The DIX/IEEE 802.3 Distinction:
Two slightly different frame formats exist:
In practice, the EtherType field in Ethernet II frames always has values greater than 1500 (the maximum frame length), so devices can distinguish between the two formats by checking if the field value is ≤1500 (length) or >1500 (EtherType).
Despite IEEE 802.3 being the official standard, Ethernet II (DIX format) won in practice. IP, ARP, IPv6, and virtually all modern protocols use the EtherType format. The 802.2 LLC header adds overhead without significant benefit for most applications. When we discuss 'Ethernet frames' today, we almost always mean Ethernet II format.
Understanding the Ethernet frame structure is fundamental to network troubleshooting, protocol analysis, and network programming. Every piece of data transmitted over a LAN is encapsulated in an Ethernet frame.
Complete Ethernet Frame on the Wire:
| Field | Size | Purpose |
|---|---|---|
| Preamble | 7 bytes | Alternating 10101010 pattern for clock synchronization |
| Start Frame Delimiter (SFD) | 1 byte | 10101011 pattern marking frame start |
| Destination MAC Address | 6 bytes | Recipient's hardware address |
| Source MAC Address | 6 bytes | Sender's hardware address |
| EtherType | 2 bytes | Identifies encapsulated protocol (e.g., 0x0800 = IPv4) |
| Payload | 46-1500 bytes | Encapsulated data from higher layers |
| Frame Check Sequence (FCS) | 4 bytes | CRC-32 error detection checksum |
| Interframe Gap | 12 bytes (96 bits) | Minimum gap between frames |
Detailed Field Analysis:
Preamble and SFD (8 bytes total):
The preamble's 7 bytes of 10101010 patterns allow the receiver's clock recovery circuit to synchronize with the incoming signal. The SFD (10101011) marks the end of timing synchronization and the start of the actual frame data. These fields are not considered part of the frame for length calculations.
Destination MAC Address (6 bytes): This identifies the intended recipient(s):
Switches use this address to determine which port(s) should receive the frame.
Source MAC Address (6 bytes): This identifies the sender. It must always be a unicast address (multicast source addresses are invalid). Switches learn MAC addresses by observing source addresses in incoming frames.
EtherType (2 bytes): Common values include:
0x0800: IPv40x0806: ARP (Address Resolution Protocol)0x86DD: IPv60x8100: VLAN-tagged frame (802.1Q)0x8847: MPLS unicastPayload (46-1500 bytes): The minimum payload size of 46 bytes ensures frames are long enough for collision detection to work in classic Ethernet. If the actual data is smaller, padding bytes are added.
The maximum payload of 1500 bytes is the Maximum Transmission Unit (MTU). Larger payloads require fragmentation at higher layers or the use of jumbo frames (up to 9000 bytes in supporting networks).
Frame Check Sequence (4 bytes): A CRC-32 checksum computed over the destination address, source address, EtherType, and payload. The receiver recalculates this value; if it doesn't match, the frame is silently discarded. There is no retransmission mechanism at Layer 2—that responsibility falls to higher layers (e.g., TCP).
Frame sizes are described differently depending on context. The 'frame size' (64-1518 bytes) excludes preamble, SFD, and IFG. The 'on-wire size' (84-1538 bytes minimum) includes everything. For efficiency calculations using the line rate, you must use the on-wire size. For MTU calculations affecting IP fragmentation, only the payload size matters.
Ethernet's success lies in its ability to increase speed by orders of magnitude while maintaining the same frame format and addressing scheme. This backward compatibility protects infrastructure investments and simplifies network design.
Speed Milestones:
| Standard | Speed | Year | Key Innovation |
|---|---|---|---|
| Ethernet | 10 Mbps | 1983 | Original IEEE 802.3 standard |
| Fast Ethernet (802.3u) | 100 Mbps | 1995 | 10x speed with same frame format |
| Gigabit Ethernet (802.3z/ab) | 1 Gbps | 1998/1999 | Full-duplex, eliminated CSMA/CD |
| 10 Gigabit Ethernet (802.3ae) | 10 Gbps | 2002 | Serial transmission, fiber-focused |
| 40/100 Gigabit (802.3ba) | 40/100 Gbps | 2010 | Lane aggregation |
| 25/50 Gigabit (802.3by) | 25/50 Gbps | 2016 | Single-lane optimization |
| 200/400 Gigabit (802.3bs) | 200/400 Gbps | 2017 | Advanced modulation |
| 800 Gigabit (802.3df) | 800 Gbps | 2024 | Next-generation data centers |
Fast Ethernet (100 Mbps):
100BASE-TX became the sweet spot for desktop connectivity through the late 1990s and 2000s. It used the same RJ-45 connectors and Category 5 cabling as 10BASE-T, making upgrades simple. Auto-negotiation allowed 10/100 Mbps devices to coexist on the same network.
Gigabit Ethernet (1 Gbps):
Gigabit Ethernet represented a qualitative shift:
Gigabit Ethernet is now the standard for desktop connectivity in enterprises.
10 Gigabit Ethernet (10 Gbps):
10GbE was designed primarily for backbone and server connectivity:
25, 40, 100, 400 Gigabit and Beyond:
Modern high-speed Ethernet uses sophisticated techniques:
The choice of 25 Gbps as a standard seems arbitrary until you understand lane economics. 100 Gbps achieved with 4x25G lanes is simpler and cheaper than 10x10G lanes. Similarly, 50G (2x25G) and 200G (8x25G) fit the lane structure. The 25G lane rate became the building block for modern high-speed Ethernet.
Switches are the fundamental building blocks of modern Ethernet LANs. They replaced hubs in the 1990s and transformed Ethernet from a shared medium into a switched fabric with dedicated bandwidth per port.
How Switches Work:
Switches operate at Layer 2 (Data Link layer), making forwarding decisions based on MAC addresses:
Learning: When a frame arrives, the switch records the source MAC address and the port it arrived on in the MAC address table (also called CAM table)
Forwarding Decision: The switch looks up the destination MAC address in its table:
Aging: MAC address entries expire after a timeout (typically 300 seconds) if no frames are seen from that address
Dedicated Bandwidth:
In a hub-based network, all devices share the available bandwidth. With 10 devices on a 10 Mbps hub, each device effectively has ~1 Mbps average.
In a switched network, each port has dedicated bandwidth. With 10 devices on a Gigabit switch, each device has the full 1 Gbps available for communication with any other device (limited by the switch's backplane capacity).
Full-Duplex Operation:
Switches enable full-duplex communication—devices can send and receive simultaneously:
Switch Architecture:
Modern switches are sophisticated devices with:
A non-blocking switch can forward traffic at wire speed on all ports simultaneously. For a 48-port Gigabit switch, this requires 96 Gbps of switching capacity (48 × 1 Gbps × 2 for full-duplex). Real enterprise switches often exceed this specification to handle oversubscription from uplinks and internal processing overhead.
Virtual LANs (VLANs) partition a physical LAN into multiple logical networks. Devices in the same VLAN communicate as if on the same physical network, regardless of physical location. Devices in different VLANs require routing to communicate—even if connected to the same switch.
Why VLANs Matter:
IEEE 802.1Q VLAN Tagging:
When frames traverse trunk links (links carrying multiple VLANs), they need a VLAN identifier. IEEE 802.1Q defines a 4-byte tag inserted between the source MAC and EtherType fields:
802.1Q Tag Structure:
| Field | Size | Description |
|---|---|---|
| TPID | 2 bytes | Tag Protocol Identifier (0x8100) |
| PCP | 3 bits | Priority Code Point (QoS, 0-7) |
| DEI | 1 bit | Drop Eligible Indicator |
| VLAN ID | 12 bits | VLAN identifier (0-4095) |
With 12 bits for VLAN ID, 802.1Q supports 4094 usable VLANs (0 and 4095 are reserved).
Port Types:
Inter-VLAN Routing:
Devices in different VLANs cannot communicate directly—they require routing. Options include:
Attackers may attempt 'VLAN hopping' to access VLANs they shouldn't reach. Techniques include switch spoofing (negotiating trunk status) and double tagging. Countermeasures: disable DTP, use a dedicated native VLAN, tag native VLAN traffic, and place unused ports in an unused VLAN.
Spanning Tree Protocol (STP) prevents loops in switched Ethernet networks. Without loop prevention, a single broadcast frame in a looped topology would circulate forever, consuming all bandwidth—a broadcast storm.
Why Loops Are Deadly:
Consider two switches connected by two links:
Within seconds, the network becomes completely saturated. CPU utilization on switches spikes. Legitimate traffic cannot get through. This is why loops must be prevented.
How STP Works:
STP (IEEE 802.1D) creates a loop-free logical topology by blocking redundant paths:
Root Bridge Election: Switches exchange BPDUs (Bridge Protocol Data Units) and elect a root bridge based on lowest Bridge ID (priority + MAC address)
Root Port Selection: Each non-root switch selects one root port—the port with the lowest cost path to the root bridge
Designated Port Selection: For each network segment, one designated port is selected (the port with lowest cost to root bridges the segment)
Port Blocking: All other ports are placed in blocking state—they don't forward data frames but continue listening for BPDUs
| State | Learns MACs | Forwards Data | Duration |
|---|---|---|---|
| Blocking | No | No | Until topology change |
| Listening | No | No | Forward delay (15 sec) |
| Learning | Yes | No | Forward delay (15 sec) |
| Forwarding | Yes | Yes | Stable state |
| Disabled | No | No | Administratively disabled |
STP Convergence:
When topology changes occur (link failure, new switch added), STP must reconverge. Classic 802.1D convergence takes 30-50 seconds—unacceptable for modern networks.
Rapid Spanning Tree (RSTP - 802.1w):
RSTP provides sub-second convergence through:
Multiple Spanning Tree (MSTP - 802.1s):
MSTP maps multiple VLANs to spanning tree instances. Instead of running 100 separate STP calculations for 100 VLANs, VLANs are grouped into a smaller number of instances. This provides:
Modern data center fabrics often avoid STP entirely using technologies like TRILL (Transparent Interconnection of Lots of Links), SPB (Shortest Path Bridging - 802.1aq), or proprietary fabric solutions. These enable multipath forwarding at Layer 2, using all available links simultaneously rather than blocking redundant paths.
While Ethernet dominates today's LANs, understanding alternative technologies provides historical context and explains why certain design principles exist. Some alternatives also persist in specialized applications.
Token Ring (IEEE 802.5):
IBM's Token Ring (1985) used token-passing for media access:
Why Token Ring Lost:
FDDI (Fiber Distributed Data Interface):
FDDI (1987) operated at 100 Mbps over fiber:
ATM (Asynchronous Transfer Mode):
ATM emerged in the 1990s as a unified networking technology for LANs, WANs, and telecommunications:
ATM's LANs (LANE): ATM LAN Emulation (LANE) provided Ethernet-like service over ATM infrastructure. However, the complexity and cost couldn't compete with switched Ethernet.
ATM's Legacy: While ATM failed in the LAN, its influence persists:
Wireless LAN (IEEE 802.11):
Wi-Fi deserves special mention as the only significant alternative to Ethernet that succeeded:
Ethernet's victory wasn't inevitable—it was strategic. Ethernet embraced 'good enough' simplicity and rapid speed increases. Competing technologies offered theoretical advantages (deterministic access, QoS, longer distances) but at higher cost and complexity. The market repeatedly chose 'cheap, fast, and simple' over 'sophisticated and expensive.'
We've explored the technologies that power Local Area Networks, with deep focus on Ethernet—the dominant technology—while understanding the historical alternatives that shaped network design principles.
What's Next:
Now that we understand LAN technologies, we'll explore the components that comprise a LAN. The next page examines switches, access points, cabling, and other infrastructure elements—how they work, how to select them, and how they combine to create functional networks.
You now understand the major LAN technologies—particularly Ethernet's architecture, evolution, and mechanisms. This knowledge forms the foundation for understanding LAN components, design, and troubleshooting covered in subsequent pages.