similar to: Testing 1.0pre2 from CVS

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

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,

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

Whens the point and click GUI coming out? All kidding aside, I seem to be confused about some of the network settings. Essentially all I want is a secure tunnel from machine A to B on two different physical networks, but I can't seem to get there. Just to get things figured out I've got two machines on the same physical network, mach A: 192.168.0.1, mach B: 192.168.0.3. bcast is

I created an application that uses dynamic forking and it works perfect in windows, but fails in wine. Is this a bug or is this feature disabled in Wine? I don't have wine myself but someone we have testing the app for us does. It's difficult to debug over the net so I was hoping for some help here... After adding some debug info we've traced a few failure points to a call to

Hi, Etienne I took a look for the below host configuration parameter (IndirectData), the default is no. For the below example: A ConnectTo B, B ConnectTo C: If IndirectData = no (default), then A wouldn’t establish direct connection with C, but will be forwarded by B. If IndirectData = yes, then A will try to establish direct connection with C, even though A don’t have the statement of

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

Hi list, I'm hoping someone can help me understand when to use IndirectData. Quoting the manual: IndirectData = <yes|no> (no) This option specifies whether other tinc daemons besides the one you specified with ConnectTo can make a direct connection to you. This is especially useful if you are behind a firewall and it is impossible to make a connection from the outside to your tinc

Hello again :) Thank you all for your reply's. Below are the config files of the 3 hosts. I use  tinc in router mode. I do not have a kernel mode config lines anywhere so tinc must be using the default settings here. I added the ipaddressx to subnets on hostc and this works. Traffic to that ip is now routed via hostc. But since this ipaddressx address changes often I need to resolve it

Well this has had me stumped for days now. For months I've been using tinc in TCPOnly because I always received the unknown host error when using UDP. On Monday, i set the flag IndirectData = yes in my host files, and removed the TCPOnly line. Initially, everything worked great. My throughput increased from 600KB/sec to 2MB/sec between the sites. However, I also did some testing with

Hi, All Here is the case: A, B, C, D all configured with "IndirectData = yes”, so connection only happens when there’s a “ConnectTo” in tinc.conf. Arrow indicate the “ConnectTo” direction Everything works fine earlier as below: 1. A connect to C, D connect to C 2. C is the transit node where only forward traffic between A and C 3. D advertise 0.0.0.0/0#2 4. A can access internet from D

*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

Hi, I´m using Tinc for several years, but I didn´t fix a performance problem. There a about 20 nodes in this network. Master: 10.0.0.12 (dedicated host in a datacenter, debian, 100mBit port) tinc.conf: Name = TincKnoten12 AddressFamily = ipv4 Interface = tun ProcessPriority=high mode = router #DirectOnly = no Compression=0 PMTUDiscovery = yes #IndirectData = yes #ReplayWindow = 64 #ConnectTo

On 11 April 2018 at 11:30, Hans de Groot <hansg at dandy.nl> wrote: > Hello again :) > > Thank you all for your reply's. Below are the config files of the 3 hosts. > I use tinc in router mode. I do not have a kernel mode config lines > anywhere so tinc must be using the default settings here. > > I added the ipaddressx to subnets on hostc and this works. Traffic

Hi there, Following situation: 3 nodes, Alpha (Home fileserver), Beta (regular PC), Gamma (Notebook). All three in a NATed LAN usually, though the notebook also gets carried around and connects from the outside from time to time. Tinc should help me keep my other 2 PCs reachable from Gamma, even when I'm not at home. Also I plan on maybe adding more nodes to that in the future. I have set

Hi, There are several issues with tinc that need to be fixed: - IndirectData: currect protocol "masquerades" hosts which have IndirectData set. This is bad, because you can't do loop detection anymore, and it requires a lot of dirty code to do the masquerading properly. - Loop detection: request handlers must be revised to break the right connections upon detecting a loop. -

Le 31/08/2016 à 10:47, Armin a écrit : > 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

Well i currently try to set up tinc between two hosts, one with normal dsl connection one behind some kind of unknown firewall (Note since OpenVp is able to connect when the normal one is the Server I guess tinc should be able, too) start.bat-------------------------------tincd -n Empire-Network -D -d4 --bypass-security (Bypass is only currently because tis not working yet)

Hello, I'm running a tinc network including dozens of nodes in switch mode. Some are running stable branch 1.0, while a small set of nodes are running 1.1 with ed25519 support. I discovered some routing issue between two nodes: (names are hidden) A (1.1): ConnectTo = B ConnectTo = C IndirectData = yes Mode = Switch B (1.0): Mode = Switch C (1.1 but only with RSA key): Mode = Switch

Hi! here a little patch for darknet functionality, i hope it does what its intended for sufficiently ... but it seems to work :). what should it do? imagine your friend-network. A trusts B and C. B trusts D and E, D trust F, C trusts G. All trust relationships are mutal A <---> C <---> G ^ \ \-----> B <---> D <---> F ^ \ \---> E