MTU / Fragment

Send a packet over links with smaller MTUs and see how IPv4 fragments it, plus how DF and PMTUD change the outcome.

A free protocol simulators tool from NetOcta that runs entirely in your browser — no sign-up or install.

About this tool

MTU is the largest IP packet a link can carry without fragmentation. When a packet is too large, IPv4 fragmentation or path MTU discovery explains what happens next. This simulator shows those choices and the problems caused when feedback is blocked. Begin with packet size versus link size, then inspect flags, fragment offsets and the destination's reassembly role.

How it works

  1. Choose a fragmentation or path-MTU scenario.
  2. Compare the displayed IP packet length with the outgoing MTU.
  3. Inspect the DF flag and resulting fragments or ICMP feedback.
  4. Follow delivery or the sender's smaller-packet retry.

Worked example

For 2,000 payload bytes, a 20-byte IPv4 header and MTU 1,000, non-final fragment payloads must fit and be multiples of 8. Use 976, 976 and 48 payload bytes: total lengths 996, 996 and 68. Offsets are 0, 122 and 244 in eight-byte units; only the last fragment has MF clear.

Common mistakes

MTU includes the IP header. Do not overlook eight-byte alignment when calculating non-final fragments. Intermediate IPv6 routers never fragment forwarded packets. Blocking necessary ICMP feedback can create a path-MTU black hole.

FAQ

Where are IPv4 fragments reassembled?

At the destination, not each router. Losing a required fragment prevents successful reassembly of that datagram, even if its other fragments arrived.