This is a follow-up to my previous post about some mysterious TCP connection timeouts in the UC Berkeley wired network.
I received many thoughtful emails in response to that post, and there was an excellent discussion on Hacker News. I’m very grateful to everyone who spent time helping with my ridiculous home networking issues.
Since then, I’ve learned some new information that (mostly) solves the mystery. In this post, I’ll first summarize the main theories people suggested, then tell the story of how a Bunny CDN engineer came to the rescue, and finally describe the root cause.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

The post discusses the theories behind TCP connection timeouts in the UC Berkeley wired network, the contribution of a Bunny CDN engineer in solving the mystery, and the potential security vulnerability in the UC Berkeley network.

asymmetric routing around the firewall