Separate one link from the complete path
In an IP context, a link MTU is the largest IP packet that a link can carry. A path crossing several links is constrained by the smallest applicable MTU along that path. A source interface capable of sending large packets does not prove that those packets can reach the destination unchanged. MTU also differs from application body size: an IP packet includes headers. State the protocol layer whose bytes are counted before subtracting overhead or comparing measurements from a host, an interface, and an application.
Subtract headers in a qualified example
For a path MTU of 1,500 bytes, an IPv4 header of twenty bytes and a TCP header of twenty bytes leave 1,460 bytes for TCP data, assuming no extra options or other overhead. Using the forty-byte IPv6 base header and a twenty-byte TCP header leaves 1,440 bytes under similarly simplified conditions. Options, extension headers, and tunnel encapsulation can change the usable size. TCP’s maximum segment size concerns the data carried by TCP, so an MTU of 1,500 must not simply be copied into an MSS assumption of 1,500.
Understand how an oversized packet is handled
An IPv6 router does not fragment a packet while forwarding it. If the packet is too large for the next link, an ICMPv6 Packet Too Big message can inform the source so it can adjust its sending size. IPv4 path MTU discovery uses its own fragmentation-control and notification mechanisms. Sources also need to validate relevant information and adapt when paths change. Do not assume that every intermediate device will automatically split a packet in whatever way makes the application succeed. The behavior depends on the protocol and the packet’s fragmentation rules.
Investigate size-dependent failures carefully
A connection can complete its handshake and handle small exchanges while larger transfers stall, making a path-MTU problem one possible explanation. Tunnel headers may reduce usable space, and blocked control messages can prevent the source from learning a smaller limit. The symptom is not proof by itself. Compare direction, packet size, notifications, and retransmissions, and identify the observation point. Segmentation offload can make a host capture show a large segment that is split before transmission on the wire. Lowering MTU without this context can hide the immediate problem while leaving the underlying configuration or notification failure unexplained.