News for hackers. Stuff that matters.
Re:TCP Client Self-Connect (2013) by Retr0id on Monday August 11, 2025 @01:57AM (#44861109)
Can confirm that it still works in 2025, and also via netcat.

I wonder if it's also theoretically possible for a pair of clients to connect to each other like this?

Re:TCP Client Self-Connect (2013) by LeoPanthera on Monday August 11, 2025 @02:14AM (#44861183)
The tailscale client does this trick to force its way through NAT-to-NAT connections.

"How NAT traversal works" - https://tailscale.com/blog/how-nat-traversal-works > "The benefits of birthdays"

Re:TCP Client Self-Connect (2013) by fenesiistvan on Monday August 11, 2025 @08:48AM (#44863556)
The tailscale article is about UDP, but here we are talking about TCP.
Re:TCP Client Self-Connect (2013) by bmenrigh on Monday August 11, 2025 @02:12AM (#44861178)
Yeah a pair of clients can via “tcp simultaneous open” but you’ll need to arrange for each client to know about the source port of the other. So bypass the usual ephemeral port choice made by the OS. And it’s still highly sensitive to timing.
Re:TCP Client Self-Connect (2013) by dilyevsky on Monday August 11, 2025 @06:36PM (#44870254)
> I wonder if it's also theoretically possible for a pair of clients to connect to each other like this?

RFC793 actually specifically calls this out as one of the supported ways of two endpoints establishing a TCP connection[0]. The fact that it works on the same host via src port collision is just a happy accident.

[0] - https://www.rfc-editor.org/rfc/rfc793.html#section-3.4