Skip to main content
networking

Fragmentation

IP fragmentation splits packets larger than the link MTU into smaller fragments for transmission, reassembled at the destination. Fragmentation hurts performance – any single lost fragment requires retransmitting the entire original packet. IPv6 does not allow router fragmentation; only endpoints can fragment.

Definition

When an IP packet exceeds the MTU of a link it must traverse, the router can fragment it into smaller pieces (IPv4 only – IPv6 requires the source to size packets correctly). Each fragment carries the same Identification field and an offset indicating where it fits in the original packet. The destination reassembles fragments using these fields. Fragmentation causes problems: losing any single fragment means the entire packet must be retransmitted, fragments increase reassembly buffer usage at the destination, and stateful firewalls must track fragments to apply rules consistently. Path MTU Discovery (PMTUD) avoids fragmentation by probing the path with DF (Don't Fragment) set – routers respond with ICMP Fragmentation Needed if the packet is too large. Setting DF and relying on PMTUD is the modern best practice. Firewalls that block ICMP break PMTUD and cause black-hole symptoms for large packets.

Examples

  • ping -M do -s 1473 host – DF set, fails if MTU < 1501
  • ip -s link show dev eth0 | grep frag – fragment counters
  • sysctl net.ipv4.ipfrag_high_thresh – kernel reassembly buffer limit

Related Protocols

Related Terms