Networking: SSH/HTTPS connects but hangs on large data — path MTU discovery black hole
Small packets pass but full-size ones vanish, so logins work and then transfers or page loads stall.
PMTU black holeSSH hangs after bannerconnection hangs on large packets MTUTLS handshake stalls Server Hello MTUpath MTU discovery blackhole Meaning
A device on the path has a lower MTU and ICMP "fragmentation needed" messages are blocked, so the sender never learns to send smaller packets. Clamp the MSS on the tunnel/router, lower the interface MTU, or allow ICMP type 3 code 4. Typical signs: ssh stalls after the banner, TLS stalls at Server Hello.
Common causes
- Firewall dropping ICMP type 3 code 4
- VPN/tunnel MTU lower than the LAN MTU
- PPPoE (1492) or cloud overlay overhead
- MSS not clamped on the gateway
- Mismatched MTU on one hop
⚡ Quick fix
- Test sizes:
ping -M do -s 1400 hostand step up - Clamp MSS:
iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu - Allow ICMP type 3
Detailed fix by platform
Linux
sudo iptables -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
How to diagnose
- Small requests — Work?
- Large transfers — Hang?
- ICMP type 3 — Allowed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- Frag needed and DF set (ICMP type 3 code 4) Networking: ping: local error: message too long, mtu=1500 / Packet needs to be fragmented but DF set
- High TCP retransmissions / packet loss Networking: netstat -s: segments retransmitted / Wireshark: TCP Retransmission, TCP Dup ACK — packet loss on the path
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026