similar to: Tinc at startup Debian 8 Jessie

Hey List, Hey Guus, I would now like to secure my tinc installation. From the man page I see the following. -L I put EXTRA="-L" in /etc/default/tinc and tinc still works. -R Do I have to put libraries and device files under /etc/tinc/NETNAME to build a functional chroot jail ? Currently lsof reports these open resources for tincd: lsof -p $( pgrep tincd ) -n COMMAND PID USER FD

Hello, I am attempting to run tinc on a raspberry pi (version 1 B HW, 512mb ram). Tinc starts, but then the tinc daemon crashes. # cat /etc/issue Raspbian GNU/Linux 7 \n \l # cat /etc/debian_version 7.8 $ apt-cache showpkg tinc Package: tinc Versions: 1.0.19-3 (/var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages) Description Language:

Hello, I have 4 VM's running in Microsoft Azure. They all should have similar configurations except from their tinc ip addresses of course. They run tinc 1.0.24. I have a 5th machine, my development machine. I am able to ping all 4 VM's from my computer when I start tinc from the commandline (tincd -n innomeer -D -d 2). 3 of the computers also work ok when running tinc as a service

Dear Guus, Thanks for the reply. I still run into some issues. Because the repositories host an older release (1.0.24-2.1+b1) of Tinc, I decided to build and install the Tinc 1.0.33 release. On a fresh install of Debian 8 I’ve done the following: cd /tmp/ wget http://tinc-vpn.org/packages/tinc-1.0.33.tar.gz tar xvzf tinc-1.0.33.tar.gz apt-get install libssl-dev zlib1g-dev liblzo2-dev

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? Router: Port 655 forwarded to 192.168.1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall

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 =

yes, I have these in C host file: Subnet=10.10.0.0/24 Subnet=0.0.0.0/1 Subnet=128.0.0.0/1 ## not metioned, because I think is maybe works in same as 0.0.0.0/1 B host file doesn't have 0.0.0.0/1 and 128.0.0.0/1 I only added one route to 5.6.7.8 via B, not via C On Mon, Feb 29, 2016 at 4:40 PM, Maxim Vorontsov <6012030 at gmail.com> wrote: > hi. > > Are you add only

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

Dear All, I am trying to enable router mode of tinc on Windows 7 platform. Although I have enabled the router mode and IP routing in Windows 7 PC (Network A Server). The PC B is still unable to connect the Network A and PC A. But the Network A and PC A is able to communicate each other via tinc. Please help and advise me any incorrect of that. Network A server Real - LAN adapter IP:

Hello, I have faced some problems : 1. With iptables running i can't ping my tincvpn server but as i turn it off i can. i have added all rules mentioned in examples but no success. 2. I want to get internet access on the client which is a win 7 computer using tincVPN but i gained no success either (i can't use bridges because server is a VPS using OpenVZ) so any advice for solving this

Hello, I downloaded tinc 1.0.9 from the site and tried to build on Fedora 10 on i386 (and also x86_64). I get, during the configure phase: checking for zlib.h... yes checking for compress2 in -lz... yes checking for lzo1x_1_compress in -llzo2... no checking for lzo1x_1_compress in -llzo... no configure: error: "lzo libraries not found." but: # rpm -qi lzo Name : lzo

Hi! I'm currently using Tinc to create a VPN between a Linux server, a Windows server, and my local laptop and desktop computers (both running Windows). I picked an IP in the 10.123.1.x range for each server, and added something like "Subnet = 10.123.1.1/32" to each host config file. It's working very well! What I'd like to do now is expose an extra subnet to the VPN. The

Guus: I have been test running the VPN between 2 geographically different clusters on a TINC VPN for a couple of days. How confident are you in the New Protocol in 1.1Pre10? Or should I just play it safe and run the old protocol for production? How long do you think it will take for you to have confidence in the new protocol? When do you think you will gain that confidence? You should be

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,

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

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

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

hi. I suggest you to look at "Automatic Dependencies" in https://www.freedesktop.org/software/systemd/man/systemd.service.html. I think using "After=" and "Recuires=" is more suitable. On Mon, Feb 29, 2016 at 4:48 PM, md at rpzdesign.com <md at rpzdesign.com> wrote: > Hello Tinc'ers: > > I want to use TIncVPN in a systemd Ubuntu environment.

Hi guys, I'm new to tinc and I'm following this tutorial <https://www.digitalocean.com/community/tutorials/how-to-install-tinc-and-set-up-a-basic-vpn-on-ubuntu-14-04> to set up tinc on Ubuntu. Because I wanted to test out the 1.1 branch, I compiled tinc from source. However, when I start tincd, it searches for config files in /usr/local/etc, rather than in /etc as shown in the

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