Aqua Blue Network

Tracking down an MTU black hole

October 2026

The symptom is always the same: small requests work, large transfers stall. SSH logs in but hangs as soon as a command prints a screenful of text. A web page loads its HTML and then waits forever for the stylesheet.

What usually happens is that a link somewhere on the path has a smaller MTU than both ends believe, and the ICMP “fragmentation needed” replies that should report it are being dropped.

Confirming it

Send packets with the don’t-fragment bit set and shrink them until they pass:

ping -M do -s 1472 example.net   # 1500 bytes on the wire
ping -M do -s 1400 example.net
tracepath -n example.net

If 1472 fails silently and 1400 succeeds, something in between is eating the difference. tracepath usually points at the hop where the path MTU drops.

Fixing it

The clean fix is to let ICMP type 3 code 4 through every firewall on the path. When the broken hop is not yours, enabling packetization-layer discovery on the hosts is a reasonable workaround:

sysctl -w net.ipv4.tcp_mtu_probing=1

On a router, clamping the TCP MSS to the path MTU does the same job for everything behind it.