similar to: Sometimes can't establish tinc connection due to authentication timeout?

Hi, Guus I encounter the below log messages that after tinc run for a while, it seems box1 begin to buffer traffic to abc, and box1 is behind a firewall to connect abc from firewall’s inside to outside, and abc is on the public internet. Normally the major traffic is actually from abc to box(download direction), but not sure how this happens, and could you suggest something we can avoid this to

Hello Guus. I've reading mailing list archives threads about it at http://www.tinc-vpn.org/pipermail/tinc/2011-July/thread.html#2757 and http://rutschle.net/pipermail/sslh/2011-July/thread.html and now trying to hide tinc server behind sslh multiplexer but without luck. First of all directly it works fine. Initiator (instance of tincd with ConnectTo statement) successfully establishes

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

Hello, I'm trying to use tinc to establish a vpn between two linux boxes. The keys are shared and the connection gets established, but I can't seem to ping either side. One side is strictly a server for the client to connect to. It has a public IP, and the private IP subnet which it's trying to "share" to the client. It's a pretty simple and straight forward setup.

Hi there, We use tincd over VSAT connections, and if the contract has been reduced to a bare minimum -and- the ship is moving, latency reaches 2 - 5 seconds (yes, seconds). Generally this is not a problem if you are patient (and most smart phones are), but tincd is slightly too fast in deciding that it is not going to work. We also use the tinc connection to check whether any traffic is possible.

Good afternoon. I've tried making use of tinc inside of a Windows XP box, mostly to test whether it is at all possible to use a JScript/VBScript file (Windows Scripting Host). However, upon executing tinc.exe (this also happens with tincd.exe), an error pops up, telling about a method that is not available in KERNEL32.DLL. Apparently, this method, InitOnceExecuteOnce, is only available from

Hi, I see there’re two configuration in tinc: In main configuration: BindToAddress = <address> [<port>] In host configuration: Port = <port> So, let’s say on svr1 /etc/tinc/test/tinc.conf: BindToAddress = ip_addr p1 BindToAddress = ip_addr p2 /etc/tinc/test/hosts/svr1: Port = p1 On the client side c1 /etc/tinc/test/tinc.conf: ConnectTo = svr1 /etc/tinc/test/hosts/svr1:

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]:

>> We use tincd over VSAT connections, and if the contract has been reduced to a bare minimum -and- the ship is moving, latency reaches 2 - 5 seconds (yes, seconds). Generally this is not a problem if you are patient (and most smart phones are), but tincd is slightly too fast in deciding that it is not going to work. We also use the tinc connection to check whether any traffic is possible.

On Wed, Mar 29, 2017 at 10:14:30AM +0200, Nick Hibma wrote: > We use tincd over VSAT connections, and if the contract has been reduced to a bare minimum -and- the ship is moving, latency reaches 2 - 5 seconds (yes, seconds). Generally this is not a problem if you are patient (and most smart phones are), but tincd is slightly too fast in deciding that it is not going to work. We also use the

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 =

I installed a cross-compiler for PowerPC 603e (OSELAS-Toolchain from Pengutronix) on an i686 machine with Fedora 24. All steps for compiling tinc (https://www.tinc-vpn.org/examples/cross-compiling-windows-binary/) worked successfully. After compiling I verified the file type (file tincd) obtaining: tincd: ELF 32-bit MSB shared object, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked,

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

I agree with the in-effective of TCP transmission, but I wonder if the the UDP packet is dropped, the tinc VPN itself wouldn’t retransmit, and if the upper level application doesn’t handle the packet loss well, will this be the problem? Or the upper level application have very limited tolerance to packet loss(like RDP application, I guess if the packet loss go to certain threshold, the connection

Hi Daniel, Yes, thanks and I should have mentioned that I am using pretty much the same thing you suggested on my routers, but for whatever reason couldn?t get that approach working on the linux box in question. Mark, Thanks for the upstart script. I had tried to do the same myself but couldn?t get my upstart script to work right. I was missing the ?-D? flag in my script. Added that and now

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 > [...]

Let’s say, tinc A node server LAN-1(single internet circuit), tinc B node and tinc C node are both serve LAN-2.(two internet circuits) Normally, we can only set tinc A to connect to either B or C, and then the other set as backup. But in some circumstances, we would like to combine the internet pipe of both two circuits, so that the tunnel traffic can have a better bandwidth. If that’s the

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

net-misc/tinc-1.0.12 works for me on amd64 1. there is an official ebuild for 1.0.11, but not for 1.0.12 yet 2. my -r1 contains changed initscript 'tincd.lo' to be used like net.lo by ln -s tincd.lo tincd.vpn_name and then calling tincd.vpn_name to start/stop 3. it is in my overlay together with latest versions of some other software:

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