similar to: tinc 1.1pre4 Win7x64 import does not recognize Unix EOL

ping times to ConnectTo machine are often over a second or at least 300 milliseconds. Hundreds or thousands of times slower than other nodes from same physical location.

c:\APPS\TINC\tincd.exe --mlock --net=mynet --config=C:\APPS\tinc\mynet Without --mlock, the service starts OK. With --mlock, the service fails to start.

I have the habit of putting the name of the host within the host file as a comment usually on the first line. Helps when files are renamed and tracking. The new version exports Name = victor and so the old comment style is not necessary. I would think the new version should still simply ignore lines that begin with the '#' character. For example, a normal host file named victor that

Would it be extremely difficult to do multicast over tinc? How about reliable multicast over tinc? This would be more traffic than multicast dns, but not _necessarily_ a great deal more. It would be for syncing some information among freeipa domain controllers. Would the tinc nodes need to be in all in switch or maybe even hub mode? EthernetOverIP over tinc?

i have a switched and bridged tincd node with two addresses, each with a different port. Address = 37.70.156.168 28655 Address = 192.168.2.228 655 i was having trouble reliably connecting to it / thru it and noticed that a log from a remote tincd node indicated it may have mixed up the ports. It doesn't appear to use the 28655 port that would be needed for remote access. Before i

Since Fedora is pushing NSS SSL instead of OpenSSL, has someone tested tinc-vpn against NSS? As i recall, a single machine can not have OpenSSL and mod_nss installed at the same time anymore. So if you have apache running, you _may_ have problems running tinc? The nss api is supposed to mostly similar to openssl api, but there are some things openssl supports and somethings nss supports. Is

Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. When the server does not receive a PMTU request back from one of the clients even when the packet size is very small (say 164), then it reverts to TCP. Should i turn off PMTUDiscovery or should it be ok to leave on? It takes a very long time to do simple pings (1 second or so), so i wonder what else i can do?

With pleasure we announce the release of version 1.1pre3. Here is a summary of the changes: * Added the "AutoConnect" option which will let tinc automatically select which nodes to connect to. * Improved performance of VLAN-tagged IP traffic inside the VPN. * Ensured LocalDiscovery works with multiple BindToAddress statements and/or IPv6-only LANs. * Dropped dependency on

With pleasure we announce the release of version 1.1pre3. Here is a summary of the changes: * Added the "AutoConnect" option which will let tinc automatically select which nodes to connect to. * Improved performance of VLAN-tagged IP traffic inside the VPN. * Ensured LocalDiscovery works with multiple BindToAddress statements and/or IPv6-only LANs. * Dropped dependency on

Hi to everybody, Can anybody tell me what packages I need to install Tinc 1.1pre2 in a server that it had installed a previous version installed? I tried to install it and when I execute the "make" it give me a lot of errors. Best regards, Ramses

On Fedora 11 (yes, with SELINUX enabled and enforcing) setting tinc.conf's ProcessPriority=high prevents tincd from starting. Anybody have an answer? tinc was compiled by me, didn't come from Fedora's rpm repo.

Something tells me this was covered recently, but i didn't find it again in gmail. The nodes see each other but if i have something misconfigured that is decreasing my speed. All my nodes are behind NATs. i have a remote node that connects to a central node via port forwarding from public port 7777 to hp821 running on port 655. remoteNode ----> public ip 1.2.3.4:7777 ---->

Dear tinc members! Recently I ran into some problems when trying to test the new tinc 1.1 builds under windows. The main problem is that the tincd daemon randomly hangs (usually in first 1-3 minutes after start). Sometimes it happens quietly, and the log does not display anything. But from time to time, there are bunch of decryption errors ("Error while decrypting: error:06065064:digital

Window allows one to specify a DNS domain name and DNS server for a particular interface. So all DNS queries of your tinc interface are sent to a particular dns server. For instance windows tinc clients can use a particular dns server on a private LAN available only to clients inside that NAT or tinc clients. NetworkManager allows you to specify the same, but the tinc interface does not show up

Hello, I have tried for days on end with no success on this, so I thought I would post it here and see if someone can help me at all. *Here's the scenario:* I have 1 PC with a Static IP/Domain (a dyndns.org account - myserver.homeip.net) connected to a router, which in turn is the gateway to the internet. It also has a static local IP (192.168.1.2). I will call this the "server"

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

IPsec Pre Shared Key for enterprise wireless is worse than PPTP according to https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/ . Make sure IPsec is used with certificates instead. tinc is an educational project sponsored by a university aiming to grow awareness of encryption over the public internet. It does not have a marketing department. Criticism is welcome. Think of

Hello, Is there a way to reliably identify a tinc TCP connection using iptables? Looking at the iptables documentation, the u32 test seems to be very flexible (though the "language" of the tests pretty unreadable): u32 U32 tests whether quantities of up to 4 bytes extracted from a packet have specified val? ues. The specification of what to extract is general enough

*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 upgraded some of my Tinc nodes from 1.0.8 recently and found something strange. All of a sudden, the vpn would not work as a full-mesh. Certain nodes were not contactable. I re-generated my rsa-keys, and checked my configuration. My vpn uses the following in tinc.conf, as I am routing both ipv4 and v6. === name = node1 mode = switch AddressFamily = any PMTU = 1280 PMTUDiscovery = yes