Dear mailing list, How do I make Tinc auto start on Debian 8 Jessie? I’ve compiled and installed the latest stable release tinc-1.0.33 and I’ve tried this: nano /usr/local/etc/tinc/nets.boot Added the netname of my vpn sudo service tinc start Should work according to: https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04 <https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04> But it doesn’t run on a reboot. Also tried: systemctl enable tinc systemctl enable tinc at vpnname But I run into errors https://wiki.archlinux.org/index.php/Tinc#Automatically_Starting_Tinc_at_boot <https://wiki.archlinux.org/index.php/Tinc#Automatically_Starting_Tinc_at_boot> What’s the official recommended way to run Tinc at startup on Debian? Can’t find anything mentioned about this in the documentation. Thanks in advance. Best regards, Jip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180106/f6ced0f9/attachment.html>
On Sat, Jan 06, 2018 at 05:14:47PM +0100, Jip de Beer wrote:> How do I make Tinc auto start on Debian 8 Jessie?Jessie uses systemd by default, so normally you'd have to tell systemd to start tinc automatically. The tinc package that comes with Debian provides the systemd service files necessary, however:> I’ve compiled and installed the latest stable release tinc-1.0.33 and I’ve tried this: > > nano /usr/local/etc/tinc/nets.bootThere are two problems here: the systemd service files don't read nets.boot, and if you installed tinc in /usr/local, then the systemd service files that come with tinc (both from the official Debian package and the 1.0.33 tarball) assume that the tincd binary is installed in /usr/sbin/.> Should work according to: > https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04 <https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04>Ubuntu 14.04 is much older than Debian jessie, and doesn't use systemd, so the instructions about nets.boot are not appropriate for your system.> Also tried: > > systemctl enable tinc > systemctl enable tinc at vpnnameThat's the correct way. However, you may have to edit the file /lib/systemd/system/tinc at .service, and change /usr/sbin/tincd to /usr/local/sbin/tincd.> What’s the official recommended way to run Tinc at startup on Debian? > Can’t find anything mentioned about this in the documentation.You're right, I'll add a section about it in the manual. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180106/0cdf0152/attachment.sig>
Dear Guus, Thanks for the reply. I still run into some issues. Because the repositories host an older release (1.0.24-2.1+b1) of Tinc, I decided to build and install the Tinc 1.0.33 release. On a fresh install of Debian 8 I’ve done the following: cd /tmp/ wget http://tinc-vpn.org/packages/tinc-1.0.33.tar.gz tar xvzf tinc-1.0.33.tar.gz apt-get install libssl-dev zlib1g-dev liblzo2-dev build-essential automake autoconf gettext texinfo cd tinc-1.0.33 ./configure && make && make install mkdir -p /usr/local/var/run/ No problems with building and Tinc works. As you can see I didn’t choose any directory to install Tinc into (/usr/local vs /usr/sbin/). That just happend by default. So I’d expect that the contents of files like tinc at .service, which are supposed to be part if the installation, also follow the default installation paths. I tried to change /usr/sbin/tincd to /usr/local/sbin/tincd inside /lib/systemd/system/tinc at .service like you say but there’s nothing there. I’m still unable to launch Tinc on system startup. Could you help me out? Including these instructions in the manual would be a great addition :) Best regards, Jip
On Mon, Jan 8, 2018 at 9:12 PM, Jip de Beer <jip.de.beer at gmail.com> wrote:> Dear Guus, > > Thanks for the reply. > I still run into some issues. > Because the repositories host an older release (1.0.24-2.1+b1) of Tinc, I decided to build and install the Tinc 1.0.33 release. > > On a fresh install of Debian 8 I’ve done the following: > > cd /tmp/ > wget http://tinc-vpn.org/packages/tinc-1.0.33.tar.gz > tar xvzf tinc-1.0.33.tar.gz > > apt-get install libssl-dev zlib1g-dev liblzo2-dev build-essential automake autoconf gettext texinfo > > cd tinc-1.0.33 > ./configure && make && make install > > mkdir -p /usr/local/var/run/ > > No problems with building and Tinc works. > As you can see I didn’t choose any directory to install Tinc into (/usr/local vs /usr/sbin/). > That just happend by default. > So I’d expect that the contents of files like tinc at .service, which are supposed to be part if the installation, also follow the default installation paths. > > I tried to change /usr/sbin/tincd to /usr/local/sbin/tincd inside /lib/systemd/system/tinc at .service like you say but there’s nothing there. > I’m still unable to launch Tinc on system startup. > Could you help me out? > > Including these instructions in the manual would be a great addition :) > > Best regards, > JipDebian support tinc config in /etc/network/interfaces, just add following line in your interface file. auto tincvpn iface tincvpn inet static address x.x.x.x netmask 255.255.255.0 tinc-net do tinc-debug 1 tinc-user nobody tinc-pidfile /tmp/tinc.pid tinc-logfile /tmp/tinc.log for more detailed information, please reference to /usr/share/doc/tinc/README.Debian -- Liang Guo http://guoliang.me/