search for: devicestandby

...inc always tries to keep at least three meta-connections open. * The new protocol now uses UDP much more often. * Tinc "del" and "get" commands now return a non-zero exit code when they don't find the requested variable. * Updated documentation. * Added a "DeviceStandby" option to defer running tinc-up until a working connection is made, and which on Windows will also change the network interface link status accordingly. * Tinc now tells the resolver to reload /etc/resolv.conf when it receives SIGALRM. * Improved error messages and event loop han...

...inc always tries to keep at least three meta-connections open. * The new protocol now uses UDP much more often. * Tinc "del" and "get" commands now return a non-zero exit code when they don't find the requested variable. * Updated documentation. * Added a "DeviceStandby" option to defer running tinc-up until a working connection is made, and which on Windows will also change the network interface link status accordingly. * Tinc now tells the resolver to reload /etc/resolv.conf when it receives SIGALRM. * Improved error messages and event loop han...

...onfiguration files (like Ed25519PublicKey within it or Compression) after creation, unless you can manage all remote nodes as well because key exchange does not transfer the updated hosts file. Inviting a new node with different name for the new key is required. tinc.conf of A AddressFamily = ipv4 DeviceStandby = no Interface = tap0 Mode = switch Name = a ProcessPriority = high LogLevel = 3 AutoConnect = no tinc.conf of remote nodes (B/C/...) AddressFamily = ipv4 LocalDiscovery = yes Mode = switch Name = b ConnectTo = a LogLevel = 3

...P 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 subnet-up script is run before tinc-up). I notice that tinc runs the subnet-up script for the local subnet immediately after the tinc-up script, with $REMOTEADDRESS empty, so I tried putting some of the interface configuration there instead. This seemed to work fin...

...lush....would block messages. All hosts are running latest tinc-1.0 stable. The server is configured as a bridge and is relaying multicasts continuously. Below is the server configuration. Name = tserver AddressFamily = ipv4 BindToAddress = 192.168.21.254 30000 KeyExpire = 28800 ReplayWindow = 0 DeviceStandby = no DeviceType = tap DirectOnly = yes Mode = hub ProcessPriority = high ClampMSS = yes Cipher = none Digest = none MACLength = 0 PMTUDiscovery = yes I have taken out what I believe is performance sapping options in an effort to boost performance. All clients (Windows 7) configuration is identica...

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