On Sun, Aug 19, 2012 at 04:42:24PM +0400, SVM wrote: > I have one node behind two masq. NATs and it works just few minutes > after initial start of tinc daemon. A few minutes after UDP traffic > to this node from the node it has connected to cannot travers double > NAT, and I understand this.
Hm, that is strange, once a connection has been made through NAT it should keep
working, unless the connection timeouts on the NAT device are set very small.
You could try setting "PingInterval = 30" in tinc.conf to have tinc send ping
packets more often.
> 1. But, if I use TCPOnly=yes option, which is deprecated as I've
> read, - it works fine, with non directed traffic, which flows via
> third node.
> If I leave TCPOnly=no(default) tinc cannot determine itself to use
> tcp instead of udp in my case as it described in documentation.
Tinc should determine it itself. If it does not, that is a bug. It can take a
minute though for tinc to detect that UDP has failed to work. Does it still not
work for you after more than a minute?
> 2. As I know from doc, by default tinc uses two connections:
> meta-connection(tcp) and data-connection(udp).
> But if I turn TCPOnly=yes? Will Meta and Data flow in one
> tcp-session or also in two different?
They will be in one TCP session.
--
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
