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.
Re:TCP Client Self-Connect (2013)
by phoenix_x on Monday August 11, 2025 @01:25PM
(#44866895)
Hmm it is not working for MacOS :( I understand that linux and macos network stacks differ. However when I ran the test it and observed the network via wireshark, it seems that my machine does not send a request containing the same source port as the destination port. It just skips it, but anyway MacOS seems to have the same increasing sequential port behavior
I wonder if it's also theoretically possible for a pair of clients to connect to each other like this?
"How NAT traversal works" - https://tailscale.com/blog/how-nat-traversal-works > "The benefits of birthdays"
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