similar to: [patch] add a debug package to the debian package

Hi! I'm trying to compile tinc-vpn 1.1pre3 on Ubuntu 12.10, but I get this error: checking curses.h usability... no checking curses.h presence... no checking for curses.h... no configure: error: "curses header files not found." (See the attached text file for the output when running ./configure) I have searched on google after this error message but I can't find anything

Thank you guys for a great product. I have successfully setup a VPN between a cloud server and an internal one (details below). However, I am unable to pass traffic from the cloud to the internal machines behind the tunnel. Internal subnet: 172.23.6.0/24 Host Public IP: 50.242.184.132 Host LAN IP: 172.23.6.148 Host VPN IP: 10.9.0.2 Cloud Server IP: 107.170.55.181 Cloud Server

Thanks. I played with it some more, and finally got it working. I am willing to write up a detailed how-to, including screen shots, if you guys are interested. Just tell me in what format you want the write-up. Cheers, From: Daniel J. Grinkevich Sent: Wednesday, July 22, 2015 7:26 AM To: tinc at tinc-vpn.org Subject: RE: Please help debug Windows setup Your port forward needs to

Turns out I needed to masquerade the traffic coming into that INSIDE node. Since I use UFW to manage IPtables, adding this to my /etc/ufw/before.rules and restarting UFW fixed it for me: " -A POSTROUTING -s 10.9.0.0/24 -o eth1 -j MASQUERADE" Very Respectfully, Kismet-Gerald Agbasi IT/Systems Administrator Central Truck Center, Inc. Office: 240-487-3315 Toll Free: 1-800-492-0709

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

Hi I have not tried systemd-coredump yet but I found something strange in my syslog file. Like this message in the en of the log file: tincd[10322]: segfault at 7fffb3180000 ip 00007ff7937f11c2 sp 00007fffb317dd68 error 4 in libc-2.23.so[7ff7936a3000+1c0000] There is more in the attached syslog file. Any clues? Best Regards, Håvard Rabbe > On 14 Feb 2019, at 02:27, Hamish Moffatt

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, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

Hello, For those who run tinc on Debian or Debian-based distributions like Ubuntu and Knoppix, be advised that the following security issue affects tinc as well: http://www.debian.org/security/2008/dsa-1571 In short, if you generated public/private keypairs for tinc between 2006 and May 7th of 2008 on a machine running Debian or a derivative, they may have been generated without a properly

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

Hi - Thanks to Sven-Haegar and Donald, but still having issues setting up with Windows. Machine1 can't ping the VPN address of machine2. Regular IPv4 address for both machines in 192.168.1.xxx range. Router: Forwarding port 655 to 101.102.103.1, UDP and TCP Forwarding port 656 to 101.102.103.2, UDP and TCP Tinc.conf on machine user1 just three lines: Name = vpnuser1 ConnectTo =

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

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

I would like to clarify the email I sent yesterday. There are two ethernet segments in two different cities that I would like to operate as one logical network. Both physical lans have a switch/hub, a gateway with one external IP address that NATs traffic and can port forward tinc ports to the internal debian stable machine (where tinc is run), various client computers ('c' in the

FYI, while rebuilding on Stretch: dpkg -i tinc_1.1~pre17-1.1_amd64.deb A seleccionar pacote anteriormente não seleccionado tinc. (Lendo banco de dados ... 33426 ficheiros e directórios actualmente instalados.) A preparar para desempacotar tinc_1.1~pre17-1.1_amd64.deb ... A descompactar tinc (1.1~pre17-1.1) ... Configurando tinc (1.1~pre17-1.1) ... /var/lib/dpkg/info/tinc.postinst: 10:

The two one-liner patches below are made against the current tinc CVS tree. The debian/rules patch replaces the prefix=blah on the "make install" line with DESTDIR=blah. The prefix is correctly set for /usr, but is overridden with the current make install. DESTDIR is the clean way to relocate the installation into the debian/tmp build dir. The second patch strips the newline off

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

Make sure your router supports nat reflection and has it enabled. On Mon, Jul 13, 2015 at 5:44 PM, Adam Macielinski <adam at macielinski.net> wrote: > Hi, > > > > Thanks to John Wice for helping me with an earlier question. My two PCs > behind the same router are still having problems connecting. Would > appreciate thoughts on what I?m doing wrong? > > > >

Hi, I'm trying to set-up a VPN using Tinc 1.0pre3. When I start tincd I get the following in /var/log/messages. On the machine that listens for incomming connections: > Mar 16 17:23:24 vpn tinc[1168]: tincd 1.0pre3 starting > Mar 16 17:23:24 vpn tinc[1168]: Ready: listening on port 655 On the machine making the connection: > Mar 16 17:16:51 mail tinc[802]: tincd 1.0pre3 starting

i have a switched and bridged tincd node with two addresses, each with a different port. Address = 37.70.156.168 28655 Address = 192.168.2.228 655 i was having trouble reliably connecting to it / thru it and noticed that a log from a remote tincd node indicated it may have mixed up the ports. It doesn't appear to use the 28655 port that would be needed for remote access. Before i