search for: kalrm

....0.31. > > Does it not log anything anymore after those messages? Or does it > continue giving the "Error looking up..." message periodically? It stops working completely. > > In the first case, try sending tinc the ALRM and/or HUP signal (tincd -n > <netname> -kALRM). This should cause tinc to retry outgoing connections > immediately. After that, it continues trying. I think, I found the cause of the problem: Is tinc using a monotonic / steady clock for timeouts or is it using the system time? If the system time is set during boot using the RTC (after th...

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

...ion. > It's the same problem with version 1.0.28 and 1.0.31. Does it not log anything anymore after those messages? Or does it continue giving the "Error looking up..." message periodically? In the first case, try sending tinc the ALRM and/or HUP signal (tincd -n <netname> -kALRM). This should cause tinc to retry outgoing connections immediately. If that doesn't help, it could be that libc doesn't reload /etc/resolv.conf after the network connection came up. Tinc has code to force glibc to reload that file every time it wants to do a hostname lookup. Did you compil...

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日