A relatively recent update (1-2 months) has introduced a fairly major
issue where connection issues seem to cause tinc to decide that there's
another node of the same name on the VPN, leading to it quitting.

It seems that it's detecting itself somehow, through an older
connection, perhaps? The daemon stopping itself is a major problem,
though, as it has to be manually restarted.

I would report this on the bug tracker, but I'm unable to find a link to
one on the website.
_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc

Reply via email to