similar to: tincctl localhost timeout

(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

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

I cant restart my tincd with 'tincctl restart -n $NETNAME' I get the message: 'Could not restart tinc daemon' It works with 'tincctl stop -n NETNAME && tincctl start -n NETNAME' but sometimes the /var/run/tinc.$NETNAME.pid file is missing so I need to kill tinc manually

This may have already been addressed, and I apologize if it has, but here is my issue. I have separated the TINCD log from syslog to isolate the VPN activity. By starting with daemon with the --logfile= switch It seems to work fine except that once log rotation takes place, the daemon does not recreate the log, nor will it write to the new log even if an empty file is put into place. The only

> > Maybe I should allow the reachable keyword for the dump graph command as > well, so you can do: > > tincctl -n <netname> dump reachable graph > > ...and not see any nodes which are unreachable. Is that what you want? This would help since dead nodes do not clutter the visual representation. What are the effects, if any, of dead nodes in the hosts/ dir? Thanks

On Tue, Dec 11, 2018 at 02:36:18PM +0800, Amit Lianson wrote: > 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 >

This approach is more complex than I'd like, but it works even on Solaris, which has neither credential passing nor permissions on the socket itself. --- src/control.c | 82 +++++++++++++++++++++++++++++++++++++++----------- src/control_common.h | 1 + src/tincctl.c | 67 +++++++++++++++++++++++++++++++++-------- src/tincd.c | 2 +- 4 files changed, 120

Hi all, I am trying to setup a configuration of Tinc to allow multiple tincd daemons for a same network (mixing bonding, etc...). I will post my solution later if I found one. This is to get better speeds in multiple gigabit/sec networks. So my question is not about this directly. I would like to know if the "netname" configured on each node, is used somewhere in communications

systemctl enable tincd at NETNAME systemctl: command not found Please help? Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Mon, Feb 8, 2016 at 7:30 AM, Maxim Vorontsov <6012030 at gmail.com> wrote: > systemctl enable tincd at NETNAME for example > > -- > brgds > Max > On Feb 8, 2016 12:15 AM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: >

On Wed, Nov 18, 2015 at 08:25:28AM +0100, Armin Schindler wrote: > But I have a question regarding "Subnet=" possibilities. When I have more than > one Server acting as host for VMs and need to have automatic routing to > all VMs on these servers, can I use tinc to create this routing automatically? > > My idea is to have a script which is started when a VM is

Hi, I'm having some trouble trying to run tinc over GNU httptunnel. On server A I have: /etc/tinc/netname/tinc-up: #!/bin/sh ifconfig $INTERFACE 10.3.0.1 netmask 255.255.0.0 /usr/bin/hts -F localhost:655 8888 /etc/tinc/netname/hosts/A: Address = foo.com Subnet = 10.3.0.0/24 TCPonly = yes /etc/tinc/netname/hosts/B: ConnectTo = A Subnet = 10.4.0.0/24 TCPonly = yes

http://bfy.tw/48zr -- brgds Max On Feb 8, 2016 7:39 AM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: Im running ubuntu 14.04. Regards Yazeed Fataar On Mon, Feb 8, 2016 at 7:35 AM, Yazeed Fataar <yazeedfataar at gmail.com> wrote: systemctl enable tincd at NETNAME systemctl: command not found Please help? Regards Yazeed Fataar On Mon, Feb 8, 2016 at 7:30 AM, Maxim

Hey Saverio, I'd really like the idea of a tinc-1.1-pre package for OpenWRT. I'm currently using tinc-1.1 with an Ed25519-only network, really like the new features and CLI and want to add some OpenWRT routers into the mix. How do you plan to handle things with OpenSSL? tinc-1.1 from git should be able to compile without it (but will then only support the built-in algorithms). Depending

Hi Guus and List, Since the CVE-2013-1428 was announced, I followed the recommendation to update my windows machines to tinc1.1pre7. I've had connectivity issues since upgrading. I've done some debugging but I can't figure out when or why its happening. All machines on the network are running Windows 7 or Windows 2008R2 Enterprise server and tinc 1.1pre7. I've got one master

I found a tincd crash caused by having two "Port" statements in a host's file. I realize this is a bug in an old version of tinc that may be fixed but I spent the past few hours tracking it down so I'm sharing it in hopes others can make use of this info. I was "cleaning" up my Tinc VPN of a collection of OpenWrt routers and tincd started crashing with "Got fatal

There are at least three cases: * Linux: check credentials and pid from client; restrict permissions from server * BSD: check credentials only from client; restrict permissions from server * Solaris: wide open --- configure.in | 4 ++-- src/control.c | 11 ++++++++++- src/control_common.h | 1 + src/tincctl.c | 38 ++++++++++++++++++++++++++++++++++---- 4

Options given on the command line have precedence over configuration from files. This can be useful, for example, for a roaming node, for which 'ConnectTo' and <host>.Address depends on its location. --- This patch is against stable branch. Merging this patch to the 1.1 branch is trivial. I use this patch on my Debian for several weeks. Here is the ifupdown script I use (some

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

Hello! I've setup tinc almost succesfully, but there is one problem remaining with a routing issue. Short Description of the situation : Workstation A (192.168.1.3) | | Tinc Host "50K" (192.168.1.1) | | <Unknown Firewall> + + + <Masq Firewall (Linux)> and Tinc Host "oeoe" (192.168.2.1) | | Workstation B

I've got a test lab set up and im having problems connecting. The first problem is that it takes it a couple of tries before it actually connects the two machines. It complains about bogus data and after trying for a minute or so it connects. kill -USR1 shows that they are connected kill -USR2 only shows the local subnet, not the remote I've tried these versions without any luck: cvs