similar to: Changing interface based on network availability

tinc has been really useful for us, and so the other day I blogged about tinc as a way of saying thank-you, http://blogs.operationaldynamics.com/andrew/software/research/using-tinc-vpn.html Somewhat innocuously, I closed with reference to NetworkManager; having used it with openvpn and been very impressed with the experience (not the openvpn part, but the fact that GNOME's networking UI made

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 =

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

> kextload /Library/Extensions/tun.kext/ I didn't have a /Library/Extensions/tun.kext/ on my machine. I googled around, and downloaded and installed from http://tuntaposx.sourceforge.net/. Not sure why the macports install didn't work, but it seems I'm making progress. Now I get this: > sudo tincd -n dpsf -D -d3 tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3

Thanks very much! It's alive! For others who are having problems, this is a summary of the differences I needed between Linux and OS X: You'll need to install http://tuntaposx.sourceforge.net/ manually. On tinc.conf: > Linux Name = ntwigg2014linux AddressFamily = ipv4 Interface = dpsfVPN ConnectTo = dpserver001 > Mac Same, but remove the Interface line entirely On tinc-up: >

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

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

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

I've got tinc running happily on a couple linux and win computers, but no luck on OS X. I'm on Yosemite 10.10.5, and I think I followed the OS X tutorial exactly, but no luck. Here's my error message: > sudo tincd -n dpsf -D -d3 tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3 Could not open /dev/tun0: No such file or directory Terminating And here's the contents

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

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

Hello, I'm trying to get tinc working on my mac. It appears to connect to other nodes, but I can't actually use the vpn. If I enter the command ifconfig tun0 10.11.12.195 netmask 255.255.255.0 I get the error ifconfig: ioctl (SIOCAIFADDR): Destination address required If I enter the commands ifconfig tun0 10.11.12.195 10.11.12.195 netmask 255.255.255.0 route add -net 10.11.12.0

>> >> 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 Guus, thank you very much for your suggestions, I could not dive into it further because I was traveling, but now I have time to reconfigure the network. At first I really like the idea of having 3 Daemons on the headquarter, one for each ISP. The firewall should forward the port 655 from each ISP's public IP Address to my internal server and to the ports 655, 656, 657 respectively,

Hi, I am trying to install tinc on a mac. When starting tinc a /dev/tun0 is created, on linux a device is created with a custom name, something like 'ci00001'. How can i achieve the same result on a mac ? Perry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20130921/3acfb278/attachment.html>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 10 Mar 2015 02:10:51 +0100 Guus Sliepen <guus at tinc-vpn.org> wrote: > If that was not the problem, then another issue might be the version > of OpenSSL on your Beaglebone not supporting the Cipher or Digest > algorithms that you are using. > This seems the most probable from the various tests and key changes and so forth

Hi all, I try to receive an ipv6 address for my PPP link via autoconf (against Cisco machine), but there is a problem I'm unable to solve so far. I can see cisco's Router-Advertisement containing prefix etc., but no IP adress is assigned to tun0 interface. Anyone succesful in IPv6 over dial-up PPP connection? When I manually assign IPv6 address, connection works. My system is

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: