similar to: tinc initialization (in both Red Hat and Debian families)

On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: > On Thu, Sep 24, 2015 at 05:51:30PM +0300, R?zvan Sandu wrote: > > > IMHO, we need: > > > > 1. A proper tinc.service file, included by default (prepackaged) in the > > stock .deb and .rpm packages in Fedora, Debian, Ubuntu, CentOS, etc. > > > > By "proper" I mean it will start

La 25.09.2015 13:00, tinc-request at tinc-vpn.org a scris: > Unfortunately, this is not something that maps well to systemd. It would > require a systemd to run a script that parses the sysconfig file and > start all the tinc daemons. Systemd will then put all those daemons in > the same control group and won't recognize something is wrong if only > one of the daemons fail. So

Hello again, >From the point of view of a Red Hat *user*, the standardised way of doing things would be to have an /etc/sysconfig/tinc file containing something like: NETWORKS="vpn1 vpn2 vpn3" (one or more names separated by spaces) At initialization, each name should launch a separate tinc instance (a different VPN) tinc service should not start until the user adds at least

On Thu, Sep 24, 2015 at 05:51:30PM +0300, R?zvan Sandu wrote: > Taking into account that both Red Hat and Debian (8.x) families now use > systemd, there is, IMHO, one small. but important correction to be done: > tinc's initialization. > > IMHO, we need: > > 1. A proper tinc.service file, included by default (prepackaged) in the > stock .deb and .rpm packages in

Would it not make more sense to have this on packagers responsiblity instead like you were saying adding it into the upstream repo. Maybe have a secondary repo that people can contribute to for distribution specific files and install scripts. On 24 September 2015 at 21:30, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: >

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

Hello, Please tell me if it's possible to use tinc together with OSPF (instead of static routes in LAN). By OSPF I mean Quagga's GNU/Linux daemon. Namely, I have a group of LANs (private 192.168.x.0/24 each). Each LAN has a GNU/Linux default gateway, 192.168.x.1, that also connects to the Internet via a public IP address (does NAT and firewall for the LAN "behind" it). tinc

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

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

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

Hello everyone, I am curently trying to make some script to auto install tinc 1.0.25 on linux servers. I have some problem with the tincd -n -K to generate the key pairs because he ask me to validate the files used for the keys.... I have read the man page but I didn't find how to validate this files without any prompt... Is there any switch option for this ? Or any solution ? Thanks a

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

(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

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:01 tinc.XXX[403]: tincd 1.0.31 starting, debug level 5 2017-02-13 11:34:01 tinc.XXX[403]: /dev/net/tun is a Linux tun/tap device (tun mode) 2017-02-13 11:34:01 tinc.XXX[403]: Executing script tinc-up 2017-02-13 11:34:02 tinc.XXX[403]: Listening on 0.0.0.0 port

Still experimenting with the automesh function. In the midst of that, I encountered a new problem. Of the 6 linux boxes in my tinc VPN, 3 were RedHat 9, 1 was Suse 9 Pro, 1 was Fedora Core 1, and one was RedHat 8.0. All was well. They were running a mix of the static binary and locally compiled-from-source binaries. I updated two of the RedHat 9 boxes to Fedora Core 1, about 3 days

Hi, some questions or wishes.. - i have some nodes with a dynamic ip, how does tinc handle this? are there keep alive pings? - if i want to force a reconnect (for example if an ip changes), i tried kill -ALRM kill -HUP but there were no reconnects, yes the manpage tells it, but a reconnect would be nice. - it is very important to me, that the interface does not go down. - when will tinc 2

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

Hello, I have two servers (A and B) in separate locations. Both are connected together via two tinc switches to provide two subnets on both servers. This works pretty good. I can start my VMs on any server connected to one of those bridges without changing any routes. The subnets hosted on both servers (each in a bridge) are 172.16.10.0/24 (mainly on A) and 172.16.11.0/24 (mainly on B) Now I

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 like half a second. If I start tinc on the command line, it works every time.