MSK · UTC+3 · 18 Nov 2026note

← back

MTU, MSS and the packets that quietly disappear

networking12 Nov 2026 · 4 min read

Ping works, SSH works, the web server answers — and one file, one API call, one image upload hangs forever. That pattern is almost always an MTU problem, and it stays invisible because small packets fit and large ones do not.

Why small works and large does not

A TCP handshake is a few dozen bytes. A TLS handshake is a couple of kilobytes. When the path MTU is smaller than what the sender assumes, the first packets get through and the first full-size segment is dropped somewhere in the middle. Nothing reports the drop; TCP just retransmits and backs off.

Routers in the path are supposed to send ICMP “fragmentation needed”. Many networks filter that ICMP, which is exactly why this bug survives for months.

client · MTU 1500 link · MTU 1400 server · MTU 1500 SYN, handshake — fits full segment — dropped
The handshake never exceeds 1400 bytes, so it passes. The first full-size segment does not, and the connection appears to hang.

How to see it

Ping with a fixed size and the “do not fragment” bit:

ping -M do -s 1472 10.0.0.1
ping -M do -s 1400 10.0.0.1
ping -M do -s 1200 10.0.0.1

If 1472 fails and 1400 works, the path MTU is somewhere between 1428 and 1500. Then confirm on the host side — a socket stuck at a tiny MSS is a strong signal:

ss -tin dst 10.0.0.1
# look for: mss:536, retrans, lost

And on the wire, the retransmissions are visible without any guessing:

tcpdump -ni any -s 0 'host 10.0.0.1 and tcp' -c 200

What actually fixes it

Then repeat the same three pings. The fix is boring, which is the point.