similar to: bridging tinc router mode network and switch mode network

> On Jun 4, 2015, at 5:52 PM, Etienne Dechamps <etienne at edechamps.fr> wrote: > > Are you sure B is correctly configured to forward packets at the layer > 3 level between the interface of the "router" tinc and the interface > of the "switch" tinc? (iptables, etc.) > No, I am not sure about this and I think this is what I don?t understand properly

Are you sure B is correctly configured to forward packets at the layer 3 level between the interface of the "router" tinc and the interface of the "switch" tinc? (iptables, etc.) On router B, are you sure the node file for B on the "router" tinc is configured to announce the entire 192.168.15.0/24 subnet (i.e. Subnet = 192.168.15.0/24)? Otherwise B won't get the

I?ve been having the same issue with Ubuntu, thankfully we have access to Upstart: ``` start on (local-filesystems and net-device-up IFACE!=lo) stop on stopping network-services author "Mark Lopez" description "Tinc Upstart Job" version "0.1" env network=master respawn exec /usr/sbin/tincd -n "$network" -D --debug=3 --logfile ``` I removed the default

I have tinc 1.1pre11 running on various routers and linux cloud servers. On one of the cloud servers, under Ubuntu 12.04, tinc is mysteriously dying once in a while, leaving a dangling PID. I have been unable to track down why it is dying, but it happens infrequently enough that I care less about why it is dying than how to robustly respawn it when it dies. Before I re-invent the wheel, has

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

> 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

Dear Lance, It is not work. Any idea? Regards, Eric -----Original Message----- From: Lance Fredrickson [mailto:lancethepants at gmail.com] Sent: Wednesday, February 17, 2016 12:53 AM To: tinc at tinc-vpn.org Subject: Re: Tinc Router Mode - PING RESULT is destination host unreachable On 2/16/2016 9:04 AM, Eric Yau wrote: > Hi Lars, > > Once I modify the firewall FORWARD rule to

I run tinc on a series of routers running 3rd party firmware (tomato). Since tinc is running on the gateway device, its routing table is aware of the mesh vpn. At each endpoint, any device one subnet can access any device on another subnet. I now have the situation where I need to make a new endpoint and entire subnet available on the mesh. In this situation I have a device running tinc

Would it be possible to mix the router and switch mode in the same tinc network?  I’m running tinc for a couple of years now in switch mode. It works very well. I have a dozen of vm’s connected to a couple of VM’s on 2 physical nodes. Those VM’s on the physical nodes are connected via a 2nd interface to an openvswitch bridge on which those physical nodes provide the connection outside. As extra

about tomato firmware... can I install it on a VMware virtual machine? tinc web ui is already included with the last tomato version? king regards, Cristiano. 2015-06-08 16:52 GMT-03:00 Lance Fredrickson <lancethepants at gmail.com>: > On 6/8/2015 11:55 AM, Cristiano Albiero Berni wrote: > > 2- Is there a kind of web interface to manager the server? >> > Tinc itself

The documentation is very clear that multicast over tinc does not work in router mode. Why?

Hi, I have two concerns about tinc's behavior regarding MAC addresses in router mode: - Looking at the code, it appears that tinc is always sending each packet with its Ethernet header, even if tinc is operating in router mode. It is my understanding that in router mode, all routing is done at the IP level, thus we do not need Ethernet information. This seems like unnecessary overhead.

Dear All, I am trying to enable router mode of tinc on Windows 7 platform. Although I have enabled the router mode and IP routing in Windows 7 PC (Network A Server). The PC B is still unable to connect the Network A and PC A. But the Network A and PC A is able to communicate each other via tinc. Please help and advise me any incorrect of that. Network A server Real - LAN adapter IP:

Dear tinc community, I am using tinc in switch mode. I have three nodes. Two nodes reside on routers, vpn-eth is bridged with internal lan, each router has several machines connected to it's internal lan. Third node is the roadwarrior - "endpoint" linux PC. When the roadwarrior is off - everything works perfectly, machines on both sides can communicate without a problem in any

Hello! I use tincd to interconnect 3 LANs: A, B and C. So long, it works fine: everybody reaches everybody. But I want a different behavior: A and B should be allowed to talk, as should B and C. I tried to simply delete the host-files on the nodes that should not be allowed to talk to eachother: A has a hostfile from B B has a hostfile from A and C C has a hostfile from B But this is no

Hi, I have some questions about tinc. " *Automatic full mesh routing*Regardless of how you set up the tinc daemons to connect to each other, VPN traffic is always (if possible) sent directly to the destination, without going through intermediate hops. " 1- To have client to client direct connection and don't have traffic through the server should I have port forward at the NAT? Or

What challenge this would solve ? VPN software in general tries to be another router when running in server mode with multiple clients. This restricts VPN customers from having complex topology. For instance, I'd like to have two tunnels between each client network and each server (with two broadband connections on each end), with some OSPF running and automatically switching from one to

Hi Lars, Once I modify the firewall FORWARD rule to ACCEPT. I can ping and access my company PC at home. All traffic can pass through that. But I think it is not a good practice to change the FORWARD rule to ACCEPT. Any idea to check and just allow the tinc VPN traffic only? Instead of allow everything pass through the FORWARD rule. Regards, Eric -----Original Message----- From: Lars Kruse

Hello to everybody, Sorry if my english isn?t very good. I need pass 802.1q through a VPN between two offices. I have mounted a WRT54GL, with OpenWRT firmware, conected to a switch trunk port in both offices. In the switch of the first office I have created five tagged VLANs and I need pass these VLAN to the second offices where it has created it too. Can I do this with Tinc in HUB/Switch

Greetings. I'm new to tinc, but have so far managed to get a couple laptops and a hosted server all connected. They're working as expected, running Tinc 1.1-pre11, which I compiled from source. Next I want to move on to adding my home router into the mix. My routers run OpenWRT. I don't have experience compiling anything from source for OpenWRT, but OpenWRT has Tinc 1.0.25