Hacker News new | ask | show | jobs
by kika 4639 days ago
To successfully traverse many NATs you need a third party, which is already accessible from two parties trying to handshake.
1 comments

Yep, that's what I meant by "accessible" too. But with Hamachi, there's a central service for client authentication. With freelan, peers authenticate directly via signed crts.
I looked into this heavily over the past few days. The punchline is this needs support for NAT traversal and some type of out-of-band way for clients to find each other.

NAT traversal is an implementation thing, and I favor Jabber as the out-of-band these days since everyone can get at least a GTalk account.

Though we now have libjingle, which basically merges both of these things and would probably elegantly solve the problem. But p2p vpn's aren't much use if you have to control the NAT router you're attached to.

> I favor Jabber as the out-of-band these days since everyone can get at least a GTalk account.

Isn't that deprecated in favour of Google Hangouts?

Whatever they're calling it, you can still get free XMPP accounts easily.
If it has been tied to hangouts then it has been tied to g+ and their ridiculous policies, I hardly class it as a good alternative.
Doesn't seem to be a problem with connecting with Pidgin, and I had it working with Wippien (sadly Wippien doesn't really work great with Win 7 or Linux).
There are many other options, though: http://xmpp.net/
Isn't the upnp feature of most home routers enough?