similar to: What if two tinc daemons received the same Subnet but with different weight?

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, Reason behind that is we have some use cases wouldn’t like to make some nodes to become the transit node, but there’re some other nodes in the topology act as the transit nodes. So if the tinc node forward subnet update it learning from one side to the other side, then it possible to become transit node if one side only have route to go through it. That node I would call it “spoke-only”

On Sat, Aug 19, 2017 at 09:21:11AM +0800, Bright Zhao wrote: > Two tinc networks/daemons, and received same subnet from the two daemons, how tinc will choose which one is preferred? And the weight settings in each daemon for subnet will or will not be the judge? If you use weights for Subnets, then the Subnet with the lowest weight will be chosen, unless the node that owns that Subnet is

On Wed, Nov 18, 2015 at 08:25:28AM +0100, Armin Schindler wrote: > But I have a question regarding "Subnet=" possibilities. When I have more than > one Server acting as host for VMs and need to have automatic routing to > all VMs on these servers, can I use tinc to create this routing automatically? > > My idea is to have a script which is started when a VM is

Hello, I have two servers (A and B) in separate locations. Both are connected together via two tinc switches to provide two subnets on both servers. This works pretty good. I can start my VMs on any server connected to one of those bridges without changing any routes. The subnets hosted on both servers (each in a bridge) are 172.16.10.0/24 (mainly on A) and 172.16.11.0/24 (mainly on B) Now I

Hi, The man page, in the part about "Subnet" directives, does not specifiy what happens when two nodes announce the same Subnet with the same weight. Is one of the two nodes chosen arbitrarily? If so, how? My use-case is to announce a default route from two different nodes of the same Tinc network. I would like to have some sort of load-balancing between the gateways, but a simple

Hello, I want to use a tinc node as a default gateway in router mode. My first attempt was to just add an extra, lower priority subnet for the host that should act as the gateway: Subnet = 192.168.12.2/32 Subnet = 0.0.0.0/0#20 but this doesn't seem to work: # route add 173.255.235.238 gw 192.168.12.2 # ping 173.255.235.238 results in the local tinc process complaining that Read packet

Hi, All Two remote tinc nodes(A, B) advertised the same route to the Tinc domain, and the local tinc node(C) has two ConnectTo to point to those two remote nodes, and I found, and let’s assume connection from C to A is better than C to B (better latency from ping) : 1. when two remote nodes are up, the traffic always send through A 2. when A is down, traffic send through B 3. when A recovered,

Hi, I have two tinc nodes which announce default gate to internet. How does tinc select which node is prefered when I route to the tinc device and not a special ip? tinc 1.0.16 ALBI...

On Thu, May 4, 2017, at 09:04, Guus Sliepen wrote: > It is currently unspecified what tinc will do when you have two nodes > with exactly the same Subnet. The only guarantee currently is that > traffic goes to one of the nodes that is online. > > The implementation currently has the effect that, from the set of nodes > that is online, tinc will choose the one that has the lowest

Multiple questions here, thinking one email is less annoying (sorry if not). Running tinc 1.0.31 1. Could anyone give an explanation (or point to documentation) of the differences between Connections, Nodes, and Edges in the USR1/2 logging, and the various information in there? 2. Connections appears to match the list of ConnectTo hosts in the main config file -- does this mean this node can

Hi, I'm trying to setup tinc tunnel between my work and home linux machines as shown here http://cl.ly/image/1H1R2X2D403X I am able to setup tinc session between A and B and I can ping them. But I can't ping C or D from B, or A respectively. Home network 192.168.1.0 Work network 10.20.50.0 tinc tunnel is 15.0.0.x. Do I need to run tinc on C and D as well? Or Do i need to manually

Hi, Just for your information I had the tinc daemon dying on the main machine I use as a hub, so I looked for a script to restart the daemon it if dies. Here is tinc.sh: ========================================================== #!/bin/bash # Tinc Process Monitor # Restart Tinc daemon When It Goes Down # Source: http://bash.cyberciti.biz/web-server/restart-apache2-httpd-shell-script/

Hello folks, I have the following problem: tincd is complaining about a missing name or so but i cannot find any mistake in the configuration. It is similar to all my other tinc nodes. here are the details: # ls -l /etc/tinc/ffnw/ drwxr-xr-x 3 root root 4096 Aug 1 10:43 hosts -rw------- 1 root root 1680 Jul 31 21:54 rsa_key.priv -rw------- 1 root root

Hi, tinc experts abc to def at x.x.x.x port 655 options d weight 540 How’s the 540 weight been calculated? What does it mean? How can I leverage this weight? The d of after options mean direct?

Hi, I have some questions about running multiple tinc deamons. The docs say you can do it to support separate VPNs, but I don't see any examples. I have been running a single tinc vpn for months with no problems, now I'm trying to add a second separate vpn. I'm running the static tinc version 1.0pre7 (built Apr 9 2002 14:00:34, protocol 14) on Debian potato. I did not want to go

Thank you, that is very helpful. And actually I do have a few further questions regarding this: 1. This weight is not the one specified in Subnet, this should be something related to the host, where can I manually configure this? 2. The weight value is ONLY take round trip latency as the measurement, or including CPU power and other factors into consideration? 3. I don't know how this

Hi Guus Thanks for clarifying. Some follow up questions: - How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to upgrade to? - What is the workaround until we patch with this fix? Using a combination of AutoConnect and ConnectTo? - When we use ConnectTo, is it mandatory to have a cert file in the hosts/* dir with an IP to ConnectTo ? -nirmal On Tue, Aug 22, 2017 at 12:10

I've been trying out IPv6 networking with tinc and noticed that it will not route smaller segments than /48 If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get network unreachable However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine Is this is a limitation in tinc or the kernel network stack itself? -------------- next part -------------- An HTML

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