search for: myvpndomain

I have a bunch of Debian stretch machines with systemd where I find that tinc starts too early during boot, and fails to work. Typically it is running, but printing out Apr 14 00:53:41 db7 tinc[3077]: Can't write to Linux tun/tap device (tun mode) /dev/net/tun: Input/output error regularly. Unfortunately because it is running systemd does not restart it, even though it's not actually

Currently I have the local tinc node's VPN IP in both the tinc-up script as well as in its hosts/$NODE file Subnet setting. Can this be avoided, to simplify deployment? Actually I am currently using a DNS lookup in the tinc-up script to get the local VPN IP ($NODE.myvpndomain), but this fails if DNS isn't ready when tinc-up is run. (DeviceStandby=yes fixes this, but then the subnet-up script is run before tinc-up). I notice that tinc runs the subnet-up script for the local subnet immediately after the tinc-up script, with $REMOTEADDRESS empty, so I tried puttin...