Alex,
I'm afraid the citation links seem to be broken (nat.html is missing), so
it's difficult to see any of the supporting documentation for this.
As it stands, UDP hole-punching fundamentally requires that your NAT
router allow UDP traffic through, which is not something most good NAT
NAT2NAT without port configuration is not that hard to implement.
A nat router need to keep the udp ports open for a amount of time,
unlike tcp that close on disconnect.
Using a 3the server you can cross nat info and make a direct connection.
It works for nat routers, it does NOT work if the
James Weatherall wrote:
Alex,
I'm afraid the citation links seem to be broken (nat.html is missing), so
it's difficult to see any of the supporting documentation for this.
Works for me just fine, but here's a direct link anyway -
http://www.brynosaurus.com/pub/net/p2pnat.pdf
And
Alex,
Actually, as I said in previous mail, it's the citation links that are
broken, not the link to the document itself.
To summarise the hole-punching aspect of things, it's basically the case
that msot NAT routers keep track of recent outbound UDP packets will allow
incoming traffic
If we're going to use something like that, why not use Kaboodle and the Get
Engaged service that you can use for free? While they don't offer the
source code for the server, they do make it available for the client. And
according to their documents, the KaboodleProxy isn't actually part of the
Alex:
How is your app better than Kaboodle and their KaboodleProxy? They make
the client source available and they even sell the proxy so you can run it
on your own machine(s), which in my book, makes it a bit more trustworthy
than having to trust someone else's machine. Granted the proxy is sold
http://www.kaboodle.org/KaboodleProxy.html says -
.. to find and connect with each other, by enabling
connections through an echoServer
which most likely means that they are relaying traffic through a
third node. This is so last century :) Hamachi is p2p and this
would probably
Ok. Interesting point about the third node... but I thought you needed a
proxy server for Hamachi as well, no?
In your first email to the list (that I have) you said:
Mediation server is NOT in the middle of the connection. All it
does is allows clients locate their peers and learn their
Khm .. I can't seem to find a description on how exactly GetEngaged
works, so I will tell how Hamachi operates and leave it to you to
compare it to Kaboodle.
Say we have two clients A and B, and the server S. First A talks to
S and S discovers A's location. Then B talks to S and S now knows
B's
Alex,
If the two ends of the connection are both behind NAT routers then, without
configuring those routers in some way, its fundamentally impossible to
connect from one to the other. So what is it that you are claiming your
mediation server does that makes this possible?
Wez @ RealVNC Ltd.
Alex,
So, in fact, there is a degree of configuration required at at least one end
(in order to allow the incoming connection through the NAT), and so this
whole setup could be replaced by a dynamic DNS name for the server... :)
Anyway guys, I think it's time this discussion moved elsewhere,
So on a side note,
I was one of the people that actually DID give Hamachi a try in my
company and I did get it to work. After configuring my firewall to
allow port 11975 and all upd ports on one test machine I got a
connection to my home computer with VNC!
There was one slight problem
James,
It is very much possible. See the paper Scott linked for the basic
idea behind it (the idea is BTW few years old already) -
http://www.brynosaurus.com/pub/net/p2pnat
Alex
James Weatherall wrote:
Alex,
If the two ends of the connection are both behind NAT routers then, without
James Weatherall wrote:
Alex,
So, in fact, there is a degree of configuration required at at least one end
(in order to allow the incoming connection through the NAT), and so this
whole setup could be replaced by a dynamic DNS name for the server... :)
Anyway guys, I think it's time this
14 matches
Mail list logo
