search for: rsandu2007

Hello, Please excuse my (probably newbie) question, but: Since RouterOS, MikroTik's proprietary OS, is largely based on GNU/Linux, anyone knows a way to run tinc on a MikroTik device? This would be in order to make an (imposed, no choice given...) MikroTik device (say the B1100AHX4 router) to participate in a tinc mesh, in interoperation with GNU/Linux machines. Please see:

...- supposing I have two different tunnels to the same destination, I can't imagine a way to route traffic between them (since in tinc routing is fully automatic and elegant, point-top-point L2TP/IPSec is very inflexible) Best regards, Răzvan În vin., 16 nov. 2018 la 12:32, Răzvan Sandu <rsandu2007 at gmail.com> a scris: > Hello, > > Please excuse my (probably newbie) question, but: > > Since RouterOS, MikroTik's proprietary OS, is largely based on GNU/Linux, > anyone knows a way to run tinc on a MikroTik device? > > This would be in order to make an (imposed,...

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

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

Hello all, For your information, below are some "bugs" (possible optimizations?), all related, for tinc's initialization in systemd. Since both RedHat and Debian recent distros have switched to systemd,**please** make sure that a solid initialization mechanism is included in precompiled .rpm and .deb packages (CentOS, Debian, Fedora, etc.)

Guus Sliepen wrote: > Yes, you can do that as well. Note that in router mode, you have to then > provide two Subnets in each host config file; one for that node's > 192.168.x.* address, and another for its 10.* address range. Thank you, it works great! Răzvan -------------- partea următoare -------------- Un ataşament HTML a fost eliminat URL:

Hello, Fortunately, the excellent pfSense gateway software offers a pre-packaged tinc directly in its official repository. This allows a pfSense machine to participate in a tinc mesh. However, experimenting with pfSense, I was unable (at least from the web interface) to figure out how to: - configure pre-packaged tinc to start with multiple partners (the equivalent of multiple Connect lines in

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, Since the present tinc documentation is not very clear about this, please explain the following: is it mandatory to include the local IP address classes in the global VPN address class? Namely, please consider the following setup (which works great in practice): 1. A tinc VPN, full mesh, with n nodes (n > 3) 2. tinc runs on the firewall, which is also the default gateway for each

Hello all, Thank you for tinc, that is an **excellent** and useful package! 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 Fedora, Debian, Ubuntu,