search for: devicestandbi

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

Hello tinc users, I have been trying to work out how key exchange/hosts file sharing in tinc 1.1 works. My topology is straightforward, a "super" always-online node A to which remote nodes B, C, ... (and so on) ConnectTo = A, to discover each other via AutoConnect (that's on by default in tinc 1.1pre17) Only super A has host files with Ed25519 keys for every node on the network.

Currently I have the local tinc node's VPN IP in both the tinc-up script as well as in its hosts/$NODE file Subnet setting. Can this be avoided, to simplify deployment? Actually I am currently using a DNS lookup in the tinc-up script to get the local VPN IP ($NODE.myvpndomain), but this fails if DNS isn't ready when tinc-up is run. (DeviceStandby=yes fixes this, but then the

The server has a 1G symmetrical fibre line. It has been speedtested to various local servers to be close to 800-900M. When there is only a single client, there isn't much problem and as soon as the connection is made, the ping time through to tunnel is a respectable 30ms. As soon as a few more clients are connected, ping time degrades to hundreds and sometimes seconds and with dropped packets.

We run tinc in a linux environment in which it sits there waiting for connections from the clients. All clients are configured to only have one ConnectTo which points to this server. We're seeing in the server log that as soon as a client's connection is activated, a whole bunch of "Flushing x bytes to that host would block" is logged and the whole vpn is bogged down and has

I have a bunch of Debian stretch machines with systemd where I find that tinc starts too early during boot, and fails to work. Typically it is running, but printing out Apr 14 00:53:41 db7 tinc[3077]: Can't write to Linux tun/tap device (tun mode) /dev/net/tun: Input/output error regularly. Unfortunately because it is running systemd does not restart it, even though it's not actually