Path MTU Discovery (PMTUD)
What is Path MTU Discovery (PMTUD)?
Path MTU Discovery (PMTUD) is how a sender finds the largest packet a route's links can carry without fragmenting it, retrying smaller after a router reports its own limit back over ICMP. AdminKit's TLS/SSL check helps tell a stalled handshake caused by a blocked PMTUD message apart from a real certificate problem.
By AdminKit team, Netbase JSC · Updated
Path MTU Discovery (PMTUD), defined in RFC 1191 (IETF Datatracker lists it as a Draft Standard) for IPv4 and RFC 8201 for IPv6, is how a sender finds the largest packet size — the maximum transmission unit, or MTU — that every link along a route to a destination can carry without fragmenting it. A sender transmits packets with the “don’t fragment” flag set; if a router along the path has a smaller MTU than the packet, it drops the packet and sends back an ICMP “fragmentation needed” (IPv4) or “packet too big” (IPv6) message naming the smaller size, and the sender retries at that size — Cloudflare’s explanation of MTU and PMTUD walks through the same don’t-fragment-flag-and-ICMP-reply sequence for both IPv4 and IPv6. The common failure mode is a firewall or middlebox blocking that ICMP message outright, intending to block unwanted ICMP traffic generally: the oversized packet is still silently dropped, but the sender never learns why, so a connection can complete its initial handshake with small packets and then stall indefinitely once it tries to send something larger — a large TLS certificate chain or a file transfer, for example — a symptom often mistaken for an unrelated problem. Operating systems make the handling of those ICMP messages configurable: the Linux kernel’s IP sysctl documentation describes ip_no_pmtu_disc, whose mode 2 discards incoming Path MTU Discovery messages and whose hardened mode 3 accepts fragmentation-needed errors only when the protocol, currently TCP or SCTP, can verify them. QUIC avoids relying on ICMP for this and instead probes path MTU directly at the transport layer, a technique called DPLPMTUD, defined in RFC 8899.
A dual-stack client runs PMTUD independently over each path it might use, including whichever one Happy Eyeballs ends up selecting for a given connection.
AdminKit groups path MTU Discovery (PMTUD) under its IP & network cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
How does a sender normally learn its path's MTU?
It transmits packets with the 'don't fragment' flag set; if a router along the path has a smaller MTU, it drops the oversized packet and sends back an ICMP message naming the smaller size, and the sender retries at that size.
What causes a PMTUD 'black hole'?
A firewall or middlebox blocking the ICMP 'fragmentation needed' or 'packet too big' message outright -- the oversized packet is still silently dropped, but the sender never learns why, so a connection can stall once it tries to send something larger than the small initial handshake packets.
Why does a PMTU black hole get mistaken for a certificate problem?
Because the connection completes its initial handshake fine with small packets and only stalls indefinitely later when it tries to send something larger, like a large TLS certificate chain -- a symptom that looks unrelated to MTU at first glance.
Does every protocol rely on ICMP for path MTU discovery?
No -- QUIC avoids relying on ICMP for this and instead probes path MTU directly at the transport layer, a technique called DPLPMTUD, defined in RFC 8899.