similar to: Tinc looking at wrong directory when given name command

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 folks, I have the following problem: tincd is complaining about a missing name or so but i cannot find any mistake in the configuration. It is similar to all my other tinc nodes. here are the details: # ls -l /etc/tinc/ffnw/ drwxr-xr-x 3 root root 4096 Aug 1 10:43 hosts -rw------- 1 root root 1680 Jul 31 21:54 rsa_key.priv -rw------- 1 root root

This is a follow-up on my previous post: http://www.tinc-vpn.org/pipermail/tinc/2008-September/001759.html After being able to build tinc from source on FC8, I have stumbled upon some configuration issue. My tinc daemon is configured as follows: [root at optiplex060 crc_idb1]# pwd /usr/local/etc/tinc/crc_idb1 [root at optiplex060 crc_idb1]# ls -l total 24 drwxr-xr-x 2 root root 4096 2008-09-15

Executing: ip tuntap add vpndrif mode tun return Keepalived errors show when tincd start: Jan 22 23:41:19 Keepalived_vrrp[1999]: Netlink: filter function error Jan 22 23:41:19 Keepalived_healthcheckers[1998]: Netlink: filter function error Jan 22 23:41:19 systemd-sysctl[23246]: Overwriting earlier assignment of kernel/shmmax in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:41:19

this is what happens when I try to run tincd root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d5 tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 5 Could not open /dev/net/tun: No such file or directory Terminating root at OpenWrt:/etc/tinc/vpn# cat tinc.conf Name = vpn_gw1 Interface = tun0 ConnectTo = vpn_gw2 Cipher = aes-256-cbc Digest = SHA512 Regards Yazeed Fataar

Hi everybody, I've spent last 16 hours trying to get Tinc working on my two almost identical linux boxes. Both are running Debian stable with backported Openssl and self-compiled kernel 2.4.24 with ebtables-patch to enable bridging firewall. Both firewalls have both masquaraded and just bridged nets behind (LAN & DMZ) and they are working perfectly. Now I need to get from my home to

I have tried starting tinc with this command line tincd -n vpn -d5 -D and get this error tincd 1.0.8 (May 16 2007 17:41:21) starting, debug level 5 No value for variable `MIGJAoGBAMnEdtmSs9pe+y0H4aHpQRO0GbJ3DFbEgHoaxsl1sKZ6eTHug klBJxXM' on line 3 while reading config file C:\Program Files\tinc/vpn/hosts/jenks Cannot open host configuration file for myself! Terminating ne1 help?

No parameters using DNS. - tinc.conf content Name = sito1 AddressFamily = ipv4 BindToAddress = <IPPUB>:665 BindToInterface = int Device=/dev/net/tun Interface = vpndrif Mode = router PingInterval = 60 PingTimeout = 5 ProcessPriority = normal - host/sito1 content Address = <IPPUB>:665 Subnet = <IPLOCAL>/<NETMASK> Port = 655 -----BEGIN RSA PUBLIC KEY----- ... -----END

Hello Community, I'm using tinc a while, but now it's the first time i have to install it on my first windows 10 client... bah, i hate windows 10, but anyway... so i just got the latest stable version of tinc and installed it the usual way - so far no problem... tap virtual adapter is present and configured, tinc config is the same as usual, so i just started the daemon... and it

I configured tinc on my little server, but i get this when i try to run it: root@blacky:~# tincd -n venere -d5 -D tincd 1.0.4 (Apr 30 2006 22:53:06) starting, debug level 5 /dev/net/tun is a Linux tun/tap device (tun mode) Executing script tinc-up Listening on :: port 655 Can't bind to 0.0.0.0 port 655/tcp: Address already in use Ready I don't understand what's wrong.. I hope

Forget about tinc. I won't work until you solve issue with your kernel. On Tue, Jan 19, 2016 at 9:45 PM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: > this is what happens when I try to run tincd > > root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d5 > > tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 5 > > Could not open /dev/net/tun: No such file

On 6 September 2017 at 10:47, Guillermo Bisheimer <gbisheimer at bys-control.com.ar> wrote: > Hi Etienne, > > I will try to reproduce the issue, as it not always happen. Just sometimes. Right, that matches my experience. > The TAP driver I have installed in the Tinc folder is version 9.0.0.8 > according to the .inf file included. > > Should I test with driver 9.0.0.9?

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

Hi Guillermo, Yes, I've also noticed there are still issues with resuming from standby on Windows, despite the latest fixes that I wrote (which are included in 1.1pre15). I think my fixes covered some of the causes of tinc misbehaving on standby, but not all of them. Are you able to reproduce the issue reliably? If so, can you please file an issue at https://github.com/gsliepen/tinc/issues

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 =

On Wed, Mar 18, 2015 at 12:10:40PM +0000, Chris Haaser wrote: > I have a tinc mesh consisting of 6 Windows servers. All are configured identically and all but one work without any problems. > On that one server however the tinc service starts, but the connection does not come up (no packets get routed, ping times out). > If I stop and start the service manually, the connection is up in

On Fri, Jan 22, 2016 at 12:50:39PM +0100, Maximilian H. wrote: > I am attempting to run tinc on a raspberry pi (version 1 B HW, 512mb > ram). Tinc starts, but then the tinc daemon crashes. What do you mean by "crashes"? Were there any error messages logged? In doubt, run tinc in the foreground with debugging messages enabled: tincd -n <netname> -d5 -D > # cat

Hey, it's been a while, but I have finally gotten around to testing that. The problem does not seem to be tinc itself, but the TAP adapter. Tinc writes key exchanges and packets and so on into its log, but Windows seems to have forgotten all about the tinc adapter - ipconfig does not show an entry for it, there are no routes for it etc. Just opening the TCP/IP properties in control center

Hello Guus, thank you for your fast reply. Indeed the upgrade to a newer Raspbian image did solve my problem with tinc, I was not aware that there was a new Jessie based version. The current Jessie based Raspbian has tinc 1.0.24 version included, which runs fine, so I did not run tinc with debug messages enabled, since the issue that had caused my tinc crashes in 1.0.19 had probably been fixed.

Hi, Does anyone here have experience running Tinc on NixOS? I'm trying to run Tinc on a NixOS machine, using the similar configuration i had for Ubuntu. My home subnet is 192.168.1.0/24 and my work is 10.16.0.0/24. However, unlike ubuntu, when I start tincd on nixos, and try to 'ifconfig $INTERFACE 192.168.1.10 netmask 255.255.255.0' in my tinc-up, I loose network access on the box