similar to: ./configure parameters

I got the file that was sent to me the other day. Unfortunitly it did not solve my problems. After a lot of hacking I have been able to get release 1.0 to almost compile. I have finally gotten all of the dependancies worked out under OpenBSD 3.2. This next error has me stumped. I can tell that it is looking for a file but have no idea how to create the file. This is the output of the the

Hi tinc list members, There were some problems with Ivo's email adresses (both zarq@iname.com and zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list. ============================================= Hi Ivo, Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere troepjes zoals een tincd scheduler. Dit werkt wat beter, omdat de

Agreed. On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > 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

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

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 succeed in resolving domain names after name > resolution becomes available. The problem is when

THis is the modified script that came with tinc 1.0pre2, and it now uses ifconfig in stead of ip-route. I changed the syntax to be correct (may already have been fixedin a newer version), it now checks whether or not there is a '/dev/tapX' or a '/dev/netlink/tapX' and it checks if there is a module or not. I also added the force_connect and the reload options. Force_connect send

On Sun, Dec 28, 2014 at 12:25:05PM +0100, Sich wrote: > I am curently trying to make some script to auto install tinc 1.0.25 on > linux servers. > I have some problem with the tincd -n -K to generate the key pairs because > he ask me to validate the files used for the keys.... > > I have read the man page but I didn't find how to validate this files > without any

Hello everyone, I am curently trying to make some script to auto install tinc 1.0.25 on linux servers. I have some problem with the tincd -n -K to generate the key pairs because he ask me to validate the files used for the keys.... I have read the man page but I didn't find how to validate this files without any prompt... Is there any switch option for this ? Or any solution ? Thanks a

OCaml has a small runtime which is statically linked into the virt tools (providing things like GC and primitives). Since OCaml 4.03 it has been possible to select variants of this runtime, one of which is compiled with -fPIC, using ‘ocamlopt -runtime-variant _pic’. This has performance implications on i686, but is relatively free on other architectures. Since it (in theory) adds to the

Hello, this morning I apparently had tinc crash on me. In 2 independent tinc clusters of 3 nodes each (but located in the same datacenter), one tinc process crashed in each of the clusters. One process apparently with `status=6/ABRT`, the other with `status=11/SEGV`. Interestingly, they crashed with only 5 minutes difference. The only thing I can come up with that might explain this correlation

I get this error starting tincd: tincd -n vpndr -d5 -D tincd 1.0.26 (Jan 22 2016 19:28:17) starting, debug level 5 /dev/net/tun is a Linux tun/tap device (tun mode) Executing script tinc-up System call `getaddrinfo' failed: Name or service not known Terminating Also keepalived return an error when tincd start. Starting as a daemon. Joutnalctl show this: Jan 22 23:14:49 systemd[1]:

Hello, I have 2 hosts HostA and HostB HostA - 10.38.9.2, kernel 2.4.16, tincd from Debian package HostB - 10.38.9.223, kernel 2.2.17-21mdk, tincd from tarball package. HostA: ------------------------------ /etc/tinc/test4/tinc.conf Name = HostA ConnectTo = HostB TapDevice = /dev/misc/net/tun PrivateKeyFile = /etc/tinc/test4/rsa_key.priv /etc/tinc/test4/hosts/HostA Subnet = 10.0.0.0/8 Port =

Hello List, I have this setup: hosta  <--> hostb  <-->  hostc Hosta and hostc are not directly connected via tinc. But both are conncted via hostb (I called my network tincnet). This works fine I can ssh from hosta to hostc and vice versa without any problems. hostc is in a whitelisted iprange at some service provider. I need hosta to talk to a certain ip (lets call it

Hey List, Hey Guus, I would now like to secure my tinc installation. From the man page I see the following. -L I put EXTRA="-L" in /etc/default/tinc and tinc still works. -R Do I have to put libraries and device files under /etc/tinc/NETNAME to build a functional chroot jail ? Currently lsof reports these open resources for tincd: lsof -p $( pgrep tincd ) -n COMMAND PID USER FD

Hi guys, I have now done the obvious - swapped out the kernel. Upgrading to 4.5.7 fixed the problem! udp UNCONN 0 1408 *:655 *:* users:(("tincd",pid=3242,fd=7)) tcp LISTEN 0 3 *:655 *:* users:(("tincd",pid=3242,fd=6)) Thank you very much for your time. Petr On Fri, Jul 15, 2016 at 7:22 AM,

Hi, Although Im dutch too, Ill write this in english. I got a similar problem then the one on the helpforum. Ill paste my setup first server tincd.conf ---- ListenPort = 8089 MyOwnVPNIP = 192.168.100.1/24 #VpnMask = 255.255.255.0 TapDevice = /dev/tap0 Passphrases=/usr/local/etc/tinc/passphrases server tapdev ---- tap0 Link encap:Ethernet HWaddr FE:FD:C0:A8:6F:01 inet

Hi, Guus Thanks a lot for your suggestion, actually I did something else as below. But one question here is if I don’t add "/sbin/ifconfig myvpn 10.0.0.1 netmask 255.255.255.0”, it seems the crontab wouldn’t trigger tinc-up, and then the ip addr of myvpn wouldn’t be configured, then it will prompt the error of "Can't write to Linux tun/tap device (tun mode) /dev/net/tun:

Hello, trying to start tinc I get the following at the client: Apr 17 16:34:50 otto tincd[10238]: tincd 0.3.3 starting, debug level 1. Apr 17 16:34:50 otto tincd[10238]: Generating 128 bits keys. Apr 17 16:34:50 otto tincd[10238]: Ready: listening on port 655. Apr 17 16:34:50 otto tincd[10238]: Connected to xxx Apr 17 16:34:50 otto tincd[10238]: Memory exhausted; exiting. - on a machine with 80

Good morning, Here is the log, I don't see anything unusual. I took the same tinc binary and tried on two other machines and it works fine - binds to 655/UDP without issues: udp UNCONN 0 0 *:655 *:* users:(("tincd",18872,7)) tcp LISTEN 0 3 *:655 *:*

Hi Etienne, I tried the patch, no change at all. Attached is a new log and also strace log. There is a FD 7 opened (the UDP socket), used and yet "ss -nlptu" doesn't see it. I have a suspicion now there is something wrong with the distro/kernel. As a test: netcat -ul -p600 ss -nlptu | grep netcat gives me no output... Petr On Thu, Jul 14, 2016 at 8:27 PM, Etienne Dechamps