similar to: Service wont start

Hello! I have set up tunnel between a FreeBSD machine and Windows Vista. Tunnel is established, but when I try to ping either end ping fails. I have temporarily switched off firewalls on both machines, no luck. Here is client tinc.conf on Vista: Name = lenovo_client ConnectTo = lenovo_server Interface = tinctap Subnet = 10.20.40.0/24 Sevrer tinc.conf on FreeBSD: Device=/dev/tap0

I am novice using tinc. I followed step by step the sample reported in http://tinc.nl.linux.org/examples/windows-install I have the following in my home (Win XP with tinc-1.0.1-install.exe): ------------------------------------------------------------------------ C:\Program Files\tinc\vpn>type tinc.conf AddressFamily = ipv4 Name = home ConnectTo = office Interface = VPN C:\Program

Hi I''m getting very high CPU usage on idle for an XP SP3 guest, which is doing nothing and is reporting 0% CPU within the guest. xentop - 14:36:29 Xen 3.2-1 10 domains: 1 running, 9 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 4192752k total, 2654960k used, 1537792k free CPUs: 4 @ 3000MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS

I'm probably doing something I'm not supposed to even try, but I'm trying for "proof of concept" before physically setting up a distant network because of logistical issues. Anyway, I have tincd running as a service on two windows machines on the same lan. I'm trying to establish a connection between those two computers on the vpn ip's (10.20.30.1 and 10.20.40.1).

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?

Hi, All Due to some routing rotation purpose, I use crontab to add below info: 0 * * * * echo Subnet = 54.169.128.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp 0 * * * * echo Subnet = 54.169.0.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp 1 * * * * /usr/sbin/tincd -n myvpn -k 1 * * * * /usr/sbin/tincd -n myvpn --debug=3 30 * * * * sed -i '/54.169.128.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp

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

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

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.

I have tinc 1.1pre11 running on various routers and linux cloud servers. On one of the cloud servers, under Ubuntu 12.04, tinc is mysteriously dying once in a while, leaving a dangling PID. I have been unable to track down why it is dying, but it happens infrequently enough that I care less about why it is dying than how to robustly respawn it when it dies. Before I re-invent the wheel, has

You might want to try with https://github.com/gsliepen/tinc/pull/120 - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket

Hi, I have successfully connected a network of about 60 nodes (many of which are virtual machines) with tinc 1.0 but encounter a severe bug when physical connectivity between two major locations is lost and then reconnected. From what I gathered, many nodes attempt to connect to many other nodes, causing 100% CPU load on all nodes, taking down the whole network with no node succeeding connecting

I have a bunch of Debian stretch machines with systemd where I find that tinc starts too early during boot, and fails to work. Typically it is running, but printing out Apr 14 00:53:41 db7 tinc[3077]: Can't write to Linux tun/tap device (tun mode) /dev/net/tun: Input/output error regularly. Unfortunately because it is running systemd does not restart it, even though it's not actually

I?ve been having the same issue with Ubuntu, thankfully we have access to Upstart: ``` start on (local-filesystems and net-device-up IFACE!=lo) stop on stopping network-services author "Mark Lopez" description "Tinc Upstart Job" version "0.1" env network=master respawn exec /usr/sbin/tincd -n "$network" -D --debug=3 --logfile ``` I removed the default

Dear all, I have been successfully running for quite some time a tinc 1.1 network in switch mode. I recently added a new node, that refuses to communicate over UDP. Running "tinc info mynode" from a different box returns: Reachability: directly with TCP It appears that tincd is not listening on UDP port 655 on "mynode". Running "ss -nlptu | grep tincd": tcp

Hello, I have 4 VM's running in Microsoft Azure. They all should have similar configurations except from their tinc ip addresses of course. They run tinc 1.0.24. I have a 5th machine, my development machine. I am able to ping all 4 VM's from my computer when I start tinc from the commandline (tincd -n innomeer -D -d 2). 3 of the computers also work ok when running tinc as a service

Hello, How does tincd determine the subnet(s) of other remote nodes? Does tincd read its copies of the hosts file and parse and follow the subnet information contained in the local files? Or does tincd solely trust the subnet information dynamically advertised by each remote node? In my experimentation, it seems that: a) tincd reads its own subnet(s) from its copy of its own host file, but

(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

First off, thanks to all who have made tinc possible and continue to work developing it. I hope perhaps in time I can become a useful part of this community. :) I'm having an interesting issue with tincctl and was hoping someone could shed some light on it. Everything seems to work correctly when I build for OSX; however on linux and windows builds, I always receive connection

On Mon, Dec 08, 2014 at 11:02:24PM -0500, md at rpzdesign.com wrote: > The self contained example is tricky because I created 4 ip-address on > the eth0 device (192.168.1.30/31/32/33) so I could test a 4 node VPN > that lives entirely within a single server. That's quite hard to do, it's far easier to run four instances of tinc on four different ports on the same machine. >