similar to: [Announcement] Tinc version 1.1pre10 released

Tinc newbie here so apologies if this is obvious or has been discussed already; I did search but couldn't find anything. I'm testing tinc 1.1pre10 between a Windows 7 client and Linux server. The Linux machine is on the internet and the Windows machine is on my home network behind NAT. I have successfully configured a Linux client on my home network to communicate with the server

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 there, we're using tinc to mesh together hosts in a public datacenter (instead of using a private VLAN, sort of). So all hosts are reasonably modern; connections are low latency with an available bandwith of around 500Mbit/s or 1Gbit/s (depending on how close they are to each other). Iperf between two nodes directly reports around 940Mbit/s. The CPUs are Intel(R) Core(TM) i7-4770 CPU @

Hi, ? I've recently moved from OpenVPN to Tinc for the mesh setup. Everything works nicely except for some looping packet issues. ? I have 12 servers around the United States, including a couple of moving clients. Every now and then the network is flooded with what I assume is looping packets. 200-300MB of bandwidth per node over 10-45 minutes (normally < 20 KB/s, idle). Most if not all

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 in desperate need of some good advice. I have a tinc network with 16 nodes. It's a star topology where all nodes are connecting to the one node (Node1) that have a static IP. Node 1 accepts incomming connections Node 2 through 16 connects to Node1 One of the nodes (Node5) stopped working a while ago (2 - 3 weeks or so), other than that everything was working fine. Today I

Hello, I think routing could be improved in several ways, at least, there lacks some documentation describing how Tinc routes packets. In order to test Tinc, I setup the following virtual network: - tinc 1.1pre9 with ExperimentalProtocol=yes - use of network namespaces (actually python-nemu[1]) - star topology, where all nodes runs tinc except the center, which I use to filter communications,

Hi, There is still tinc-1.1pre7-1-iphoneos-arm.deb, but it can not connect 1.1pre9 server. Error log shows Peer tries to roll back protocol version to 17.0. Is it possible compile 1.1pre9 for iOS? Thank you. -- @hshh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20131021/d88ae312/attachment.html>

Hi all, I tried Tinc 1.1 from git on 4 nodes, each one in a datacenter. They were able to ping each other, etc... but I had problem with multicast, nothing seemed to pass (all is OK with Tinc 1.0.23). I checked logs and on every nodes I have a lot of: Failed to decrypt and verify packet And Error while decrypting: error:00000000:lib(0):func(0):reason(0) So I get back to 1.0.23 which works

In the past 24 hours multiple persons have contacted me regarding the use of elliptic curve cryptography in tinc 1.1 in light of the suspicion that the NSA might have weakened algorithms and/or elliptic curves published by NIST. The new protocol in tinc 1.1 (SPTPS) uses ECDH and ECDSA to do session key exchange and authentication, in such a way that it has the perfect forward secrecy (PFS)

In the past 24 hours multiple persons have contacted me regarding the use of elliptic curve cryptography in tinc 1.1 in light of the suspicion that the NSA might have weakened algorithms and/or elliptic curves published by NIST. The new protocol in tinc 1.1 (SPTPS) uses ECDH and ECDSA to do session key exchange and authentication, in such a way that it has the perfect forward secrecy (PFS)

https://bugzilla.mindrot.org/show_bug.cgi?id=3170 Bug ID: 3170 Summary: Sometimes sshd responds with different server signature Product: Portable OpenSSH Version: 8.1p1 Hardware: ARM OS: Other Status: NEW Severity: normal Priority: P5 Component: sshd

Hi, I was previously using tinc-1.1pre8 and it worked just fine, but after upgrading to tinc-1.1pre10 my Windows machine is unable to connect to my tinc network, as it fails to complete the handshake. Steps to reproduce: - Set up a Linux node with tinc-1.1pre10 using "tinc init" - Set up a Windows node with tinc-1.1pre10 using "tinc init", and try to make it connect to the

Hi! I tried these two Dockers on Synology nas: https://github.com/JensErat/docker-tinc/ https://github.com/bys-control/docker-tinc For testing i set up a master Windows machine and a client one with also Windows. Connection between of them Works. So no i try to add a Synology NAS, so i can do remote backup. But i cannot set up any connection between the Docker container and master Windows

The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS x86_64 gcc version is 3.4.6 I checked out the llvm-gcc from svn, configured with ../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install --enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking --disable-shared --disable-multilib and get the following error message: make

I try to logon to map using dovecot with SSL required. I get following entries in the log:Mar 20 13:49:30 auth: Debug: Loading modules from directory: /opt/lib/dovecot/modules/auth Mar 20 13:49:30 auth: Debug: Module loaded: /opt/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Mar 20 13:49:30 auth: Debug: Read auth token secret from /opt/var/run/dovecot/auth-token-secret.dat Mar 20

Hi, this commit https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: make[3]: Entering directory '/home/bernd/buildroot/br4/output/build/dovecot-2.2.33.2/src/lib-test' /bin/bash ../../libtool --tag=CC --mode=compile

Hello all, my apologies if I have failed to RTFM, but the PDF manual and google were no help. I am trying to get a simple two node tunnel setup. I have verified that the up scripts bring up the interfaces as they are written; however my gut feeling is that there is something wrong there, but I am not sure exactly what. Misc items: * I have a Port line in horcrux because I ran INIT as a user,

gcc 3.4.x builds LLVM incorrectly on x86_64. gcc 4.0 will get you much farther, but the llvm-test regression tests still have massive problems. Zhongxing Xu wrote: > The machine is a Dell workstation with xeon processors. The OS is RHEL > 4 AS x86_64 > gcc version is 3.4.6 > > I checked out the llvm-gcc from svn, configured with > ../llvm-gcc/configure