TCPOnly is required since 1.0.13?

[Guus Sliepen]

On Sun, Nov 28, 2010 at 10:06:11PM +0000, wildph at wildph.net wrote:

> I upgraded some of my Tinc nodes from 1.0.8 recently and found something
> strange.
> 
> All of a sudden, the vpn would not work as a full-mesh. Certain nodes
> were not contactable.
[...]
> With TCPonly = no, the vpn would only connect to ONE of the hubs, and
> traffic would not be routed to any other host on the vpn.
> 
> In order to get full mesh functionality back, I have had to set TCPonly
> to yes, on all nodes.

That is very strange. Setting TCPOnly to yes should actually disable the full
mesh functionality.  Can you run the VPN without TCPOnly = yes, and then run
tincd -n <netname> -kUSR2 on one of the nodes, and send us the resulting output
from the syslog, and repeat this with TCPOnly = yes?

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20101129/9df7d38c/attachment.pgp>