Tunnel MTU mismatches and missing ICMP feedback can create black holes. Separate loss, interface errors and path-MTU evidence; an intermediate hop that ignores probes is not proof of a broken router.
Scope and prerequisites
Use low probe rates and authorized destinations. ping may require network capabilities. IP MTU differs from payload size: IPv4 without options uses 28 extra bytes for IP and ICMP, making 1472 bytes fit a 1500-byte packet. VPNs and encapsulation reduce the effective budget.
1. Collect evidence
Compare interface error/drop counters across two timestamps. Run small pings and tracepath to the same destination. Destination loss matters more than missing ICMP replies from one intermediate router, which may rate-limit probes while forwarding traffic normally. Include return-path and peak-period observations.
ip -s link
ping -c 5 example.com
tracepath example.com
2. Make a controlled change
For IPv4, reduce ping size gradually with -M do instead of assigning a guessed MTU everywhere. A failed large ping alone is insufficient because ICMP may be filtered. Small-packet success plus large-transfer failure and PMTU evidence strengthens the hypothesis; corroborate with actual TCP/TLS traffic.
# IPv4, low rate; decrease payload size to compare results.
ping -4 -c 3 -M do -s 1472 example.com
ping -4 -c 3 -M do -s 1400 example.com
tracepath -6 example.com
3. Verify the outcome
Change MTU only on the responsible interface or tunnel with out-of-band access available. The diagnostic example deliberately avoids network-changing commands that could sever management. Recheck large transfers, TLS and destination loss afterward. Firewall policy must correctly handle IPv4 Fragmentation Needed and IPv6 Packet Too Big.
curl -I --connect-timeout 5 --max-time 15 https://example.com/
ss -ti
ip -s link
Rollback and prevention
Record the old value and network-manager configuration for rollback. MSS clamping can help tunneled TCP, but does not fix every UDP flow or the root MTU issue. Do not hide congestion, NIC faults or genuine packet loss by lowering MTU. Monitor retransmissions and endpoint quality alongside latency.
Technical references
For related checks in this workflow, see Troubleshoot IPv6 Websites When IPv4 Works and Troubleshoot Docker DNS and Service-to-Service Networking.
