similar to: Tinc hangs if started with network disconnected

Am 17.02.2017 um 10:59 schrieb Guus Sliepen: > On Fri, Feb 17, 2017 at 09:55:26AM +0100, Sandro Stiller wrote: > >> 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:02 tinc.XXX[403]: Error looking up XXX.net port 2300: Temporary failure in name resolution > [...]

I use systemd or monitd scripts to check if the tinc vpn nodes are pingable and simply restart the tinc daemon if they're not. In my case I have i have a complicated dns setup where at tinc boot time DNS is not yet resolving by the time tinc starts. A simple ping check on the fqdn for the master nodes does the job. On 17 Feb 2017 9:45 am, "Sandro Stiller" <sandro.stiller at

On Fri, Feb 17, 2017 at 09:55:26AM +0100, Sandro Stiller wrote: > 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:02 tinc.XXX[403]: Error looking up XXX.net port 2300: Temporary failure in name resolution [...] > Even if I reconnect the interface, tinc does not continue. > If I

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日

If tincd is started before name resolution comes up, it keeps failing for ever to resolve domain names in Address= host configuration variable after name resolution becomes possible. I think tincd should succeed in resolving domain names after name resolution becomes available.

On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote: > >> If tincd is started before name resolution comes up, it keeps failing >> for ever to resolve domain names in Address= host configuration >> variable after name resolution becomes possible. >> >> I think tincd should

Hello, I am trying 1.1 branch and I experience a segmentation fault upon ALRM signal. This looks like a race condition. I have my tincd daemon instantiated manually in if-up.d/jmuchemb (without IF_TINC_NET) and when if-up.d/tinc runs, it sends a ALRM signal that makes tincd crash. It fails here: Core was generated by `tincd -D -n jmuchemb -d -o ConnectTo srv -o srv.Address 81.x.y.z -o

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

Hi, some questions or wishes.. - i have some nodes with a dynamic ip, how does tinc handle this? are there keep alive pings? - if i want to force a reconnect (for example if an ip changes), i tried kill -ALRM kill -HUP but there were no reconnects, yes the manpage tells it, but a reconnect would be nice. - it is very important to me, that the interface does not go down. - when will tinc 2

Hi! I have compiled and installed tinc 1.1pre5 on a ubuntu machine. With the tinc 1.0.x version that is included in the ubuntu repository I am used to having the config files in /etc/tinc/ and where each vpn has a own directory. The file nets.boot placed in /etc/tinc where I can specify which vpn tunnels that is going to start automatically. How can I get the vpn tunnels to start automatically

Hello everybody, I am using fairly standard setup with tinc version 1.0.31 on Debian 9.1 and Windows Pro 7 clients, however the users complain that tinc is very slow. (they connect to smb shares and transfer files). This is my configuration the client host files only have the keys. http://paste.debian.net/plainh/7a904554 Any advice and options to speed the connections up. What Cypher will

Hi, i try to etablish unencrypted onnection and have in my config: Cipher=aes But this causes the following error: 2018-05-23 12:08:27 tinc.backbone[14746]: tincd 1.0.31 starting, debug level 5 2018-05-23 12:08:27 tinc.backbone[14746]: Got fatal signal 11 (Segmentation fault) 2018-05-23 12:08:27 tinc.backbone[14746]: Trying to re-execute in 5 seconds... I have no idea what i'm doing

On 2017-02-21 16:39, Tomasz Chmielewski wrote: > tshark shows "TCP Spurious Retransmission" for cases where curl is not > able to fetch any data. > > > Both tinc servers are running Ubuntu 16.04 (64 bit) with tinc 1.0.26. > > DC1 is Europe (Hetzner); DC2 is in USA (Amazon AWS). > > > > What's interesting, I don't have these timeouts when I

(Second try to send this. I wonder if the first one gotten eaten by a spam filter; I'll link to patches instead of attaching them.) Here are the tincctl patches I've been working on. They apply to http://www.tinc-vpn.org/svn/tinc/branches/1.1@1545. I intend to commit them once the crypto stuff's fixed. Since they're basically done, I'm emailing them now for review and in case

Hi there, Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the virtual guests don't get their RBD disks made available to them. On openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML is as follows: <domain type='xen' id='7'>   <name>mytwotel-a</name>   <uuid>a56daa5d-c095-49d5-ae1b-00b38353614e</uuid>  

Hello, After upgrading my client system from Debian jessie to Debian stretch (which includes an update from tinc 1.0.24 to tinc 1.0.31), I am having trouble with my VPN: As long as I let tinc connect directly (no "Proxy" configuration option on the client), everything works fine: # tincd -n rath -D -d tincd 1.0.31 starting, debug level 1 /dev/net/tun is a Linux tun/tap device (tun

It's QEMU 4.2.1-lp152.9.6.1. I've tried updating it from the Open Build Service repos but there's too many version conflicts. Marcel On 26/10/20 9:02 pm, Ján Tomko wrote: > On a Friday in 2020, Marcel Juffermans wrote: >> Hi there, >> >> Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >> virtual guests don't get their RBD disks

Migration from 3.6.25-0ubuntu0.12.04.10 to 4.x with passdb backend = ldapsam Hi. I tried to migrate my storage(smb) server to more newer version, but faced with 'segfaults", after(in progress) client authenticating, when samba tries to start a new smbd instance (as i understand). I saw client authentication success, which interrupts in following places: In case with

Sure. ``` [global] workgroup = EXAMPLE server string = dns proxy = no interfaces = eth0 bind interfaces only = yes log file = /var/log/samba/log.%m max log size = 1000 # new options log level = 5 netbios name = FILES #panic action = /usr/share/samba/panic-action %d server role = STANDALONE SERVER local master = no security = user encrypt passwords =

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot