I use systemd or monitd scripts to check if the tinc vpn nodes are pingable
and simply restart the tinc daemon if they're not.
In my case I have i have a complicated dns setup where at tinc boot time
DNS is not yet resolving by the time tinc starts. A simple ping check on
the fqdn for the master nodes does the job.
On 17 Feb 2017 9:45 am, "Sandro Stiller" <sandro.stiller at
elfin.de> wrote:
On my system, tinc is started on bootup.
If the Network cable is not connected, tincd hangs forever after these
messages:
2017-02-13 11:34:01 tinc.XXX[403]: tincd 1.0.31 starting, debug level 5
2017-02-13 11:34:01 tinc.XXX[403]: /dev/net/tun is a Linux tun/tap device
(tun mode)
2017-02-13 11:34:01 tinc.XXX[403]: Executing script tinc-up
2017-02-13 11:34:02 tinc.XXX[403]: Listening on 0.0.0.0 port 655
2017-02-13 11:34:02 tinc.XXX[403]: Ready
2017-02-13 11:34:02 tinc.XXX[403]: Error looking up XXX.net port 2300:
Temporary failure in name resolution
2017-02-13 11:34:02 tinc.XXX[403]: Could not set up a meta connection to
XXXVPN
2017-02-13 11:34:02 tinc.XXX[403]: Trying to re-establish outgoing
connection in 5 seconds
2017-02-13 11:34:02 tinc.XXX[403]: Purging unreachable nodes
Even if I reconnect the interface, tinc does not continue.
If I restart the service manually, everything works fine, even with
disconnected network interface (it tries again and again until internet
connection works).
I think, there is some kind of boot-time race condition.
It's the same problem with version 1.0.28 and 1.0.31.
Do you have an idea how to find/solve the problem?
Thanks,
Sandro
_______________________________________________
tinc mailing list
tinc at tinc-vpn.org
https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20170217/67d1d55d/attachment.html>
