A most elegant TCP hole punching algorithm

Uptrenda 16 points 2 comments March 15, 2026
robertsdotpm.github.io · View on Hacker News

Discussion Highlights (2 comments)

jcalvinowens

If you're asking "where is the listener", you don't need one: https://datatracker.ietf.org/doc/html/rfc9293#simul_connect

EnigmaCurry

> Many home routers try to preserve the source port in external mappings. This is a property called “equal delta mapping” – it won’t work on all routers but for our algorithm we’re sacrificing coverage for simplicity. It is precisely this point that has flummoxed me when connecting my p2p wireguard config[1] with a friend that uses a pfsense router, no matter what we tried, pfsense always chooses a random source port. But in the simple case this blog outlines, if both ends use the same source port, this method punches through 2 firewalls effortlessly: [1] https://blog.rymcg.tech/blog/linux/wireguard_p2p/

Semantic search powered by Rivestack pgvector
3,471 stories · 32,344 chunks indexed