On 5 aug 2008, at 16:09, Rémi Denis-Courmont wrote:
What's the difficulty with TCP? If I understand things correctly,
once
you use a certain port as a source port number on the public side, a
behave-compliant NAT will forward incoming sessions towards that port
number to you. So the only thing the application has to do is figure
out what the address/port is that others see and not release the port
number and it's in business.
The passive side of the TCP connections can hardly be behind a NAT.
Isn't that the whole point of endpoint independent NATing?
I first open a session with source port 10 and destination address X.
The NAT rewrites the source port into 93 and the source address into
Y. The server at X tells me values 93 and Y. I then start listening on
port 10 and tell others to contact me on Y port 93.
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
