similar to: tinc Digest, Vol 123, Issue 11

Hi, after trying for days I ended up with a working tinc configurazion of 2 subnets, now my goal is to add 2 more subnets and comunicate. I might seem dumb at this point but honestly I don't work in IT or Networking stuff, and so I dont have that deep knowledge. A little explanation of my configuration is HOST A (VPN server) Public IP: 1.2.3.4 tun0 Subnet = 192.168.10.0/24 tun0 IP =

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

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

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

Hi all :) I have a masqueraded home lan as well as a friend of mine. I have set up two tinc daemons on both masquerading gateways and I have no trouble connecting (it works pretty smooth) and they show up in the syslog as configured after sending an USR1 / USR2 signal to the daemons. The trouble is the routing / firewalling of the packets. Maybe somebody could give me a hand here? :) The

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

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

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

On Sat, 5 Mar 2016, shad0wrunner at gmx.de wrote: > 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 >

Hello! I'm trying to make a wireless mesh network with b.a.t.m.a.n. protocol, and I would like to secure the wireless links with tinc. My test network is 2 wireless routers with OpenWRT Kamikaze firmware, and the network topology is the following: |CLIENT|eth0: 192.168.180| <--> |eth0: 192.168.1.1|MESH-NODE|ath0: 192.168.5.54| <~~> |ath0: 192.168.5.51|GW|eth1: 192.168.1.51|

Guus, Thank you for your help (a)>>You said:- First, if you are already using "ip" to assign an address..... Why should I use "ip route" instead of "route add..." Surely both write same to the Routing table? (b) My problem was, that Tinc servers could not ping remote clients, whereas clients could ping successfully across VPNWhen pinging Client to Client

Thank you, Parke and Guus. I have now understood and got it working. Because of my beginner belief, I assumed that the tinc vpn end points needed to be on the same network. I have now discovered that the tinc vpn IP end points addresses can be arbitrary, and different! So I have set the end points to be local to the LAN they connect, and added on each tinc server a dev route to ensure

Hello,I have 6 Ubuntu 18.04 machines in a Tinc (1.35) network, where 3 are in Spain and 3 in UK.One machine in each country is running Tinc, and as both ends are behind NAT, they both connect outward to an Upcloud VM. The 4 non-tinc machines can Ping and SSH each other without issue, and so from that point of view, the Tinc VPN is working fine.However, the 2 tinc machines can only ping and ssh

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

El 12 de febrero de 2016 16:51:59 CET, Eric Yau <ericyaukhy at hotmail.com> escribi?: >Hi All, > > > >I am trying to setup the site-to-site VPN with TINC for connect my home >network to company network. Here is the IP allocation and configuration >for >your reference. > > > >Home PC (192.168.1.2) ?-----? Home (OPENWRT Router, 192.168.1.1, >10.0.0.1)

Hello! I've setup tinc almost succesfully, but there is one problem remaining with a routing issue. Short Description of the situation : Workstation A (192.168.1.3) | | Tinc Host "50K" (192.168.1.1) | | <Unknown Firewall> + + + <Masq Firewall (Linux)> and Tinc Host "oeoe" (192.168.2.1) | | Workstation B

I'm having a bit of a problem getting tinc up and running between a pair of RedHat (one 6.0, the other 6.1) boxes. It's installed and configured to the point where they can connect, but I'm not seeing any traffic passing between the two systems. System A looks like - tinc.conf: # Sample tinc configuration. # Insert your own ip numbers instead of the placeholders, # and be sure to use

I have now got the tinc demons (on network OFFICES) on BranchB and BranchA talking to each other, see below for log from BranchB. For some trouble shouting issues relating to OsX see at the end of my e-mail. However, I have not yet achieved the network connectivity/routing that I would like. The aim is: BranchB is a laptop I would like to connect it (via tinc) to my office network, so that