Network and IP Planning · #13
Online MTU and MSS Calculator
Calculates the inner MTU and TCP MSS (clamping) value from encapsulation overhead.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
When a tunnel or PPPoE is added, some packets no longer fit the path; if ICMP 'fragmentation needed' messages are blocked, some websites load and others hang. The fix is usually the right MTU and TCP MSS clamping value. The tool calculates both from the overhead and IP version.
How to use it
- Enter the MTU of the physical path (1500 for Ethernet).
- Choose the encapsulation or choose 'Custom' and enter the overhead in bytes.
- Choose the IP version and TCP header length (20 B without options; 32 B with timestamps).
Fields
- Path MTU
- IP MTU of the physical interface; usually 1500 on Ethernet.
- Encapsulation
- Values are common overheads; IPsec overhead varies with cipher and padding.
- Custom overhead
- Only with 'Custom'.
- Inner IP version
- IPv4 header 20 B, IPv6 header 40 B.
- TCP header
- 20 B without options; 32 B with the timestamp option.
Worked example
| Input | Value |
|---|---|
| Path MTU | 1500 |
| Encapsulation | None |
| Inner IP version | IPv4 |
| TCP header | 20 |
Expected result: 1500 − 20 B IPv4 − 20 B TCP → MSS 1460 B.
1460 B is the standard MSS on plain Ethernet. With PPPoE on the same line the inner MTU drops to 1492 and the MSS to 1452; set that value as MSS clamping on PPPoE routers.
Second scenario
| Input | Value |
|---|---|
| Path MTU | 1500 |
| Encapsulation | PPPoE (8 B) |
| Inner IP version | IPv4 |
| TCP header | 20 |
Expected result: PPPoE: inner MTU 1492 B, MSS 1452 B.
Method and assumptions
Inner MTU = path MTU − encapsulation overhead. MSS = inner MTU − IP header − TCP header.
PPPoE adds 8 B, GRE (new IPv4 + GRE) 24 B, VXLAN (outer IPv4 + UDP + VXLAN + inner Ethernet) 50 B. IPsec ESP tunnel overhead depends on algorithm, IV and padding; the listed values are common upper bounds, enter your own cipher suite's value with 'Custom'.
The minimum IPv6 link MTU is 1280 B (RFC 8200); anything below is an error. For IPv4, below 576 B gives a warning.
Using the result and troubleshooting
Apply the MSS as TCP MSS clamping on the tunnel interface or firewall (Cisco: ip tcp adjust-mss). TCP sessions then work even where ICMP is blocked.
UDP traffic (some VPNs and VoIP) is not affected by MSS clamping; lower the interface MTU for that traffic too.
Limits and common mistakes
- It does not measure the real path MTU; use
ping -f -l(Windows) orping -M do -s(Linux). - An 802.1Q tag is layer-2 overhead and does not reduce the IP MTU, so it is not listed.
Frequently asked questions
Why 1492 with PPPoE?
PPPoE adds 8 bytes (6 B PPPoE header and 2 B PPP protocol field); 1492 B remain of the 1500 B Ethernet payload.
Related tools and service
- Uplink Oversubscription CalculatorCalculates the ratio of total downlink to uplink capacity normally and after losing one uplink.
Related service: Metro Ethernet and Internet Line Management