similar to: subnet-up/down scripts for Windows

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

On 6/12/18 11:45 am, Daniel Lo Nigro wrote: > I worked this out - I just had to manually add a route on the Windows > machines: > > route add 192.168.122.0 mask 255.255.255.0 10.123.1.4 > > (where 10.123.1.4 is the local IP on the Tinc interface) > I was hoping that Tinc would automatically configure the routing > tables, but configuring it manually is fine. Tinc will

Hi I have not tried systemd-coredump yet but I found something strange in my syslog file. Like this message in the en of the log file: tincd[10322]: segfault at 7fffb3180000 ip 00007ff7937f11c2 sp 00007fffb317dd68 error 4 in libc-2.23.so[7ff7936a3000+1c0000] There is more in the attached syslog file. Any clues? Best Regards, Håvard Rabbe > On 14 Feb 2019, at 02:27, Hamish Moffatt

I cannot even ping the LAN router on 192.168.1.1, but if I ssh though the tunnel to 192.168.1.3, I can ping it. Investigating with tcpdump withoug guidelines is beyond my skills I'm afraid. I used tinc in router mode because it is proposed like in most howto I found... Would just switching to switch mode makes things easier or that's not related? Le sam. 12 janv. 2019 à 05:17, Hamish

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On Wed, 7 Oct 2020, Hamish Moffatt wrote: > On 22/9/20 4:44 pm, Hamish Moffatt wrote: >> Is it possible to a configure a tinc (1.0.35) node to only send outbound >> through specific nodes, rather than trying to establish direct connections? >> >> I have a node which can connect to all the others directly, but some

Hi, attached is a patch that fixes that the NAME variable in subnet-up/down scripts for local subnets is not set. The reason for this was that there was a "hole" in the envp array in src/subnet.c:subnet_update(). If the subnet was local, envp[6] was NULL and the evaluation stoped there. Actually, the name string was leaking. This is easily fixed by changing the order in the array. I

Hi! I'm currently using Tinc to create a VPN between a Linux server, a Windows server, and my local laptop and desktop computers (both running Windows). I picked an IP in the 10.123.1.x range for each server, and added something like "Subnet = 10.123.1.1/32" to each host config file. It's working very well! What I'd like to do now is expose an extra subnet to the VPN. The

On 13/2/19 12:28 am, Tomasz Chmielewski wrote: > On 2019-02-12 22:12, Håvard Rabbe wrote: >> Hi >> Im running tinc 1.1pre17. My problem is that my tinc nodes >> occasionally crashes. When it crashes the tinc node is not running >> anymore. Time between failure can be sometimes days or weeks. >> >> Do anyone here have a proposal for how to debug and get this

On 7/10/20 2:45 pm, Erich Eckner wrote: > Hi, > > On Wed, 7 Oct 2020, Hamish Moffatt wrote: > > > On 22/9/20 4:44 pm, Hamish Moffatt wrote: > >> Is it possible to a configure a tinc (1.0.35) node to only send > outbound through specific nodes, rather than trying to establish > direct connections? > >> > >> I have a node which can connect to all

Is it possible to a configure a tinc (1.0.35) node to only send outbound through specific nodes, rather than trying to establish direct connections? I have a node which can connect to all the others directly, but some routes have terrible packet loss, so I'd like to configure it not to try. thansk Hamish

On 12/1/19 2:29 pm, Lars Kruse wrote: > Hello > > > Am Thu, 10 Jan 2019 11:58:33 +0100 > schrieb Julien dupont <marcelvierzon at gmail.com>: > >> The two tunnels are working. From a client I can ping or ssh VPN_office on >> both tunnel and LAN IPs 172.16.0.2 and 192.168.1.3. I cannot however ping >> any other computer on the LAN, I get no pong back but it

Hello, I'm confused by the subnet-up calls made by tinc. I was assuming that I'd be called once when it connects to another node. However, subnet-up appears to be called much more often than that. For example, I have the following configuration: ,---- | $ cat tinc.conf | ConnectTo = spitzer | Name = chronos | Mode = switch | | $ cat hbt/hosts/spitzer | address =

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

On Tue, Mar 21, 2017 at 06:51:37PM +0100, albi at life.de wrote: > We run tinc in router mode on over 10 server. > Some server announce the same subnet. > I can add routing with subnet-up and remove routing with subnet-down. But if I do this, my routing will be removed when > only one anncounce comes in, even there is an other server who still has the routing to the same network. >

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 [...] >

On Tue, May 05, 2015 at 01:18:15PM +0200, Alessandro Briosi wrote: > Now the odd thing is that when the VPN comes up they both also add the local > subnet to their routes on the tinc interface: [...] > the subnet-up script runs this command: > ip route add $SUBNET dev $INTERFACE metric $WEIGHT > > Should I filter it in the subnet-up script? I have other installations which >

Hi, Am Wed, 22 Mar 2017 07:51:23 +0100 schrieb Guus Sliepen <guus at tinc-vpn.org>: > [..] > 1. Use different weights for the otherwise identical Subnets, and ensure > you pass that along to the route up/down commands so the kernel can also > distinguish them. in linux the following command within "subnet-up" accomplishes that behaviour: ip route add

Hi, Guus I referre to the two separate tinc process/network(received same subnet), not Sunbet selection within one tinc process/network. My understanding is if different tinc process comes with exact subnet, as they are not related with each other(they have no idea regarding weights with each other), I guess the routing depends on the host's main routing table, for specific route it depends

Hi all, I'm experiencing a strange problem. I have setup 2 gateways which are behind a NAT router. They are configured in Route mode and have the ips 10.0.0.1/32 and 10.0.0.2/32 on the tinc interface The also have subnets (192.168.1.0/24 and 192.168.2.0/24 respectively). Now the odd thing is that when the VPN comes up they both also add the local subnet to their routes on the tinc

One of my hosts just rebooted for the first time in ages, and now it won't connect to any other nodes. The log just contains continual "error while decrypting metadata" errors. tincd[8324]: Error while decrypting: error:060A7094:digital envelope routines:EVP_EncryptUpdate:invalid operation tincd[8324]: Error while decrypting metadata from fairfield_gw (yy.yy.yy.yy port 655)