News for hackers. Stuff that matters.
Re:JSON+UDP+DHT=Freedom by klibertp on Thursday August 23, 2012 @03:44AM (#4421342)
> 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)

Re:JSON+UDP+DHT=Freedom by alberich on Thursday August 23, 2012 @06:05AM (#4421622)
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.
Re:JSON+UDP+DHT=Freedom by arnoldb0620 on Thursday August 23, 2012 @08:07AM (#4421903)
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

Re:JSON+UDP+DHT=Freedom by medecau on Thursday August 23, 2012 @06:06AM (#4421623)
Switches behind NAT either have to configure a port to receive UDP directly or depend on some other switch for hole-punching.