search for: maxtimeout

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 tinc.vpn[6620]: Trying to re-establish outgoing connection in 115 seconds Dec 5 11:27:09 frank tinc.vpn[6620]: Try...

...s 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 each other, why try other daemon? MaxTimeout = <seconds> (900) This is the maximum delay before trying to reconnect to other tinc daemons. Guus Sliepen <guus at tinc-vpn.org>于2017年8月12日 周六下午2:41写道： > On Thu, Aug 10, 2017 at 09:37:13PM +0800, Bright Zhao wrote: > > > When the meta connection get lost, it’ll be reco...

...> 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 how this can do for connexion. This should be on FAQ, because I can't found it when I searchid this config. May be too few searching... See you GG

Hi, 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 longer) will be beneficial for the unstable connection.

...======================== Central Node (10.0.0.1) configurations: ============================================================================== --------------------------------------- tinc.conf --------------------------------------- Name=central Mode=router AddressFamily=any BindToInterface=eth0 MaxTimeout=333 KeyExpire=888 PingInterval=88 PingTimeout=4 #Forwarding=kernel TunnelServer=yes --------------------------------------- hosts/central --------------------------------------- Compression=10 PMTUDiscovery=yes Subnet=10.0.0.0/28 Subnet=0.0.0.0/0#10 ==============================================...

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

...olowing from tcpdump: IP(tos 0x0, ttl 64, id 0, offset 0, flags[DF], proto UDP(17), length 136 So the TOS field doesn't take the value from TOS of encapsulated packet. Is this a bug or I do something wrong? Thank you in advance. === $ tinc.conf $ Name = eiger Interface = tap1 Mode = switch MaxTimeout = 120 PriorityInheritance = yes ConnectTo = pika ===

...er daemon? > > Timeouts are handled separately for each ConnectTo. So if you have > multiple ConnectTo's, they will all be tried in parallel, and each has > its own timeout that starts at 5 seconds, gets incremented by 5 every > time it fails, but it will never increase it beyond MaxTimeout. > > So if you have a connection to A that is failing, and after a while the > timeout for it is 300 seconds, and if a working connection to B > suddenly fails, then tinc will try to reconnect to B after 5 seconds. > > -- > Met vriendelijke groet / with kind regards, >...

...24 as it's the latest in the repos, but we did also test it with 1.0.30, but it made no difference. The common settings for every host in tinc.conf (just BindToAddress and Name are host specific): AddressFamily = ipv4 Forwarding = internal DirectOnly = no Device = /dev/net/tun MinTimeout = 2 MaxTimeout = 300 PingTimeout = 90 TunnelServer = yes Broadcast = no hosts configurations: Port = 655 Compression = 0 Cipher = aes-128-cbc IndirectData = no Thanks! Tuomas Silen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc-devel...

..."); ! printf("Mode: %s Verbose: %s Tracing: %s\n", mode->m_mode, ! verbose ? "on" : "off", trace ? "on" : "off"); printf("Rexmt-interval: %d seconds, Max-timeout: %d seconds\n", rexmtval, maxtimeout); } --- 710,717 ---- printf("Connected to %s.\n", hostname); else printf("Not connected.\n"); ! printf("Mode: %s Verbose: %s Tracing: %s Literal: %s\n", mode->m_mode, ! verbose ? "on" : "of...

..."); ! printf("Mode: %s Verbose: %s Tracing: %s\n", mode->m_mode, ! verbose ? "on" : "off", trace ? "on" : "off"); printf("Rexmt-interval: %d seconds, Max-timeout: %d seconds\n", rexmtval, maxtimeout); } --- 723,730 ---- printf("Connected to %s.\n", hostname); else printf("Not connected.\n"); ! printf("Mode: %s Verbose: %s Tracing: %s Literal: %s\n", mode->m_mode, ! verbose ? "on" : "of...

...bug.cgi?id=1800195 Signed-off-by: Salvatore Bonaccorso <carnil at debian.org> --- tftp/tftp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tftp/tftp.c b/tftp/tftp.c index d15da2200ef8..d067f9699778 100644 --- a/tftp/tftp.c +++ b/tftp/tftp.c @@ -48,7 +48,7 @@ extern int maxtimeout; #define PKTSIZE SEGSIZE+4 char ackbuf[PKTSIZE]; int timeout; -sigjmp_buf toplevel; +extern sigjmp_buf toplevel; sigjmp_buf timeoutbuf; static void nak(int, const char *); -- 2.20.1

...bug.cgi?id=1800195 Signed-off-by: Salvatore Bonaccorso <carnil at debian.org> --- tftp/tftp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tftp/tftp.c b/tftp/tftp.c index d15da2200ef8..d067f9699778 100644 --- a/tftp/tftp.c +++ b/tftp/tftp.c @@ -48,7 +48,7 @@ extern int maxtimeout; #define PKTSIZE SEGSIZE+4 char ackbuf[PKTSIZE]; int timeout; -sigjmp_buf toplevel; +extern sigjmp_buf toplevel; sigjmp_buf timeoutbuf; static void nak(int, const char *); -- 2.20.1

...s 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 can't be made after > ... 30 secondes? and never wait more than 30 secondes. Just add the following line to tinc.conf: MaxTimeout = 30 -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://www.tinc-vpn...

> Le 10/02/2015 14:23, Guus Sliepen a ?crit : >> Just add the following line to tinc.conf: >> >> MaxTimeout = 30 On Mon, Feb 9, 2015 at 11:25 PM, GG <guolang at greboca.org> wrote: > This should be on FAQ, because I can't found it when I searchid this config. > May be too few searching... It is pretty easy to find. Go to: http://tinc-vpn.org/ Then click on: documentation manual (HTML...

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

...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 longer) will be beneficial for the unstable connection. You can set the maximum time that tinc will wait before reconnecting by setting the MaxTimeout option in tinc.conf. The default is 300 seconds. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: no...

...each other, why try other daemon? Timeouts are handled separately for each ConnectTo. So if you have multiple ConnectTo's, they will all be tried in parallel, and each has its own timeout that starts at 5 seconds, gets incremented by 5 every time it fails, but it will never increase it beyond MaxTimeout. So if you have a connection to A that is failing, and after a while the timeout for it is 300 seconds, and if a working connection to B suddenly fails, then tinc will try to reconnect to B after 5 seconds. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org...

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