On Sat, Mar 30, 2013 at 08:21:32PM +0100, Rene Bartsch wrote: > I've set up Tinc in switch-mode on the three nodes "gw", "rb493g" and > "v900w", but the nodes "rb493g" and "w900v" do not connect to each > other. [...] > Common entries in all three tinc.confs: [...] > IndirectData = yes
If you enable IndirectData, rb493g and v900w will never make a direct
connection to each other. Set this option to no.
> I can ping each node from each other node, but the DOT-graph shows no
> direct connection between "rb493g" and "w900v" causing superflous
> traffic and latency on the uplink of the node "gw"
The graph only shows the meta connections (ie, those manually specified with
ConnectTo), not the data connection. With tinc 1.0 it is hard to see if a
direct connection is made. You can try to install tinc 1.1pre6 (it is backwards
compatible with 1.0.x), and then, from rb493g for example, run the command
"tincctl info v900w". This should tell you if a direct connection is made or
not. Also note that tinc makes direct connections on demand, so first you need
to ping the other node before you will get a useful answer.
You can also run tcpdump on your external interface to check whether traffic
really goes directly to the other node or whether it is sent via gw.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
