On Tue, Feb 17, 2009 at 01:30:56PM -0200, Christian Lyra wrote: > I´m also surprised to learn that the tinc ping/meta data stuff was done > by tcp. This explains why I saw a established tcp connection from nated > host to public server, and a unreplied udp connection from public > server to nated host. I was expecting that everything should be done > with either tcp or udp and not both. Changing the control to a protocol > only is possible?
You can use the TCPOnly option to make all traffic go via TCP. Although it
would in theory be possible to tunnel everything via UDP, the problem is that
tinc needs a reliable, in-order transport layer for its communication with
other daemons, and I don't want to reimplement TCP on top of UDP.
The latest version of tinc in the git repository has code to detect whether
communication via UDP is possible, if not it will use TCP exclusively.
--
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
