similar to: How tinc route traffic when two subnets are identical?

On Thu, May 04, 2017 at 03:45:52PM +0800, Bright Zhao wrote: > 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

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

Hi, Lars Thanks for your suggestion, will give it a try later to see how it performs. But, yesterday, I did a below test: A ConnectTo B and C, B ConnectTo D, C ConnectTo D; All nodes turned "IndirectData" on in its host configuration, so the tunnel only follow metacomnection instead of direct connect. D announced default route by having the Subnet = 0.0.0.0/0 statement in its host

Sure, let me reply all here for my finding. @Lars @Guus A’s tinc.conf: Name = bright AddressFamily = ipv4 ConnectTo = aly_hk A’s tinc-up: #!/bin/sh ifconfig $INTERFACE 10.0.0.110 netmask 255.255.255.0 A’s host config: Subnet = 10.0.0.110/32 (VPN address) Subnet = 192.168.31.0/24 (LAN address) IndirectData = yes (enabled for every tinc nodes) The node aly_hk (vpn address 10.0.0.3) connects with

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?

Hello, Am Thu, 4 May 2017 15:45:52 +0800 schrieb Bright Zhao <startryst at gmail.com>: > [..] > > So I would like to know, the underlying mechanism for equal path of Subnet is > what? Tinc will test the latency, or something else to make the decision? tinc only _allows_ certain traffic to pass - it does no routing on its own. You will need to manipulate your routing setup

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

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, Tinc expert If there’re multiple tinc nodes announce default route in their host configuration of Subnet = 0.0.0.0/0, how for the remaining nodes to select which is the best route to get out? All of them participant in the same tinc net. I did some test, like A as the branch, B,C,D as the nodes to announce default route; when all up , A select B, but if B down, A will go C, C down, A will

Hi, Etienne In addition, is there any option or switch can turn of the automatic direct connection? For the example below, even A has the route to C and can establish UDP connection directly, but I need the traffic to go through B, how can I achieve that easily? (instead of remove something from A’s routing table, or manually block the connection between A and C) > On 1 May 2017, at 6:28 PM,

On Tue, Apr 10, 2018 at 03:36:08PM +0200, Hans de Groot wrote: > hosta  <--> hostb  <-->  hostc > > Hosta and hostc are not directly connected via tinc. But both are conncted > via hostb (I called my network tincnet). This works fine I can ssh from > hosta to hostc and vice versa without any problems. > > hostc is in a whitelisted iprange at some service

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

yes, I have these in C host file: Subnet=10.10.0.0/24 Subnet=0.0.0.0/1 Subnet=128.0.0.0/1 ## not metioned, because I think is maybe works in same as 0.0.0.0/1 B host file doesn't have 0.0.0.0/1 and 128.0.0.0/1 I only added one route to 5.6.7.8 via B, not via C On Mon, Feb 29, 2016 at 4:40 PM, Maxim Vorontsov <6012030 at gmail.com> wrote: > hi. > > Are you add only

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”

Hi, Etienne I took a look for the below host configuration parameter (IndirectData), the default is no. For the below example: A ConnectTo B, B ConnectTo C: If IndirectData = no (default), then A wouldn’t establish direct connection with C, but will be forwarded by B. If IndirectData = yes, then A will try to establish direct connection with C, even though A don’t have the statement of

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

There is no concept of "client" or "server" in tinc. tinc is purely peer-to-peer. "ConnectTo" statements only indicate which node will attempt to establish the initial connection, but once the connection is established, direction does not matter. It is unclear from your message which node is responsible for which subnet. If X/32 truly belongs to C, then simply set

Hi, Tinc experts Diagram as below, A is trying to access host X behind C: A >> B >> C — “host X" B is the tinc server for A, but also B is the tinc client to connect to C. My question is, if I only use one VPN (/etc/tinc/myvpn), then the host configuration for B will be tricky. As the tinc server to A, B’s host config (/etc/tinc/myvpn/hosts/B) needs have the Subnet = X/32,

Hi, Guus I did some test regarding the points you mentioned below, and yes, you’re right, but some of points may need further adjusted: 1. The destination of IPv4 wouldn’t be changed, Yes I agree, that’s the goal and final destination for the communication. But during the path, it may be encapsulated into another packet(tunnel mode), where the outside IP header is the physical address, but the

my network: local pc(192.168.1.2)-->openwrt_adsl_router A( 192.168.1.1/24&11.22.33.44pppoe&10.10.10.1/24 tinc)<---remote B: 10.10.20.1/24 ^ | remote C:10.10.0.1/24 all running tinc 1.0.x, ADSL router