search for: vpn_name

net-misc/tinc-1.0.12 works for me on amd64 1. there is an official ebuild for 1.0.11, but not for 1.0.12 yet 2. my -r1 contains changed initscript 'tincd.lo' to be used like net.lo by ln -s tincd.lo tincd.vpn_name and then calling tincd.vpn_name to start/stop 3. it is in my overlay together with latest versions of some other software: git://gitorious.org/jasiu-overlay-for-gentoo/jasiu-overlay-for-gentoo.git 4. can you add an information on tinc-vpn, that Gentoo officially supports tinc? -- Jan Pso...

...I have four networks connected via tinc - A, B, C and D. B, C and D connect to A. What is odd to me is that B and C communicate directly (without going to A); while all communication to D network goes via A. When I turned more verbose logging on tinc, I show a line like this: "adding route to VPN_NAME vi MASTER_VPN_NAME". Why does it happening ? Regards Kosta Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

...ave their port 655 open, but no node in the network has a ConnectTo to any blue labeled node - we are still using tinc1.1pre14 - The configuration was loaded by ensuring: - each node has the keys and Address for their ConnectTo targets - tinc was reloaded using the command: sudo tinc -n <vpn_name> reload The main motivation to do this: To avoid the network split bug we hit, that was addressed earlier in this email and to do this by ensuring deliberate and redundant connections to yellow1 and yellow2 We are concerned that: - We still dont see edges in the graph that show connections bet...

Hi Guus Thanks for clarifying. Some follow up questions: - How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to upgrade to? - What is the workaround until we patch with this fix? Using a combination of AutoConnect and ConnectTo? - When we use ConnectTo, is it mandatory to have a cert file in the hosts/* dir with an IP to ConnectTo ? -nirmal On Tue, Aug 22, 2017 at 12:10