similar to: [Announcement] Version 1.0.13 released

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

With pleasure we announce the release of version 1.0.11. Here is a summary of the changes: * Really allow fast roaming of hosts to other nodes in a switched VPN. * Fixes missing or incorrect environment variables when calling host-up/down and subnet-up/down scripts in some cases. * Allow port to be specified in Address statements. * Clamp MSS of TCP packets to the discovered path MTU.

With pleasure we announce the release of version 1.0.11. Here is a summary of the changes: * Really allow fast roaming of hosts to other nodes in a switched VPN. * Fixes missing or incorrect environment variables when calling host-up/down and subnet-up/down scripts in some cases. * Allow port to be specified in Address statements. * Clamp MSS of TCP packets to the discovered path MTU.

With pleasure we announce the release of version 1.0.5. Here is a summary of the changes: * Lots of small fixes. * Broadcast packets no longer grow in size with each hop. This should fix switch mode (again). * Generic host-up and host-down scripts. * Optionally dump graph in graphviz format to a file or a script. * Support LZO 2.0 and later. This version of tinc is compatible with

With pleasure we announce the release of version 1.0.5. Here is a summary of the changes: * Lots of small fixes. * Broadcast packets no longer grow in size with each hop. This should fix switch mode (again). * Generic host-up and host-down scripts. * Optionally dump graph in graphviz format to a file or a script. * Support LZO 2.0 and later. This version of tinc is compatible with

Hello, I am tying to create tinc vpn for the ~1000 nodes and was thinking why meta connections are needed at all if I only need static configuration where every node knows addresses of other hosts and due to the amount of traffic any indirect connections will not work, so DirectOnly=yes is a must and then passing around routing information is not needed, right? Currently I have 10 nodes

With much pleasure we announce the release of version 1.0. Here is a summary of the changes: * Lots of small bugfixes and code cleanups. * Throughput doubled and latency reduced. * Added support for LZO compression. * No need to set MAC address or disable ARP anymore. * Added support for Windows 2000 and XP, both natively and in a Cygwin environment. This version is compatible with

With much pleasure we announce the release of version 1.0. Here is a summary of the changes: * Lots of small bugfixes and code cleanups. * Throughput doubled and latency reduced. * Added support for LZO compression. * No need to set MAC address or disable ARP anymore. * Added support for Windows 2000 and XP, both natively and in a Cygwin environment. This version is compatible with

With pleasure we announce the release of version 1.0.6. Here is a summary of the changes: * More flexible detection of the LZO libraries when compiling. * Fixed a bug where broadcasts in switch and hub modes sometimes would not work anymore when part of the VPN had become disconnected from the rest. This version of tinc is compatible with 1.0pre8, 1.0 and later, but not with earlier

With pleasure we announce the release of version 1.0.6. Here is a summary of the changes: * More flexible detection of the LZO libraries when compiling. * Fixed a bug where broadcasts in switch and hub modes sometimes would not work anymore when part of the VPN had become disconnected from the rest. This version of tinc is compatible with 1.0pre8, 1.0 and later, but not with earlier

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

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

With pleasure we announce the release of tinc version 1.1pre16. Here is a summary of the changes in tinc 1.1pre16: * Fixed building with support for UML sockets. * Documentation updates and spelling fixes. * Support for MSS clamping of IP-in-IP packets. * Fixed parsing of the -b flag. * Added the ability to set a firemall mark on sockets on Linux. * Minor improvements to the build system.

With pleasure we announce the release of tinc version 1.1pre16. Here is a summary of the changes in tinc 1.1pre16: * Fixed building with support for UML sockets. * Documentation updates and spelling fixes. * Support for MSS clamping of IP-in-IP packets. * Fixed parsing of the -b flag. * Added the ability to set a firemall mark on sockets on Linux. * Minor improvements to the build system.

If you're using StrictSubnets, you will still be fine. StrictSubnets means that A will only use B's key (which C does not know) to send packets to B's statically configured subnets. C cannot impersonate B (as in, take its node name) because it would have to know B's private key to do so, and it cannot impersonate B's subnets because A is using StrictSubnets. The worst that C

With pleasure we announce the release of tinc version 1.0.27. Here is a summary of the changes: * When using Proxy, let the proxy resolve hostnames if tinc can't. * Fixes and improvements of the DecrementTTL option. * Fixed the $NAME variable in subnet-up/down scripts for the local Subnets. * Fixed potentially wrong checksum generation when clamping the MSS. * Properly choose between

With pleasure we announce the release of tinc version 1.0.27. Here is a summary of the changes: * When using Proxy, let the proxy resolve hostnames if tinc can't. * Fixes and improvements of the DecrementTTL option. * Fixed the $NAME variable in subnet-up/down scripts for the local Subnets. * Fixed potentially wrong checksum generation when clamping the MSS. * Properly choose between

Hi, I had some performance problems with TINC running on Windows XP. I had a VPN tunnel running over a wireless network to a Linux VPN server. Web browsing through the tunnel was a pain. Big web pages with lots of pictures loaded very slow compared to a plain network connection. When the VPN client was running on a Linux computer, and a Windows computer was browsing the web through the VPN