MTU / MSS Calculator

Find the right MSS for your path.

Start from your path MTU, add any encapsulation overhead, and get the effective MTU and the TCP MSS to clamp to — for both IPv4 and IPv6.

calc — mtu/mss
MSS = effective MTU − IP header − TCP header. IPv4 header 20B, IPv6 header 40B, TCP header 20B (no options). IPsec figures are approximate; exact overhead varies by cipher and mode.
Invalid input
Recommended MSS
Path MTU
Overhead
Effective MTU
IPv4 MSS
IPv6 MSS
tcp-mss clamp
How it works

The MTU is the largest frame payload a link will carry — classically 1500 bytes on Ethernet. The MSS is the largest TCP segment of data that fits without fragmenting, so it's the MTU minus the IP and TCP headers.

For plain IPv4: 1500 − 20 (IP) − 20 (TCP) = 1460. For IPv6 the base header is larger: 1500 − 40 − 20 = 1440. Every layer of encapsulation eats into the MTU available to the inner packet, lowering the MSS further.

Why MSS clamping exists

When traffic crosses a tunnel (GRE, IPsec, PPPoE, VXLAN), the added headers shrink the usable MTU. If endpoints still try to send 1460-byte segments, packets need fragmentation — and if the DF bit is set and PMTUD is broken, they're silently dropped. "MSS clamping" rewrites the TCP MSS option during the handshake so both ends agree on a size that fits, avoiding the black hole.

EncapsulationOverheadIPv4 MSS @1500
None01460
802.1Q VLAN41456
PPPoE81452
GRE241436
VXLAN501410
IPsec ESP (approx)~58~1402
FAQ
What's the standard MSS for a 1500-byte MTU?

1460 for IPv4, 1440 for IPv6 (no TCP options).

What MSS should I clamp to over GRE?

With a 1500 MTU and 24 bytes of GRE overhead, clamp IPv4 MSS to 1436. Many engineers clamp to 1400 as a safe round number that also survives an extra layer.

Why are IPsec figures approximate?

ESP overhead depends on cipher, block padding, authentication, and tunnel vs transport mode. Treat the IPsec presets as ballpark and verify on your gear.