[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
howtos:network_services:tinc [2014/03/12 14:05 (UTC)] – spelling tonberryhowtos:network_services:tinc [2022/06/08 12:25 (UTC)] (current) – [Installation] pointed to SlackBuild tonberry
Line 17: Line 17:
  
 ===== Installation ===== ===== Installation =====
 +
 +=== Compile using SlackBuild ===
 +  * Tinc is now apparently maintained as [[https://slackbuilds.org/repository/15.0/network/tinc/|SlackBuild]].
 +
 +=== Compile from source ===
   * Download sources from http://www.tinc-vpn.org/download/   * Download sources from http://www.tinc-vpn.org/download/
  
Line 65: Line 70:
 #!/bin/sh #!/bin/sh
 ip addr add 192.168.1.1/24 dev vpnNIC ip addr add 192.168.1.1/24 dev vpnNIC
 +ip route add 192.168.1.0/24 dev vpnNIC
 ip link set vpnNIC up ip link set vpnNIC up
 +</file>
 +
 +  * Create tinc-down script that deconfigures VPN interface when VPN shuts down. Make the file executable too.
 +
 +<file - tinc-down>
 +#!/bin/sh
 +ip link set vpnNIC down
 +ip route del 192.168.1.0/24 dev vpnNIC
 +ip addr del 192.168.1.1/24 dev vpnNIC
 </file> </file>
  
Line 112: Line 127:
 There are a few differences in Windows configuration. There are a few differences in Windows configuration.
  
-  * You still generate initial configuration files, but place them in into where Tinc is installed, which should be something like C:\Program Files\tinc\<VPN name>+  * You still generate initial configuration files, but place them into where Tinc is installed, which should be something like C:\Program Files\tinc\<VPN name>
  
   * In tinc.conf, omit Interface directive, because Tinc daemon will then automatically select TUN/TAP device and directive may do more harm than good. Especially if Tinc service starts and fails immediately, check that Interface is not set.   * In tinc.conf, omit Interface directive, because Tinc daemon will then automatically select TUN/TAP device and directive may do more harm than good. Especially if Tinc service starts and fails immediately, check that Interface is not set.
Line 138: Line 153:
  
 ===== RC script ===== ===== RC script =====
-Here is some script to start all VPNs on boot. +Here is some script to start all VPNs on boot. Note that stop command differs between 1.0 and 1.1 (prerelease) branches; 1.0 calls tinc**d**, 1.1 calls tinc (no d).
  
 <code bash> <code bash>
 howtos:network_services:tinc ()