3 tinc nodes (2 behind nat and 1 with a public ip).

[deep_eye]

I have a similar constellation. 1 Master-Node and many "satellites" behind nat-routers.
The master-node have a public ip (with dyndns).
On all routers are "port-forward" enabled (every node has a unique port, so it's possible to have 2 nodes behind one nat-router).
We use the port-forward to have direct connections between the tinc-nodes. The node-addresses comes from the master (he is always reachable).

hosts-file master:
Address = <dyndns-name>
Port = 12345
Compression = 0
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----

hosts-file satellite:
Port = 12346  (every new node, has a higher number: 12347, 12348)
Compression = 0
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----

tinc.conf - satellite:
Name = <client-name>
Interface = <interface>
Mode = switch
MaxTimeout = 10
PingInterval = 120
ConnectTo = <dyndnsname of master-node>
ConnectTo = <satellite1>
ConnectTo = <satellite2>
...


Guus Sliepen schrieb:
> On Tue, Nov 30, 2010 at 10:09:51PM +0100, Perry Couprie wrote:
> 
>> I have 3 tinc nodes.
>> 2 nodes, A and B are behind a nat router.
> [...]
>> node A en B connect to node C.
>> But node A en B don't connect to each other.
>> What do i have to change to connect node A en B directly to each other.
> 
> With the latest version of tinc, you should not have to do anything. It should
> automatically detect if a direct connection between A and B is possible.
> However, it depends on the NAT routers if this is possible or not.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc