Why Ethernet MTU Is 1500 Bytes: Historical and Technical Reasons
This article explains why the Ethernet maximum transmission unit (MTU) settled on 1500 bytes, covering early hardware constraints, cost considerations, the emergence of jumbo frames, modern traffic analysis, and why changing this long‑standing value remains difficult.
Ethernet is ubiquitous, and virtually every hardware vendor implements it; a common parameter for all Ethernet links is the MTU (Maximum Transmission Unit), which defines the largest packet size that can be transmitted without fragmentation.
In most LANs the MTU is about 1500 bytes, a value also widely used on the Internet, although other link‑layer technologies can support larger packets.
For example, Wi‑Fi (802.11) typically uses an MTU of 2304 bytes, fiber links around 4352 bytes, and Ethernet itself can be configured for “jumbo frames” up to 9000 bytes when the NIC, switch, and router all support it.
Despite these larger possibilities, the Internet backbone largely sticks to the 1500‑byte MTU to avoid fragmentation across heterogeneous networks.
Historically, the 1500‑byte figure emerged from early Ethernet design constraints: hardware buffer sizes, cost of larger NICs, and the need to keep transmission delays and header overhead reasonable. An early email (cited by the author) noted that a larger MTU would increase NIC cost and hinder Ethernet’s widespread adoption.
Early Ethernet used shared coaxial cable or hubs, allowing only one packet on the segment at a time, so a modest MTU helped keep transmission times short.
Modern traffic analysis, such as data from the AMS‑IX exchange point, shows that about 20 % of packets observed are at the maximum length, indicating significant bandwidth consumption by packet headers.
Combining traffic graphs from backbone and LAN measurements reveals that packet headers can consume a large portion of bandwidth, with peak‑traffic overhead estimated at 246 Gbit/s. If the entire network used jumbo frames, the overhead would drop to roughly 41 Gbit/s.
Nevertheless, changing the Internet’s collective mindset about MTU is extremely difficult; many operators still run with the traditional 1500‑byte MTU.
If you want to learn more about the history of the 1500‑byte Ethernet MTU, you can contact the author at [email protected] .
$ ip l 1: lo: mtu 65536 state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp5s0: mtu 1500 state UP link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
Images in the original article illustrate the traffic distribution and the proportion of large packets.
High Availability Architecture
Official account for High Availability Architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.