search for: levenlabs

...the following the example https://www.tinc-vpn.org/examples/proxy-arp/, it seems to have: Subnet = 192.168.1.0/24 for the office, yet the IP address for the office is 192.168.1.2. Is that example no longer valid or am I misunderstanding? On Tue, Feb 14, 2017 at 4:01 PM, James Hartig <james at levenlabs.com> wrote: > On Tue, Feb 14, 2017 at 3:43 PM, Etienne Dechamps <etienne at edechamps.fr> > wrote: > > Hang on a second. I've just re-read your original message and I > > believe you are confused about what the "Subnet" option does. Again, > > it deal...

...rd phenomena you're reporting. If you make sure to use different IP subnets for VPN addresses and physical addresses, your problems should go away. On 14 February 2017 at 20:36, Etienne Dechamps <etienne at edechamps.fr> wrote: > On 14 February 2017 at 18:59, James Hartig <james at levenlabs.com> wrote: >> When you say "and to the local network" what IP does it try to send to >> on the local network? The subnet address? > > No. The Subnet option deals with routing *inside* the VPN, not the > underlying "real" network. > > In tinc 1.1, t...

...that address should be sent to the virtual network interface managed by tinc (instead of the physical network), which will then use its own internal routing systems (configured by the Subnet options) to send the packet to "roadwarrior". On 11 May 2017 at 04:40, James Hartig <james at levenlabs.com> wrote: > @Etienne, I understood your explanation about the Subnet being the network > *inside* the VPN, but the following the example https://www.tinc-vpn.org/ > examples/proxy-arp/, it seems to have: > Subnet = 192.168.1.0/24 > for the office, yet the IP address for the off...

On Tue, Feb 14, 2017 at 1:46 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Tue, Feb 14, 2017 at 11:21:34AM -0500, James Hartig wrote: > >> Those 2 boxes are in the same subnet and have addresses of 10.240.0.4 and >> 10.240.0.5, respectively, on their eth0 interface. Port 655 on tcp and udp >> is open to the world. The tinc_test_2 box has a ConnectTo of

On 14 February 2017 at 18:59, James Hartig <james at levenlabs.com> wrote: > When you say "and to the local network" what IP does it try to send to > on the local network? The subnet address? No. The Subnet option deals with routing *inside* the VPN, not the underlying "real" network. In tinc 1.1, the address that local discovery...

...Are they simply forwarded by some other router somewhere? Or are they configured on some other network interface on the machine? If you're using tinc 1.1, please provide the output of "tinc dump edges" while your network is up. On 14 February 2017 at 16:21, James Hartig <james at levenlabs.com> wrote: > We are testing tinc inside Google Compute within a single region and an > external region. Two boxes are created as follows: > /etc/tinc/test/tinc_test_1 > Subnet = 10.240.0.0/16 > Subnet = 10.240.0.4/32 > Address = 104.154.59.151 > > /etc/tinc/test/tinc_te...

...104.154.59.151 port 655 local 10.240.0.5 port 655 options 700000c weight 1 I brought down tinc_test_2 and brought it back up and the output from "tinc dump edges" didn't seem to be any different while it was flip flopping. > On 14 February 2017 at 16:21, James Hartig <james at levenlabs.com> wrote: >> >> We are testing tinc inside Google Compute within a single region and an external region. Two boxes are created as follows: >> /etc/tinc/test/tinc_test_1 >> Subnet = 10.240.0.0/16 >> Subnet = 10.240.0.4/32 >> Address = 104.154.59.151 >>...

...are currently using openvpn for this but we want something that is mesh so we can handle something like the openvpn master server going down. > On 14 February 2017 at 20:36, Etienne Dechamps <etienne at edechamps.fr> wrote: >> On 14 February 2017 at 18:59, James Hartig <james at levenlabs.com> wrote: >>> When you say "and to the local network" what IP does it try to send to >>> on the local network? The subnet address? >> >> No. The Subnet option deals with routing *inside* the VPN, not the >> underlying "real" network. >...

We are testing tinc inside Google Compute within a single region and an external region. Two boxes are created as follows: /etc/tinc/test/tinc_test_1 Subnet = 10.240.0.0/16 Subnet = 10.240.0.4/32 Address = 104.154.59.151 /etc/tinc/test/tinc_test_2 Subnet = 10.240.0.0/16 Subnet = 10.240.0.5/32 Address = 104.197.132.141 /etc/tinc/test/tinc.conf Name = $HOST AddressFamily = ipv4 Interface = tun0