similar to: New Protocol

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.

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: The documentation does not have the following use cases very well defined or described. I have created a PDF file that Tinc-VPN can use to public and I would be happy to make more PDF files for usage with the examples on the web site. There are 2 pages in the PDF file attached, the first page is a production setup and the page is a test setup wholly contained within a single server. IS

On Mon, Feb 29, 2016 at 07:48:45AM -0600, md at rpzdesign.com wrote: > I want to use TIncVPN in a systemd Ubuntu environment. > > But I want other services to run AFTER tinc has started running and has its > tun0 device initialized and ready. > > Does anybody have a suggestion on what I put into the service files so that > they are ExecStart after Tinc has come up at boot

Tried to Build Tinc. Linker was confused, Makefile lacking reference to -ltinfo I guess. FYI. root at rpzcentos tinc-1.1pre10]# make make all-recursive make[1]: Entering directory `/adev/tinc-1.1pre10' Making all in m4 make[2]: Entering directory `/adev/tinc-1.1pre10/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/adev/tinc-1.1pre10/m4' Making all in

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 =

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

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:

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gus: Is it even worth my time to use any of the 1.1.X versions and only use the 1.0.24 Stable version for a VPN deployment today? Or is the 1.10pre 95% stable and only lacking UDP forwarding? Please do not be optimistic, I My use case is one where I have several servers connected by TCP/UDP and all servers are master, there is no hub and no

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

Window allows one to specify a DNS domain name and DNS server for a particular interface. So all DNS queries of your tinc interface are sent to a particular dns server. For instance windows tinc clients can use a particular dns server on a private LAN available only to clients inside that NAT or tinc clients. NetworkManager allows you to specify the same, but the tinc interface does not show up

On Sun, Dec 07, 2014 at 04:33:49PM +0100, Guus Sliepen wrote: > Hm, on Debian it works fine, OTOH the command "libncurses5-config > --libs" does tell me to link with -ltinfo. I'll see if I can add that > to the autoconf script. On CentOS 7 tinc 1.1 compiles without problems. Also, both on Debian and CentOS "pkg-config --libs ncurses" only prints

On Fri, Dec 12, 2014 at 02:21:08AM -0500, md at rpzdesign.com wrote: > Oops, I got it to work only after putting the WAN on port 656 so it > did not interfere with port 655 for the LAN. You should not need to have two tinc daemons just because you have a WAN and a LAN interface. By default (ie, if you don't specify BindToAddress and/or BindToInterface), tinc listens on all interfaces,

Hello tincers, I run a small tinc mesh using version 1.1pre10 on mostly linux (debian) hosts. In the past, I was able to successfully join my windows machine to the tinc network, when I was running an earlier version of tinc (throughout the mesh). However, with 1.1pre10, I have had no success. Is this a known error, a misconfiguration on my part, or some other issue? I currently have no tinc-up

On Tue, Mar 01, 2016 at 04:31:13AM -0600, md at rpzdesign.com wrote: > Where do I get information about the details of not needing a tinc-up script > anymore? (/etc/network/interfaces) You can just use the normal /etc/network/interfaces way of configuring the interface, like this: iface vpn inet manual address 192.168.1.1 netmask 255.255.255.0 tinc-net <netname> > Also,

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