3 ms·

> to discover its public IP:PORT What about switches that want to run from behind a NAT? Could it be that UDP was chosen with this in mind? (http://en.wikipedi

> to discover its public IP:PORT What about switches that want to run from behind a NAT? Could it be that UDP was chosen with this in mind? (http://en.wikipedia.org/wiki/UDP_hole_punching http://en.wikipedia.org/wiki/UDP_hole_punching)

alberich 14y ago
I was wondering how this approach deals with systems running behind NAT also. With IPv6 not happening anytime soon, there will be a large number of systems without individual public addresses available. Routing this UDP packets may require tweaking firewall rules, etc.
medecau 14y ago
Switches behind NAT either have to configure a port to receive UDP directly or depend on some other switch for hole-punching.
arnoldb0620 14y ago
if server a is behind a nat, it first needs to send out a message to server b this will open a random port for typically 60 seconds automatically. Then another message will need to originate from server a within the 60 second time period in order to keep the port open. http://en.wikipedia.org/wiki/NAT_traversal http://en.wikipedia.org/wiki/NAT_traversal