Kernaali Tools
References

Ethernet, MTU & TCP MSS Quick Reference

A one-page A4 reference for frame size, VLAN overhead, IP MTU, TCP MSS and tunnel budgeting.

One A4 page · 100% scale · turn off browser headers and footers.

Ethernet, MTU & TCP MSS Quick ReferenceKERNAALI / FIELD REFERENCE

Count at the right layer

Ethernet frame: destination + source + type (14 B) | VLAN tags (4 B each) | payload / padding | FCS (4 B). Preamble/SFD (8 B) and interframe gap (12 byte-times) consume link time outside that frame.

QuantityBaselineWhat is included
Ethernet IP MTU1,500 BEntire IP packet; excludes Ethernet header and FCS
Untagged frame1,518 B1,500-byte payload + 14-byte header + 4-byte FCS
One VLAN tag1,522 BSame IP packet; an extra 4 bytes at Layer 2
Two VLAN tags1,526 BSame IP packet; 8 bytes of tags
Minimum untagged frame64 BIncludes FCS; payload is padded if necessary
IPv4 header20 B minimumOptions can increase it
IPv6 base header40 BExtension headers add more
TCP header20 B minimumOptions can increase it
UDP header8 BNo TCP MSS negotiation

TCP data budget

Base MSS = IP MTU − fixed IP header − fixed TCP header. With MTU 1,500: IPv4 MSS 1,460; IPv6 MSS 1,440.

The advertised MSS option uses the fixed headers. A sender reduces actual payload for TCP options and IPv6 extensions. Twelve bytes of TCP options leave 1,448 bytes of IPv4 data in a 1,500-byte packet.

MSS clamping affects TCP. It does not repair oversized UDP packets or replace path-MTU discovery.

Tunnel worksheet

Start from the underlay IP MTU. Subtract outer IP, tunnel headers, authentication and worst-case padding. Then subtract the inner IP and transport headers for a data budget.

An illustrative 1,500-byte underlay with a verified 60-byte encapsulation budget leaves 1,440 bytes of inner IP MTU and base IPv4 TCP MSS 1,400.

Overhead varies. GRE options, ESP cipher/padding, NAT-T, additional tunnels and PPPoE change the result. Do not apply one fixed deduction to every VPN.

Symptoms and checks

Small pings work but large transfers stall: inspect path MTU, allow needed ICMP/ICMPv6 errors, and test both directions. A capture may omit FCS or VLAN tags due to offload. Interface counters and capture sizes may therefore count different bytes. Jumbo-frame limits must match across the entire path.

Technical references

Found an issue? Send a correction with a reproducible example.