similar to: The reconnect timer can be adjusted in 1.0.31?

Hi, Guus I noticed th default reconnect for the first time is 5s, if failed the timer will be increase, I would like to know if this timer can be adjusted? The Max Timeout you mentioned seems not exactly the one, from the description below, it looks to me it is the total time for connect to be re-established, if not it trying other tinc daemon? Different tinc deamons have nothing related to

Thanks. >From the document, the default looks 900s. And let's say tinc connected to A, B, C; What if the connection to A failed(To B and C are fine), and tried many times until the last try which wait the Max Timeout, then tinc will not try again to connect A, right?(And when the Max Timeout for connection to A will be reset?) Guus Sliepen <guus at tinc-vpn.org>于2017年8月12日

On Thu, Aug 10, 2017 at 09:37:13PM +0800, Bright Zhao wrote: > When the meta connection get lost, it’ll be reconnect like below: > Trying to re-establish outgoing connection in 5 seconds, and if it’s failed, then the timer will be increased for another try. > > My question is, how to adjust the reconnect timer, in some cases, the reconnect delay for a while(increase to something

On Sat, Aug 12, 2017 at 09:17:10AM +0000, Bright Zhao wrote: > I noticed th default reconnect for the first time is 5s, if failed the > timer will be increase, I would like to know if this timer can be adjusted? No, this cannot be adjusted. > The Max Timeout you mentioned seems not exactly the one, from the > description below, it looks to me it is the total time for connect to be

Hi I've compiled Tinc 1.0.2 from source but I'm having trouble. Not only am I having disconnections all the time (could be a network issue however) but even worse, Tinc is ignoring my MaxTimeout = 60 and is waiting longer and longer and longer (logfile shows it at 120 seconds). Is this a bug or have i misconfigured anything? best regards Marco Amrein Dec 5 11:25:12 frank

Le 10/02/2015 14:23, Guus Sliepen a ?crit : > On Tue, Feb 10, 2015 at 08:54:16AM +0800, GG wrote: > >> [...] >> >> How it possible to make tincd restart if the connexion can't be made after >> ... 30 secondes? and never wait more than 30 secondes. > > Just add the following line to tinc.conf: > > MaxTimeout = 30 > Thanks a lot. I will let you know

Hi! I'm in China now and my Internet connexion is very bad. I ever use the best ADSL provider that I can have. In some case (often), the connexion is lost. At the first time, tincd will wait few time and retry. But, this delay is increased if the connexion can't be made... so, it's quicker to kill tincd and restart it. How it possible to make tincd restart if the connexion

Hello! I'd like to use PriorityInheritance option, despite it is still experimental. (Why it could be experimental, when it looks quite simple feature, no?) But this option doesn't change the TOS field of outgoing UDP packet. I just do tcpdump on outgoing interface from vty1: $ sudo tcpdump -vni eth0 udp dst port 655 And from vty2 I do ping with setting of tos field to EF(0xb8). $

Hi Guys, I have been using tinc in a linux environment, which has always been working fine. Recently I encountered an issue that tinc process exits(or crash?) when internet is down. What could be the cause of it? Is there a timeout mechanism inside tinc code that it will exit after failing to bring up tun/tap interface for a long period? The internet has been down for several days. I am trying

Hi, We have a tinc network of about ~200 hosts and in the full mesh configuration we've had a lot of problems with the edge propagation storms taking the entire network down. Recently we had a setup with a small number of "hubs" to which all the other nodes connected to, which limited the number of meta connections, but that didn't help much with the edge propagation issues.

Hi, We set up tinc tunnels over 3G when the connection becomes available. It is a mobile environment so connections come and go frequently. We send tinc an ALRM signal to retry a connection, but somehow this fails once in a while. Is there a way to influence the retry interval for connections that are down and the interval increment? We would like to be able to set this to 1 minute after ALRM.

I've noticed some inconsistent performance with some of my tunnels and thought I would take some of the spare free time I have over the holidays to try to figure out what the cause of that may be. My environment in this case is my home LAN. Please forgive my use of the terms "server" and "client" in this email, I only use these terms to simply explanation. I statically

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

On my system, tinc is started on bootup. If the Network cable is not connected, tincd hangs forever after these messages: 2017-02-13 11:34:01 tinc.XXX[403]: tincd 1.0.31 starting, debug level 5 2017-02-13 11:34:01 tinc.XXX[403]: /dev/net/tun is a Linux tun/tap device (tun mode) 2017-02-13 11:34:01 tinc.XXX[403]: Executing script tinc-up 2017-02-13 11:34:02 tinc.XXX[403]: Listening on 0.0.0.0 port

I'm been experiencing a very very odd problem for the past several weeks and am throwing it out in case someone can shed some light on it for me. There is a single box on our tinc mesh which can be pinged from all hosts, but cannot ping any. It is not limited to ping, the box cannot communicate over tinc. tinc is running in router mode for this mesh. ~30 other nodes function normally,

--- doc/tinc.conf.5.in | 3 +++ src/linux/device.c | 7 +++++++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/doc/tinc.conf.5.in b/doc/tinc.conf.5.in index 2bfd5fe..01f7f81 100644 --- a/doc/tinc.conf.5.in +++ b/doc/tinc.conf.5.in @@ -255,6 +255,9 @@ a lookup if your DNS server is not responding. This does not affect resolving hostnames to IP addresses from the host

Hi maximilian, the problem of MUTproble is happened here for me, and the patch is working fine, should be helpful anyway. which mode you used? router, switch or HUB? thanks PHB -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20200402/fb3597ed/attachment.html>

Hi I have built a few networks with tinc and feel quite familiar with it. But now I have got a scenario where I can't clearly figure out how things work with tinc: I have two nodes, both of them are in different private networks and visible only to different servers, which have got an internal and an external IP. So my topology looks like this: [n1]->[host1]<-->[host2]<-[n2]

On Mon, Feb 09, 2015 at 10:57:05AM +0100, Florian Klink wrote: > I have some hosts which converted to systemd-networkd (which doesn't > support hooks by now), and most of the time, tinc simply won't come up > after bootup (or won't be able to reconnect when the network is > changed), which is really ugly. > > Having a local dns in front is somewhat hacky, I'd

Hello, I am experiencing some weird problems in a setup with tinc where communication between the 'server' and the 'clients' occur over 3g connections. Let me describe briefly the setup: - The server, on a public IP, runs tinc 1.0.8, in router mode, and the whole setup uses one VPN network. All client's VPN addresses are on the same subnet, and each client has a seperate