similar to: tinc and routing Cont'd

Hi Ivo, A2000 smtp says iname.com is on its blacklist, and icicle.yi.org is bouncing my emails: in: function build_fdset() status.active should be status.dataopen Greetz -- hansb - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://ftp.nl.linux.org/pub/linux/tinc/

Hi, I have an experimental setup with two interconnected LANs by means of tinc and a cable ISP. Within the two LANS, two machines act as a router: they have a route from LAN a to LAN b using the tap0 device in their routing tables. The route is manually added by the route command. If for one reason, tincd crashes the route disappears also. What would be the best way to solve this problem?

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

This Message was undeliverable due to the following reason: The user(s) account is temporarily over quota. <hansb@direct.a2000.nl> Please reply to Postmaster@direct.a2000.nl if you feel this message to be in error. -------------- next part -------------- Skipped content of type message/delivery-status-------------- next part -------------- An embedded message was scrubbed... From:

Hello everybody, I am doing some test with TINC and Windows 7 and I am having some issues with routing. (see attachment for the client configuration) The set-up I configured uses DHCP over the TINC tunnel and the Windows guests ends up with two gateways (one from its own network and one from the TINC network). The problem is that traffic when browsing the internet should go over the TINC tunnel

Hello, I'm trying to use tinc to establish a vpn between two linux boxes. The keys are shared and the connection gets established, but I can't seem to ping either side. One side is strictly a server for the client to connect to. It has a public IP, and the private IP subnet which it's trying to "share" to the client. It's a pretty simple and straight forward setup.

Hi, Hopefully someone can help me. I've been trying to set up a private vpn, for both internal ipv6 and ipv4 traffic. There are two Hosts involved with the vpn at the moment. I've been struggling with this but am now going round in circles - Can anyone recognise and explain what i'm doing wrong? The tinc daemons are listening on an ipv4 address, connected to the standard

Hi, I setup tinc on two hosts with IP 192.168.200.102 on the first and IP 192.168.200.101 on the second. And it works. Now I would like to route packets thru 192.168.200.101 from 192.168.200.102 by adding the following route: ip route add 10.10.70.0/24 via 192.168.200.101 dev TINCDEVICE However, when I ping 10.10.70.254 from 192.168.200.102, I see the packet being sent to TINCDEVICE (tcmpdump)

Hi tinc list members, There were some problems with Ivo's email adresses (both zarq@iname.com and zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list. ============================================= Hi Ivo, Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere troepjes zoals een tincd scheduler. Dit werkt wat beter, omdat de

On Wed, Jan 10, 2018 at 11:29:22AM +0100, cr0n wrote: > Meta connection graph: > > A – B – C – D > │ │ > └─ E ───────┘ > > Node configuration: > > • StrictSubnets = yes > • AutoConnect = yes > • B has Forwarding = internal, all other nodes have Forwarding = off > > All nodes can reach each other directly with UDP *except* A and D. > Packets

Hi, I have a question around whether there is any way to control tinc routing if you have multiple routes to the same destination. I have a three node configuration, let's call them: home -> connects to both other nodes vps1 -> a VPS, providing connection to the internet vps2 -> another VPS, also providing a connection to the internet Both vps nodes provide their own 192.168.x.0

Hi, I have successfully setup a tinc network between five hosts (in switch mode). Two of the hosts have static and known IP addresses (S1 and S2). Other hosts (H3-H5) connect one (or both) of them. The traffic flows nicely between all hosts. The initial edges (ConnectTo configuration directives) in my test network are: S1<->S2 H3 -> S1 and S2 H4 -> S1 H5 -> S2 As far as I have

Hi Daniel, Yes, thanks and I should have mentioned that I am using pretty much the same thing you suggested on my routers, but for whatever reason couldn?t get that approach working on the linux box in question. Mark, Thanks for the upstart script. I had tried to do the same myself but couldn?t get my upstart script to work right. I was missing the ?-D? flag in my script. Added that and now

I have two internal networks 192.168.9.0/24 and 192.168.0.0/24 each connected to the internet and each connected as a VPN via tinc (device vpn). The gateways are 192.168.9.1 and 192.168.0.1 Attached to the 192.168.9.0/24 network is another network 172.16.1.0/24 via a gateway 192.168.0.1 <==> 172.16.1.1. On 192.168.0.1 gateway I have routes (route -n) like this: Kernel IP routing table

hey there, Tinc will generate a new MAC address every time the daemon restarts. In my setup, in switch mode, I give IP addresses using DHCP to the different tinc vpn clients. Some of these boxes are 'pets' and request a particular ip address which is specified in their dhclient.conf. My trouble is that since the MAC is regenerated every time the daemon is restarted, I am forced to have

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

On Mon, Jan 16, 2017 at 11:31:18AM +0000, Azul wrote: > Tinc will generate a new MAC address every time the daemon restarts. It is actually the kernel that generates a new MAC address for the tun/tap interface. > if there a way to control that tinc MAC behaviour ? ie. generate it once > and re-used that same one every time ? You can set the MAC address yourself in the tinc-up script.

Hi, can anybody tell me the differneces in routing inside of tinc in version 1.1. Is there some detection for slow tunnels, use other way then? Meybe there is some webpage, than I would be thankfull for the link. ALBI...

Hi list, I have a question regarding routing in Tinc 1.1. Please consider the following example of a small network: • 5 nodes: A, B, C, D, E • C and E are nodes with very small bandwidth Meta connection graph: A – B – C – D │ │ └─ E ───────┘ Node configuration: • StrictSubnets = yes • AutoConnect = yes • B has Forwarding = internal, all other nodes have Forwarding = off All nodes