similar to: [Announcement] Version 1.1pre4 released

Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion

With pleasure we announce the release of tinc version 1.1pre10. Here is a summary of the changes: * Added a benchmark tool (sptps_speed) for the new protocol. * Fixed a crash when using Name = $HOST while $HOST is not set. * Use AES-256-GCM for the new protocol. * Updated support for Solaris. * Allow running tincd without a private ECDSA key present when ExperimentalProtocol is not

With pleasure we announce the release of tinc version 1.1pre10. Here is a summary of the changes: * Added a benchmark tool (sptps_speed) for the new protocol. * Fixed a crash when using Name = $HOST while $HOST is not set. * Use AES-256-GCM for the new protocol. * Updated support for Solaris. * Allow running tincd without a private ECDSA key present when ExperimentalProtocol is not

With pleasure we announce the release of version 1.1pre3. Here is a summary of the changes: * New experimental protocol: * Uses 521 bit ECDSA keys for authentication. * Uses AES-256-CTR and HMAC-SHA256. * Always provides perfect forward secrecy. * Used for both meta-connections and VPN packets. * VPN packets are encrypted end-to-end. * Many improvements to tincctl: *

With pleasure we announce the release of version 1.1pre3. Here is a summary of the changes: * New experimental protocol: * Uses 521 bit ECDSA keys for authentication. * Uses AES-256-CTR and HMAC-SHA256. * Always provides perfect forward secrecy. * Used for both meta-connections and VPN packets. * VPN packets are encrypted end-to-end. * Many improvements to tincctl: *

With pleasure we announce the release of tinc version 1.1pre5. Here is a summary of the changes: * Fixed long delays and possible hangs on Windows. * Fixed support for the tunemu device on iOS, the UML and VDE devices. * Small improvements to the documentation and error messages. * Fixed broadcast packets not reaching the whole VPN. * Tincctl now connects via a UNIX socket to the tincd

With pleasure we announce the release of tinc version 1.1pre5. Here is a summary of the changes: * Fixed long delays and possible hangs on Windows. * Fixed support for the tunemu device on iOS, the UML and VDE devices. * Small improvements to the documentation and error messages. * Fixed broadcast packets not reaching the whole VPN. * Tincctl now connects via a UNIX socket to the tincd

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

[This email is either empty or too large to be displayed at this time]

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.

Hello, First of all thank you very much for Tinc. I have been using 1.0.24 under Debian & Alpine Linux 32 bit using 'BindToAddress' in tinc.conf without any issues to bind to an IPv6 ULA Address. With 1.1pre10 'BindToAddress' in tinc.conf on the client machines fails with: ============================================================================== tincd 1.1pre10 (Jun

Hi! I'm trying to compile tinc-vpn 1.1pre3 on Ubuntu 12.10, but I get this error: checking curses.h usability... no checking curses.h presence... no checking for curses.h... no configure: error: "curses header files not found." (See the attached text file for the output when running ./configure) I have searched on google after this error message but I can't find anything

Hi, I'm new to Tinc, so a "Hello" to all! :-) In my setup one master node has a static public IP. All other nodes have dynamic public IPs changing every 24 hours (and yes, in Germany even Global IPv6 Unicast Prefixes are dynamic on DSL/Cable sockets :-( ). To distribute the dynamic node-IPs to all other nodes, the following "host-up" script is used:

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

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.

First off, thanks to all who have made tinc possible and continue to work developing it. I hope perhaps in time I can become a useful part of this community. :) I'm having an interesting issue with tincctl and was hoping someone could shed some light on it. Everything seems to work correctly when I build for OSX; however on linux and windows builds, I always receive connection

Hi, I've stumbled upon a problem which I can't solve easily with the available options in tinc - at least as far as I see. If enlightenment is all I need, I'll happily accept pointers ;) I try to establish a connection between two hosts. Each host has multiple addresses assigned to it's internet interface. A stripped down list would be: Host 1: 2001:780:0:1e::1

With pleasure we announce the release of tinc version 1.1pre6. Here is a summary of the changes: * Fixed tincd exitting immediately on Windows. * Detect PMTU increases. * Fixed crashes when using a SOCKS5 proxy. * Fixed control connection when using a proxy. This is the sixth pre-release of the 1.1 branch of tinc. Tinc 1.1 is protocol compatible with 1.0.x, but will have large

With pleasure we announce the release of tinc version 1.1pre6. Here is a summary of the changes: * Fixed tincd exitting immediately on Windows. * Detect PMTU increases. * Fixed crashes when using a SOCKS5 proxy. * Fixed control connection when using a proxy. This is the sixth pre-release of the 1.1 branch of tinc. Tinc 1.1 is protocol compatible with 1.0.x, but will have large

Hi, Thanks to John Wice for helping me with an earlier question. My two PCs behind the same router are still having problems connecting. Would appreciate thoughts on what I?m doing wrong? Router: Port 655 forwarded to 192.168.1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall