similar to: [Announcement] Version 1.1pre1 released

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

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

> > Maybe I should allow the reachable keyword for the dump graph command as > well, so you can do: > > tincctl -n <netname> dump reachable graph > > ...and not see any nodes which are unreachable. Is that what you want? This would help since dead nodes do not clutter the visual representation. What are the effects, if any, of dead nodes in the hosts/ dir? Thanks

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

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

On Tue, Dec 11, 2018 at 02:36:18PM +0800, Amit Lianson wrote: > We're suffering from sporadic network blockage(read: unable to ping > other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release, > the same network blockage also manifested itself in a pure 1.0.33 > network. > > The log shows that there are a lot of "Got ADD_EDGE from nodeX >

For my opinion, special function not needed, because at first time, oai set to NULL, freeaddrinfo tried to free each ai, until occurance of ai_next == NULL. But it works. Linux, Windows, coordinator with white IP, other nodes behind NAT's (1 or two NAT's, only direct connections allowed). There are some problems with MinGW make, at least - mingw-64 from Fedora 25. 1. No definition for

A long long time ago, I asked about the different tinc branches. Guus, you said at the time that * trunk is 1.0, bugfixes only * 1.0-gnutls, POKEY, and pre4-cube are stagnant * 2.0 is where new work should happen...at the time, it didn't compile, and it appears it still doesn't This answer discouraged me; I have trouble getting excited about new work in a branch that's been

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

Apparently I install some packages in the wrong way and now I'm having some problems updating my OS. This is what I'm doing: # yum update --enablerepo=remi,remi-php5 Loaded plugins: fastestmirror, security Setting up Update Process Loading mirror speeds from cached hostfile epel/metalink 2.3 kB 00:00 * base: centos.xpg.com.br * epel: mirror.globo.com

I cant restart my tincd with 'tincctl restart -n $NETNAME' I get the message: 'Could not restart tinc daemon' It works with 'tincctl stop -n NETNAME && tincctl start -n NETNAME' but sometimes the /var/run/tinc.$NETNAME.pid file is missing so I need to kill tinc manually

On Tue, 27 Feb 2018 08:12:53 +0100, Guus Sliepen wrote: > I was thinking by setting a flag whenever we call io_del(), and checking > that flag in the for-loop in event_loop(). So basically you would store a generation number in the tree that gets incremented by a call to io_del()? Or should the flag/number be changed each time the order of the tree changes? > > Changing the order

Only the short -b option is missing, --batch works as expected. - todd diff --git a/src/tincctl.c b/src/tincctl.c index 9eb9a1b..766b769 100644 --- a/src/tincctl.c +++ b/src/tincctl.c @@ -168,7 +168,7 @@ static bool parse_options(int argc, char **argv) { int r; int option_index = 0; - while((r = getopt_long(argc, argv, "+c:n:", long_options, &option_index)) != EOF) { +

There are at least three cases: * Linux: check credentials and pid from client; restrict permissions from server * BSD: check credentials only from client; restrict permissions from server * Solaris: wide open --- configure.in | 4 ++-- src/control.c | 11 ++++++++++- src/control_common.h | 1 + src/tincctl.c | 38 ++++++++++++++++++++++++++++++++++---- 4

Ok, for further info, below is the full compiler output when running gnu make. The first error, ../thread/thread.h:78: parse error before `pthread_rwlock_t' is the one that brings on all the others. I've checked /usr/include/pthread.h and didn't find pthread_rwlock_t in it. So my guess is, pthread on solaris 2.6 is too old (afaik, there are three versions of solaris that are

Hi: WARNING: This is long. Just updated libshout and configured. Configure didn't bomb so I guess it went OK and found what it wanted. But when I ran make I got this: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I./.. -g -O2 -Wp,-MD,.deps/avl.pp -c avl.c -fPIC -DPIC -o .libs/avl.lo In file included from ../stream.h:20, from ../config.h:17, from avl.c:33: