On Mon, Apr 16, 2018 at 09:10:02AM +1000, Hamish Moffatt wrote: > 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 [...] > Apr 16 06:54:43 dbtest3 tinc[3206]: tincd 1.1pre14 (Jun 5 2017 01:24:43) > starting, debug level 0 > Apr 16 06:54:43 dbtest3 tinc[3206]: /dev/net/tun is a Linux tun/tap device > (tun mode) > Apr 16 06:54:43 dbtest3 tinc[3206]: Error starting /usr/sbin/tincd > Apr 16 06:54:43 dbtest3 tinc[3206]: SIOCSIFADDR: No such device > Apr 16 06:54:43 dbtest3 tinc[3206]: rsvpn: ERROR while getting interface > flags: No such device > Apr 16 06:54:43 dbtest3 tinc[3206]: SIOCSIFNETMASK: No such device > Apr 16 06:54:43 dbtest3 tinc[3206]: SIOCADDRT: No such device > Apr 16 06:54:43 dbtest3 tinc[3206]: SIOCADDRT: No such device
That sounds like tinc's tun interface is not being configured correctly. Can you show us your tinc-up script? > The tinc.service file says that tinc should start after networking > (After=network.target). I wonder if After=network-online.target might be > better? As defined by > https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ > > I changed my local copy and tinc came up on boot successfully. Hm, tinc itself should handle the network not being online just fine. It will automatically retry after a while if it cannot make any outgoing connections. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: PGP signature
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
