similar to: Tinc configuration for PowerPC

Hello, We're suffering from sporadic network blockage(read: unable to ping other nodes) with 1.1-pre17. Before upgrading to the 1.1-pre release, the same network blockage also manifested itself in a pure 1.0.33 network. The log shows that there are a lot of "Got ADD_EDGE from nodeX (192.168.0.1 port 655) which does not match existing entry" and it turns out that the mismatches

Hi Thanks removing the first line "ip tuntap add dev $INTERFACE mode tun" seems to have helped regarding the tun error, however it is not connecting. If I stop the tinc service and then run: root at web3:~# tincd -n gainplus -d -D tincd 1.0.33 starting, debug level 1 /dev/net/tun is a Linux tun/tap device (tun mode) Listening on 10.130.69.123 port 655 Ready Trying to connect to

Dear mailing list, How do I make Tinc auto start on Debian 8 Jessie? I’ve compiled and installed the latest stable release tinc-1.0.33 and I’ve tried this: nano /usr/local/etc/tinc/nets.boot Added the netname of my vpn sudo service tinc start Should work according to: https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04

Hi there, I hope this is the right list. I have been trying to cross compile the LLVM 3.2 for our x86 target by using i586 cross compiler provided by Oselas toolchain (http://www.pengutronix.de/oselas/toolchain/index_de.html). I have cross-compiled multitudes of 3rd party projects before and usually I can apply similar methods to compile the most of them. I have however not been able to figure

I have about 15 nodes running 1.1pre15 connected and running quite well. I don't remember why I installed 1.1preX originally. Possibly because I added a router with custom firmware to the network (Tomato Shibby firmware for my ASUS router) which included 1.1pre14. Now I'm trying to add an Openwrt device and it includes 1.0.33 only. This will replace the Tomato Shibby device with

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

Hi, Are you sure? What happens if you manually telnet/socket 10.130.39.180 nsasia at web3:~$ telnet 10.130.39.180 655 Trying 10.130.39.180... Connected to 10.130.39.180. Escape character is '^]'. 0 db1 17 Connection closed by foreign host. Stopping the service and running debug I get: nsasia at web3:~$ sudo tincd -n gainplus -d5 -D tincd 1.0.33 starting, debug level 5

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

Hello list, I install the tinc 1.0.33 through Homebrew using the below command: brew install tinc And I configure the tinc and want to start it, but the tinc logs shows that utun socket resource busy: /u/l/C/t/1.0.33 ❯❯❯ cat /usr/local/Cellar/tinc/1.0.33/logs/tincd.log 2018-02-26 16:04:15 tinc[60361]: tincd 1.0.33 starting, debug level 0 2018-02-26 16:04:15 tinc[60361]: Could not connect utun

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

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

There are few reasons why I stick to older OSes. In case of FreeBSD its my customized Imunes platform for network simulations... Anyway, back to root problem: gcc -std=gnu99 -DHAVE_CONFIG_H -DCONFDIR=\"/etc\" -DLOCALSTATEDIR=\"/var\" -DFORTIFY_SOURCE=2 -g -O2 -MT tincd.o -MD -MP -MF $depbase.Tpo -c -o tincd.o tincd.c &&\ mv -f $depbase.Tpo $depbase.Po

One of my hosts just rebooted for the first time in ages, and now it won't connect to any other nodes. The log just contains continual "error while decrypting metadata" errors. tincd[8324]: Error while decrypting: error:060A7094:digital envelope routines:EVP_EncryptUpdate:invalid operation tincd[8324]: Error while decrypting metadata from fairfield_gw (yy.yy.yy.yy port 655)

Yes, I am sure but added another broader rule: nsasia at db1:~$ sudo ufw allow from any port 655 proto udp same result for debug example. regards Robert >>> Rafael Wolf <rfwolf at gmail.com> 13-Jun-18 5:32 PM >>> Telnet will only do tcp not udp which tinc works on. Are you sure udp 655 is open? On Wed, Jun 13, 2018, 3:51 AM Robert Horgan <robert

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

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

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?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

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

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