similar to: [Announcement] Tinc version 1.1pre13 released

I have not been paying attention, I was kind of hoping ecn encapsulation was improved in this version? On Sat, Apr 30, 2016 at 12:12 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc version 1.1pre13. Here is > a summary of the changes: > > * Fix BSD tun device support that was broken in 1.1pre12. > * Speed up AutoConnect when

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

I have long included tinc in the cerowrt project as a lighter weight, meshy alternative to conventional vpns. I sat down a few days ago to think about how to make vpn connections work better through fq_codel, and decided I should maybe hack on a vpn to do the job. So I picked up tinc's source code for the first time, got it working on IPv6 as a switch in a matter of minutes between two

On Wed, Dec 3, 2014 at 4:02 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Wed, Dec 03, 2014 at 12:07:59AM -0800, Dave Taht wrote: > > [...] >> https://github.com/dtaht/tinc >> >> I successfully converted tinc to use sendmsg and recvmsg, acquire (at >> least on linux) the TTL/Hoplimit and IP_TOS/IPv6_TCLASS packet fields, > > Windows does not have

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now

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.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

>Updated support for BSD tun/tap devices. It is broken on FreeBSD tun. tcpdump on tun, 09:05:07.458988 IP0 bad-hlen 0 On Sun, Apr 24, 2016 at 8:16 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc version 1.1pre12. Here is > a summary of the changes: > > * Added a "--syslog" option to force logging to syslog even if

Guus: Great job. I would love to see a library version of Tinc for linux. Kind of like an API instead of configuration files. Don't have time right now, but maybe one day I will re-factor the code for library orientation. It would have a single unix socket with a JSON API. I use Tinc on linux Ubuntu 15.10 x64 for all my vpn stuff. It allows Elastic Search and RethinkDB to survive in the

On Fri, Jan 13, 2017 at 12:33 PM, Gary Stainburn <gary at ringways.co.uk> wrote: > > > Also, it was suggested that I use nmcli in a cronjob to re-activate it if > it > drops. I can check to see if it's still active by 'grep'ing the IP > address, > but I don't know the nmcli to re-activate an existing WIFI connection. > > Can anyone help here too,

Thanks Guss, some comments and questions: If you make the yellow nodes ConnectTo all other nodes, and not have > AutoConnect = yes, and the other nodes just have AutoConnect = yes but > no ConnectTo's, then you will get the desired graph. The reason this approach is not desirable is because it fails at automation. It requires us to add a new line of AutoConnect = <new node that

Hi Today our Tinc network saw a network partition when we took one tinc node down. We knew there was a network partition since the graph showed a split. This graph is not very helpful but its what I have at the moment: http://i.imgur.com/XP2PSWc.png - (ignore node labeled ignore, since its a dead node anyways) - node R was shutdown for maintenance - We saw a network split - we brought node R

You could say the same thing about computers in general: I hate them, they automated many tasks in life and took many jobs out of the market!. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer at ngtech.co.il -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Gary Stainburn Sent: Monday, January 16, 2017

Hi All, I see an unexpected beahviour from NetworkManager on CentOS 7.1. Using nmcli tool, I create a bond with two slaves as explained in the Red Hat 7.1 Networking guide. I enable slaves and master; bond works as expected. When I restart NetworkManager, it creates a new bond with the same name but not connected to any device. Two bonds with the same name is confusing for my other monitoring

Hi Guus Following your suggestion we reconfigured our tinc network as follows. Here is a new graph and below is our updated configuration: http://imgur.com/a/n6ksh - 2 Tinc nodes (yellow labels) have a public external IP and port 655 open. They both have ConnectTo's to each other and AutoConnect = yes - The remainder tinc nodes (blue labels) have their tinc.conf set up as follows:

thanks Guus for the quick response. I am using tinc 1.1 if I use AutoConnect = yes then will it automatically remove connections that are no longer in use? What are the security issues with 'AutoConnect = yes' I should be worried? for my use case I might go upto 20 to 30 + tinc hosts connected to single tinc box. as per the doc AutoConnect = yes is experimental, I am using it in our