TCPOnly is required since 1.0.13?

[wildph at wildph.net]

Hi,

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.

I re-generated my rsa-keys, and checked my configuration.  My vpn uses
the following in tinc.conf, as I am routing both ipv4 and v6.

===
name = node1
mode = switch
AddressFamily = any
PMTU = 1280
PMTUDiscovery = yes
TCPonly = no
ConnectTo = hub1
ConnectTo = hub2
ConnectTo = hub3
===

My VPN has some hosts called by nodex.  These nodes are dynamic-ip, and
set to contact (connectTo) the hubs when they bring up their tincd.

The hubx nodes are fixed-ip, and are connected to each other in a full mesh.

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.


Hope this helps someone


Graeme