similar to: add Subnet dynamicly

If your question is "can I assign the same subnet to multiple tinc nodes on the same network", the answer is yes (for both 1.0 and 1.1). That can indeed be used for seamless failover. That said, when sending packets to a subnet assigned to multiple nodes, it is not very well-defined which node tinc will send the packets to - currently it tries to estimate which one is closest by

On 8.2.19. 22:39, albi wrote: >>> The setup looks like this: >>> web <- tinc "tiosp" -> gateway <- tinc "tiutl" -> backup > Which lan ips do all your computers have? network addess will be fine. > > > ALBI... Hi Albi, web:   tinc tiosp: 172.16.1.10   local: 10.0.0.5 gateway:   tinc tiutl: 172.16.0.5   tinc tiosp: 172.16.1.5   local:

> If your question is "can I assign the same subnet to multiple tinc > nodes on the same network", the answer is yes (for both 1.0 and 1.1). Yes exactly. > currently it tries to estimate which one is closest by measuring the > time it took to establish metaconnections along the edges to the node, Shure? I remember alphabetic order (host name) in tinc 1.0. Is it the same

Hi, is it possible to run two tinc hosts to make failover in case of crash of one tinc host? Or should I switch to tinc 1.1? ALBI...

> I'm using something similar to Amazon's VPCs, where a logical group of > instances has a local subnet from the cloud provider. This local subnet > is always 10.0.0.0/24. As there are multiple VPC's, these private local > subnets dont collide. I do not know what Amazon does, and it looks like I do not want to know it :-) Am I correct? web, gateway and backup have NO

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

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. Is it possible to run subnet-down only it the last announce to a subnet is going down?

On 6 April 2015 at 23:03, <albi at life.de> wrote: >> currently it tries to estimate which one is closest by measuring the >> time it took to establish metaconnections along the edges to the node, > > Shure? I remember alphabetic order (host name) in tinc 1.0. Actually, yes you're right, my bad, I was confused between edge_t::weight and subnet_t::weight while looking

>> The setup looks like this: >> web <- tinc "tiosp" -> gateway <- tinc "tiutl" -> backup Which lan ips do all your computers have? network addess will be fine. ALBI...

On 11/15/2015 02:28 PM, Armin Schindler wrote: > 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

Dear list, I'm currently trying to simulate a VPN in a very simple configuration at home. My normal home-net 192.168.0.0/24 serves as "the internet". Three test machines are used, two of them connected to "the internet": odin , external IP 192.168.0.100/24 on eth0 thor , external IP 192.168.0.101/24 on eth0 My VPN uses address space 10.0.0.0/8 in the following way: odin

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

Running a DHCP server over a tinc VPN operating in router mode is a very weird setup. In theory one *might* be able to make it work, but since every node needs to be statically configured with tinc routing information anyway ("Subnet" configuration), that doesn't sound very useful to me. On 30 August 2016 at 11:56, <albi at life.de> wrote: > > If you're using a TAP

Hello, How does tincd determine the subnet(s) of other remote nodes? Does tincd read its copies of the hosts file and parse and follow the subnet information contained in the local files? Or does tincd solely trust the subnet information dynamically advertised by each remote node? In my experimentation, it seems that: a) tincd reads its own subnet(s) from its copy of its own host file, but

Hi, I need to re-open the thread blow. The situation is still the same. The HUP signal does not trigger reloading of subnet declarations in own hosts file (Version 1.0.35). After a quick view to the source code, file src/net.c shows in line 658 would reload subnets when using StrictSubnets only. But why? With StrictSubnets it doesn't make sense to me. I did a quick check and removed the if

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Analyzing a routing problem in a tinc net I found, that a declaration of a class-A subnet (x.0.0.0/8) in a host configuration file is ignored, e.g. Subnet = x.0.0.0/8 Looking at the subnet lists produced with kill -USR2 does not show this subnet in the log (but all others, that are configured in the same file). Splitting the subnet in two /9

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 06.02.2015 um 21:36 schrieb Guus Sliepen: > On Fri, Feb 06, 2015 at 09:01:21PM +0100, Flynn Marquardt wrote: > >> Analyzing a routing problem in a tinc net I found, that a declaration of >> a class-A subnet (x.0.0.0/8) in a host configuration file is ignored, e.g. >> >> Subnet = x.0.0.0/8 > [...] >> Splitting

> If you're using a TAP interface (i.e. layer 2, Ethernet) combined with router mode (an unusual setup, at least on > Linux), Thanks, DeviceType = tap does the job. > operating at layer 3, therefore tinc will strip any layer 2 header (including the MAC address) before sending the packet > across the VPN. As a result, changing the MAC address of the virtual interface will have