similar to: tinc and routing

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

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

> - Indirectdata finally REALLY REALLY works now! > - More precise debug messages Hmmm ... I can't prove that using the CVS code I checked out this morning. Everything works like yesterday: I can ping the peer but I canot go beyond: *** SERVER *** Jun 27 09:04:56 lemon tinc.9[10186]: tincd 1.0pre3 (Jun 27 2000 08:53:56) startin g, debug level 4 Jun 27 09:04:56 lemon tinc.9[10186]:

I gave tinc1.0pre3 a test after the modifications you have done today. It insists that it is still 1.0pre2 but this is due to the fact the you used "1" as tag for configure.in rather than "CABAL". Anyway - results were not much more successful than yesterday: *** SERVER side log file from startup until sone seconds after connection was established *** Jun 25 21:14:30 lemon

*You should repeat this for all nodes you ConnectTo, or which ConnectTo you. However, remember that you do not need to ConnectTo all nodes in the VPN; it is only necessary to create one or a few meta-connections, after the connections are made tinc will learn about all the other nodes in the VPN, and will automatically make other connections as necessary. * The above is from the docs. Assuming

On 30.08.2016 17:37, Guus Sliepen wrote: > On Tue, Aug 30, 2016 at 02:38:16PM +0200, Armin Schindler wrote: > >> we use a meshed VPN with TINC to connect 7 offices. >> Some office are in other countries and use other ISPs. The connection >> between some ISPs (peering partners) are not that good. This means we >> have packet loss between those direct connections.

Hi, Lars Thanks for your suggestion, will give it a try later to see how it performs. But, yesterday, I did a below test: A ConnectTo B and C, B ConnectTo D, C ConnectTo D; All nodes turned "IndirectData" on in its host configuration, so the tunnel only follow metacomnection instead of direct connect. D announced default route by having the Subnet = 0.0.0.0/0 statement in its host

Hi, here's a small list of things that need to be done, and the version when it should be ready. smartcard support 1.1 LDAP support 1.1 public/private keys for authentication 1.1 don't store passphrases in files that are called after IP addresses 1.0 use names to identify

Hi everyone, I'm setting up a VPN over IPv6, attempting to build an IPv4-over-IPv6 tunnel, but when I try to connect to the server, I got this: System call `getaddrinfo' failed: Address family not supported. Client runs WindowsXP, and I did almost exactly the same as http://www.tinc-vpn.org/examples/windows-install . Here is the configuration files: ------- tinc.conf ------- Name =

Hi I'm trying to implement a scheme in which the nodes will have a direct UDP tunnel to each other. First, all nodes make connection with one public node, and then make connections with each other. And I came across the following problem: Remotely located nodes can establish a direct UDP connection, but the nodes that are in the same local network can not, and all traffic goes through the

On Tue, Apr 10, 2018 at 03:36:08PM +0200, Hans de Groot wrote: > hosta  <--> hostb  <-->  hostc > > Hosta and hostc are not directly connected via tinc. But both are conncted > via hostb (I called my network tincnet). This works fine I can ssh from > hosta to hostc and vice versa without any problems. > > hostc is in a whitelisted iprange at some service

Hi, I have been messing arroudn with tinc for a while and now I got a configuration working like the example (4.7) from the manual I have 3 systems, in my case system a is the only one that can be accessed directly. B and C connect to A I have 3 subnets A 5.1.0.0 gw 5.1.0.1 B 5.2.0.0 gw 5.2.0.1 C 5.3.0.0 gw 5.3.0.1 This work fine and the gateways are ip number son t he interfaces of the 3

Hello. I apologize in advance for my question -- it's seemingly trivial, but I've spent countless hours on its solution to no avail. Basically, I have two tinc servers: Home: Ethernet adapter LAN: IP Address. . . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 Ethernet adapter

Hello all, we use a meshed VPN with TINC to connect 7 offices. Some office are in other countries and use other ISPs. The connection between some ISPs (peering partners) are not that good. This means we have packet loss between those direct connections. To avoid this direct connection, I would like to tell TINC to use a defined other host to route the packets to. E.g. instead of doing direct

Hi Ivo, --On Freitag, 23. Juni 2000 01:15 +0200 Ivo Timmermans <zarq@icicle.yi.org> wrote: > I'm not sure I fully understand your patch. This is not so important since I'm trying to get 1.0pre2 running. Although I had no luck so far, I'll point out what's going wrong at the end of this mail. > For instance, you force a > key exchange when the connection is made,

Hi there, I would need some help with my configuration. I have tried a long time, but did not find my error. Thus I would really appreciate your help. There are three hosts: 1. h181 2. h182: Should ConnectTo h181 3. h183: Should ConnectTo h181 *Files under /etc/tinc/vpn0/hosts* [h181:] Address = 94.130.108.xxx Subnet = 172.16.1.1/32 -----BEGIN RSA PUBLIC KEY----- *** -----END RSA PUBLIC

We are testing tinc inside Google Compute within a single region and an external region. Two boxes are created as follows: /etc/tinc/test/tinc_test_1 Subnet = 10.240.0.0/16 Subnet = 10.240.0.4/32 Address = 104.154.59.151 /etc/tinc/test/tinc_test_2 Subnet = 10.240.0.0/16 Subnet = 10.240.0.5/32 Address = 104.197.132.141 /etc/tinc/test/tinc.conf Name = $HOST AddressFamily = ipv4 Interface = tun0

Hi, I've set up Tinc in switch-mode on the three nodes "gw", "rb493g" and "v900w", but the nodes "rb493g" and "w900v" do not connect to each other. On each node port 655 is opened with TCP and UDP. "gw": static IPv4- and IPv6 address listed in the hosts-file "gw" hosts-files: "gw",

hi folks well, tinc is a really nice tool and we implemented it on 3 linux servers and 2 mobile clients (XP notebooks) so far. one of the 3 tinc servers is making troubles, when a connection is initiated from this server over a zyxel 642 adsl router out to the other 2 servers in the internet. the logfiles of the other 2 servers shows: > tinc[1398]: Received UDP packet from unknown

I don't know why, but for my case, I reduced the tinc topology from a complex one(which provide layered redundancy) to a very simpled one(one connection), and that connection drop disappeared. Later, let me draw the topology and share the config to you to see if there's any findings of the cause. Guus Sliepen <guus at tinc-vpn.org>于2017年9月14日 周四上午3:20写道： > On Wed, Sep 13, 2017