similar to: [Announcement] Tinc version 1.1pre11 released

On Mon, Jan 05, 2015 at 08:10:48AM -0700, Lance Fredrickson wrote: > Allowing tinc to run without RSA keys is a very big > bonus for us embedded device users. We have a limited amount of nvram space > for storage (tomato firmware). RSA keys took up quite a bit, so being able > to run using only ED25519 makes tinc very appealing for this platform, and > saves tons of space for more

On Mon, Jan 5, 2015 at 7:10 AM, Lance Fredrickson <lancethepants at gmail.com> wrote: > Just wanted to pop in and say I think 1.1pre11 is a really good release. > I have a couple nodes behind a work firewall (sonicwall) over which I have > no control. Previously nodes always fell back to TCP, and the connection > was unusable. Now it always connects over UDP and works like it

We are testing tinc inside Google Compute within a single region and an external region. Two boxes are created as follows: /etc/tinc/test/tinc_test_1 Subnet = 10.240.0.0/16 Subnet = 10.240.0.4/32 Address = 104.154.59.151 /etc/tinc/test/tinc_test_2 Subnet = 10.240.0.0/16 Subnet = 10.240.0.5/32 Address = 104.197.132.141 /etc/tinc/test/tinc.conf Name = $HOST AddressFamily = ipv4 Interface = tun0

Hi, I am playing with LocalDiscovery again and have noticed that I do not see any LocalDiscovery broadcasts anymore. I am using tinc 1.1-pre9 in switch mode and have set LocalDiscovery = yes in tinc.conf. I do not see any broadcasts on any network and I also do not see anything in the debug output. What to do? -nik -- # apt-assassinate --help Usage: apt-assassinate [upstream|maintainer]

Hi, I've got a four site site-to-site tinc mesh working nicely. I have the following systems at two of those sites: 10.a.a.2: Linux box running tinc and DHCP/DNS for site A 10.a.a.dhcp: Windows desktop with a GPU 10.b.b.2: Linux box running tinc and DHCP/DNS for site B 10.b.b.dhcp: Linux laptop I'd like to use Steam In-Home Streaming to game in the laptop streaming from the desktop. The

Hi Guus, Am Freitag, den 25.09.2015, 17:04 +0200 schrieb Guus Sliepen: > Ok, that means by default the UDP NAT timeout on the Cisco is extremely > short. > > > I check the manual of the the Cisco NAT for any TCP/UDP > > timeout settings, but there is no way to modify anything like "keeps > > TCP/UDP connections alive". > > It wouldn't be called

Hello, Is it possible to sign/verify data with the ed25519 keys of a tinc 1.1 host? More specifically, is it possible to sign a file with these keys using openssl? If so, how? If not, what program could be used, and how? Thanks and cheers, @

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

Hi Guus, Am Freitag, den 25.09.2015, 09:36 +0200 schrieb Guus Sliepen: > On Fri, Sep 25, 2015 at 08:41:06AM +0200, Marcus Schopen wrote: > > > I'm running some tinc clients behind a NAT (masquerading, Cisco Router) > > connecting to a host outside on a public IP in a different network. The > > tunnels get unstable every few minutes and I see packet loss when > >

Greetings. I'm new to tinc, but have so far managed to get a couple laptops and a hosted server all connected. They're working as expected, running Tinc 1.1-pre11, which I compiled from source. Next I want to move on to adding my home router into the mix. My routers run OpenWRT. I don't have experience compiling anything from source for OpenWRT, but OpenWRT has Tinc 1.0.25

On Mon, Dec 22, 2014 at 9:30 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > Although the cryptography is now separated from the rest of the logic in > tinc, it is not really replaceable, since only OpenSSL is supported. > However, there is also a new protocol in tinc 1.1, which uses Ed25519 > and ChaCha-Poly1305. The code for those algorithms is included in tinc, > so the

Hi all! Is there any way to make tinc use keys from a keyring or similar? I'm trying to find a way to manage multiple server, making it easier to register a new user to the network. Thanks! -- Martin Iñaki Malerba inakimmalerba at gmail.com inaki at satellogic.com

Hello, did you read this paper? ECDSA Key Extraction from Mobile Devices via Nonintrusive Physical Side Channels https://www.cs.tau.ac.il/~tromer/mobilesc/

Hello I have currently a larger network deployed using 1.1pre11. I have now tried to use 1.1pre14 on a remote system, but I have problems to make it work with compression enabled. It appears that a 1pre14 client cannot talk to a 1.1pre11 server with compression enabled, even though the tunnel is being established with no errors. I have tried both lzo and zlib with various levels, none works.

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

I can confirm that Steam In-Home Streaming does work properly over tinc, for having tried it myself, as long as tinc is configured to route the broadcasts properly, as Guus described. Note that it would be easier to set up tinc nodes on your Windows desktop and Linux laptops, to avoid the additional complication of having to relay broadcast packets between your local networks and the tinc network.