similar to: Help linking subnets

Hi, Thank you Guus, I think the /16 solution is the easier to apply so I modified my tinc-up in host A to be like #!/bin/sh ifconfig $INTERFACE 192.168.10.1 netmask 255.255.0.0 a route -a from HOST A shows: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 178.62.128.1 0.0.0.0 UG 0 0 0 eth0 10.129.0.0

>> I have tinc up and running on a kvm/libvirt host. libvirt creates a >> bridge and assigns ip to this bridge, for instance 192.168.1.1. All >> guests have an ip within 192.168.1.0/24. I want to access the guests >> in this libvirt network with tinc from the internet via the host. >[...] >> and tinc.conf like this >[...] >> Interface = tun0 >>

>> Sorry, I don't get it. I thought the Subnet parameter is indented for >> routing local nets to the remote host. >> This way a remote host can access the provided local nets. >> >> What I have is my host A with vms (ips within 192.168.1.0/24). >> My host A has a bridge to the vm's network. The bridge has the IP >> 192.168.1.1. Furthor more

>> >> Nice hint, but it's not this simple. Libvirt complains about the >> network not the interface. The interfaces have different names already. >> It seems like tinc bind the subnet on startup and libvirt doesn't >> like it > Well, if it's about the subnet, then it's up to you to change the > Subnets in the host config files (and change

Hi, Does anyone here have experience running Tinc on NixOS? I'm trying to run Tinc on a NixOS machine, using the similar configuration i had for Ubuntu. My home subnet is 192.168.1.0/24 and my work is 10.16.0.0/24. However, unlike ubuntu, when I start tincd on nixos, and try to 'ifconfig $INTERFACE 192.168.1.10 netmask 255.255.255.0' in my tinc-up, I loose network access on the box

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

Lastest Modifications: HOST A: Removed 2 route add as you suggested, and it's still working. HOST B: This host has a openwrt as gateway and I added few days ago as you suggested on freenode and this is HOST B Gateway route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0

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

Hi, I am running OpenVPN where i have one central hub VPN server, and multiple spoke VPN clients. I can ping from each client to the server and each client to computers on the subnet which the server resides (192.168.2.0/24) so it works ok there. I cannot however, ping from one client to another client. I guess the packet path would go: clienta -> vpn -> shorewall/router -> vpn ->

I have now got the tinc demons (on network OFFICES) on BranchB and BranchA talking to each other, and I have been able to access services (like AFP, Apple file sharing) between the two hosts (in both directions), but not beyond the local network connected to BanchA. I am unclear which routing can be provided by tinc and which routing would I have to add manually. The aim is: BranchB is a

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

I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024 fe80::/64 dev eth0 proto kernel metric 256 $ ping6 fd80:2015:2105:abcd::1 PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes 64 bytes from fd80:2015:2105:abcd::1:

Hi, I am trying to access devices (ip cams) through clients using the tinc vpn. Let's demonstrate the problem with two clients: client name [ip in eth0] [ip in tun0] gl752 (A) 192.168.1.33 10.0.0.1 xps13 (B) 192.168.1.55 10.0.0.2 I also have an ip camera connected to the local network at 192.168.1.21. I want to try a situation where I am accessing, from linux box

Hi Ok I have a simple lab setup with three nodes , one acting as the "Central Node" and the other two as remote nodes which "*ConnectTo*" the central node in order to be able to communicate with each other. What I would like to know is , once the tinc remote nodes establish a connection to the "Central Node" , my understanding was that if the remote nodes want to

Hi, First sorry for my bad English. I made a vpn wtih tinc for link my home and my two office. In Addition I want to configure my android device to link with my vpn. The topology of the net is this: cubox(a linux machine in my home with vpn address 192.168.0.20) groppalbero (a linux machine in my second office with vpn address 192.168.0.40) imac(a mac machine in my first office with vpn address

Yes. The problem is lollipop. I tried to install tinc on my brother's device which mount a cyano 10.1( android 4.2.2) and it works. I don't understand which is the problem with lollipop. Is there a firewall that block the packets? Andrea Squeri If you are running Lollipop / Android 5.x on your Nexus 5, then you are probably seeing the same issue I was with it. lollipop seems to change

Hello, I have been reading through the documentation and trying to set up a very small VPN as a test for a larger rollout that I would like to complete in the future but cannot get this working. The configuration seems like it should be relatively simple, so I'm most likely missing something basic but I just cannot see what I'm doing wrong. At the moment I am trying to get this working

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

I don't know.. It seems that anyone had try to made work tinc with lollipop. Even googoling i don't found anything about this argoument. Andrea Squeri Il 27/mar/2015 06:55 "Tatsuyuki Ishi" <ishitatsuyuki at gmail.com> ha scritto: > SELinux is considered as the biggest problem. > > On Thu, Mar 26, 2015, 22:37 Andrea Squeri <andrea.squeri at gmail.com>