MTU Overhead Calculator

Calculate effective payload MTU and recommended TCP MSS after accounting for encapsulation overhead from VLANs, GRE, IPsec, VXLAN, and more.

Built by a network engineerCalculations run locally in your browserNo signup requiredNetwork information is not transmitted to our servers

MTU Overhead Calculator

IPv4 header = 20 bytes, IPv6 header = 40 bytes. Affects TCP MSS calculation.

Encapsulation Layers

58 bytes

IPsec ESP Tunnel (AES-GCM): ESP tunnel mode with AES-GCM adds ~58 bytes (38 ESP + 20 outer IP header). Actual overhead varies by encryption and authentication.

Results

Physical MTU
1500 bytes
IP Version
IPv4
Total Overhead
58 bytes
Effective Payload MTU
1442 bytes
Recommended TCP MSS
1402 bytes
MSS Adjustment
Recommended
Encapsulation overhead reduces effective MTU. Ensure all devices in the path use matching MTU and MSS values to avoid fragmentation.

Note: Exact overhead can vary by protocol options and encryption method. IPsec overhead depends on the encryption algorithm (AES-CBC, AES-GCM), authentication (HMAC-SHA1, SHA-256), and whether tunnel mode or transport mode is used. The values shown are typical estimates for common configurations. For IPv4, the TCP MSS is calculated as effective MTU minus 20 bytes (IP header) minus 20 bytes (TCP header). Always verify with your specific configuration and vendor documentation.

What the MTU Overhead Calculator Does

The MTU overhead calculator computes the effective payload MTU after accounting for encapsulation overhead from tunneling and tagging protocols. It also recommends a TCP MSS (Maximum Segment Size) value to avoid fragmentation, correctly accounting for IPv4 (20-byte header) versus IPv6 (40-byte header). You can stack multiple encapsulation layers to model real-world scenarios like IPsec over GRE over 802.1Q.

How the Calculation Works

The calculator sums the overhead bytes from all selected encapsulation layers and subtracts the total from the physical MTU to get the effective payload MTU. The recommended TCP MSS is the effective MTU minus the IP header size (20 bytes for IPv4, 40 bytes for IPv6) minus 20 bytes for the TCP header. If the effective MTU drops below the IP version minimum (576 for IPv4, 1280 for IPv6), a fragmentation warning is displayed.

Example

For a physical MTU of 1500 with IPsec ESP tunnel mode (AES-GCM) overhead of 58 bytes using IPv4:

  • Effective MTU: 1442 bytes
  • Recommended MSS: 1402 bytes (1442 - 20 IP - 20 TCP)
  • MSS Adjustment: Recommended (set MSS to 1402 on the tunnel interface)

With IPv6 as the inner protocol, the MSS would be 1382 bytes (1442 - 40 IPv6 - 20 TCP) due to the larger IPv6 header.

Common Encapsulation Overheads

  • 802.1Q VLAN: 4 bytes per tag
  • QinQ: 8 bytes (double tagging)
  • GRE: ~24 bytes (base GRE + IP header)
  • IPsec ESP Transport (AES-GCM): ~38 bytes
  • IPsec ESP Tunnel (AES-GCM): ~58 bytes (includes outer IP)
  • IPsec ESP Transport (AES-CBC/HMAC-SHA1): ~42 bytes
  • IPsec ESP Tunnel (AES-CBC/HMAC-SHA1): ~62 bytes
  • VXLAN: 50 bytes (8 VXLAN + 8 UDP + 20 IP + 14 Ethernet)
  • PPPoE: 8 bytes
  • MPLS: 4 bytes per label
  • NAT-T: 8 bytes (UDP encapsulation for IPsec)

Common Use Cases

  • Determining correct MSS clamping values for VPN tunnels
  • Planning MTU for VXLAN-based overlay networks
  • Calculating effective MTU for IPsec site-to-site VPNs in tunnel vs transport mode
  • Troubleshooting fragmentation issues in nested tunnel environments
  • Sizing MTU for IPv6-over-IPv4 tunnels

Important Considerations

Exact overhead can vary by protocol options and encryption method. IPsec overhead, for example, depends on whether you use AES-CBC or AES-GCM, HMAC-SHA1 or SHA-256, and transport mode versus tunnel mode. The values provided by this calculator are typical estimates — always verify against your specific configuration and vendor documentation. Path MTU Discovery (PMTUD) can help detect the actual MTU along a path, but it can fail when ICMP is blocked. In those cases, MSS clamping on the tunnel interface is a common workaround. Note that IPv6 has a minimum MTU of 1280 bytes (RFC 8200), higher than the IPv4 minimum of 576 bytes.

Frequently Asked Questions

What is TCP MSS and why does it matter?

TCP MSS (Maximum Segment Size) is the largest amount of data TCP can send in a single segment. It should be set to the effective MTU minus 40 bytes (20 for IP header, 20 for TCP header) to avoid fragmentation.

Why does my VPN have a lower effective MTU?

VPN protocols like IPsec add encryption headers and encapsulation to each packet, consuming bytes from the physical MTU. For example, IPsec ESP adds approximately 74 bytes, reducing a 1500-byte MTU to 1426.

How do I fix fragmentation issues in tunnels?

Common solutions include increasing the physical MTU (if supported), reducing MSS via TCP MSS clamping on tunnel interfaces, or enabling Path MTU Discovery. If ICMP is blocked along the path, MSS clamping is the most reliable fix.

Technically Reviewed By

Senior Enterprise Network Engineer — 25+ years of IT and network infrastructure experience, including enterprise Cisco switching, routing, wireless, firewalls, VPN, network access control, SD-WAN, and large-scale network operations.

Last reviewed: 2026-09-04

Calculations are performed using standards-based formulas and verified against known reference values. All computation runs client-side in your browser.

Related Resources