What it is
MTU stands for maximum transmission unit. It is the largest IP packet a link will carry in one piece. Most Ethernet networks use 1500 bytes. That number includes the IP header. The Ethernet frame around it adds more bytes on the wire, so do not compare an MTU setting to a frame capture without allowing for that.
Each link on a path can have a different MTU. Your laptop may use 1500, a VPN may use 1400, and a cloud tunnel may use 1450. The path MTU is the smallest value between two hosts. A packet can fit the first hop and still be too large for a later one. The router then fragments it or drops it and sends an error.
MTU is not bandwidth. Larger packets cut per packet overhead, which is why storage networks use jumbo frames of 9000 bytes. They do not make a slow link fast. On mixed networks a large MTU is a liability if one device or tunnel cannot handle it. Stay at 1500 unless you control every hop.
How it works
A host compares each IP packet to its local MTU. IPv4 can fragment a large packet before sending, but many applications set the don't fragment flag. Routers then drop the packet instead of splitting it. The router should return an ICMP message saying the packet was too big and reporting the next hop MTU. The host lowers its size and retries. That process is path MTU discovery.
IPv6 routers do not fragment packets. The sender must use path MTU discovery or keep packets small. That makes blocked ICMP a bigger problem on IPv6. If a firewall drops the error, the sender never learns the limit. It keeps retrying the same large packet and the connection stalls. Engineers call this a PMTUD black hole.
TCP adds its own limit. During the handshake each side advertises a maximum segment size, or MSS. The MSS is the largest TCP payload it can accept, based on the MTU minus the IP and TCP headers. A router or firewall can rewrite that value as packets pass. This is called MSS clamping. It helps when a tunnel lowers the MTU but the endpoints still assume 1500. MSS clamping covers TCP only. UDP needs its own size check.
Why it matters for a business
MTU problems appear as odd application failures, not a dead link. A user can open a site, log in and load a small page, then watch a file upload hang. A VPN session can work until a large response arrives. An API call with a small request may work while a larger response times out. Teams blame the app, the Wi-Fi or the ISP when the limit sits in a tunnel or firewall.
The cost is time and trust. Staff retry uploads, customers see stalled forms, and remote workers lose access to files. Tickets take longer because small pings succeed and basic checks look clean. Cloud and hybrid designs add more places for a mismatch. Site-to-site VPNs, load balancers, container overlays and private links all add headers. A packet sent at 1500 bytes can exceed the limit once it is wrapped for a tunnel.
Common mistakes
One mistake is turning on jumbo frames everywhere because a storage team uses them. Jumbo frames need every switch, router, firewall, virtual switch and network card on the path to agree. One 1500 byte device in the middle will drop the larger packets. Keep jumbo frames inside a controlled segment.
Another mistake is blocking all ICMP. Path MTU discovery depends on ICMP fragmentation needed messages. If you block them, large packets vanish and users see timeouts. Allow the specific ICMP types you need at the edge and log them.
Teams also test only one direction. The return path can differ. A ping from a branch to a cloud server may pass while the reverse direction fails. Test with the same VPN, firewall and route the application uses.
A final trap is assuming a large ping proves the whole path. ICMP may be handled differently from TCP. A firewall may allow ping while blocking the ICMP errors that TCP needs. Capture packets at both ends when you can. Look for repeated retransmissions of the same large packet.
How to get started
Map the paths that matter: office to cloud, VPN to data center, partner link and any overlay. For each path, note the MTU at every hop and the header size each tunnel adds. Test from a real client with the don't fragment flag. On Linux, ping -M do -s 1472 sends a 1500 byte IP packet because 28 bytes go to the IP and ICMP headers. Lower the size until it passes, then add 28 to get the path MTU. Windows uses ping -f -l 1472, and macOS uses ping -D -s 1472.
Fix the cause at the narrowest point. If a VPN tunnel is the limit, set the tunnel MTU and clamp TCP MSS on both endpoints. If a firewall blocks ICMP, allow fragmentation needed messages from the routers on the path. If a cloud network uses an overlay, check its documented MTU and subtract it from the underlay. Change one setting at a time and retest the same application flow.
Add MTU checks to your change process. Any new tunnel, load balancer, container network or firewall rule can change the path MTU. Record the value in your network diagram and test it after the change. Watch for retransmissions and timeouts on large transfers, not only link status. When the path is complex, an outside review can save guesswork. Cloudverg's Expert architecture session is $450/month and includes a 90-minute video call with a senior architect plus a written summary.
Frequently asked questions
What is MTU in simple terms?
MTU is the largest IP packet a link will carry without splitting it. Most Ethernet links use 1500 bytes. The path MTU is the smallest link MTU between two hosts, so a tunnel or firewall can lower it even when your local network is set to 1500.
Why do small pings work but large uploads fail?
Small packets fit every hop, so basic checks pass. Large packets hit a lower MTU and are dropped, often because an ICMP error is blocked or a tunnel is not configured correctly. The link can look healthy while the application stalls on larger transfers.
Should I raise MTU to 9000 on my network?
Only if every device on the path supports jumbo frames and you control the whole path. Mixing 9000 byte hosts with 1500 byte devices causes drops that are hard to trace. Keep jumbo frames inside a tested segment, and route to other networks through a device that handles the size difference.