similar to: what is in version Tinc 2.0?

I meant Tinc site-site VPN deployments in US business segments. Just references if any. On Tue, Mar 20, 2018 at 1:44 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Tue, Mar 20, 2018 at 12:53:55PM -0700, al so wrote: > > > Are there any Tinc deployments in the USA in Medium sized businesses and > > small Enterprises? > > Yes. However, VPNs are Virtual *Private*

On Wed, Mar 14, 2018 at 12:36 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Wed, Mar 14, 2018 at 08:42:20AM -0700, al so wrote: > > > Is there performance issue with Tinc compared to alternatives? > > Performance depends on many variables, it is impossible to say "A is > nn% faster/slower than alternative B". The best way to check which > alternative

Suppose tinc is installed on 100 routers in 100 sites. How to automate site-site vpn management across 100 sites? Some kind of vpn management solution? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180329/90f0198d/attachment.html>

Is there performance issue with Tinc compared to alternatives? Is it still single threaded? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180314/985dfc11/attachment.html>

This part I have to answer on-list: > On 29 Mar 2018, at 17:50 , al so <volkswak at gmail.com> wrote: > > automation refers to day to day vpn management from non-IT layman... not a geek running shell/ansible scrpits. Dear Also / Volk Swak TINC have it’s uses and place in the VPN environment. Perhaps you could/should consider https://pritunl.com/ <https://pritunl.com/> or

There is a reason most NMS systems used SNMP in the past and REST apis past 7+ years. They don't use CLIs except toy Expect type scripts.. Not just security but better error handling and more. Good luck learning! On Thu, Mar 29, 2018 at 9:03 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > SNMP is mainly used for monitoring, not _server_ automation. > > Also, it's

Is SPTPS protocol enabled in 1.1 by default? Or we need to manually enable it. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20180316/2360e357/attachment.html>

So as probably any Tinc user, I noticed there are two versions: 1.0 and 1.1. On the website is explained that 1.1 is the stepping stone for 2.0 and that it has a lot of neat features *planned*. However, in the repositories, one usually finds version 1.0, and since I'm someone who prefers having everything run through repositories instead of manually updated, I want to know if it's worth

Please feel free to share your own benchmarks if any in the mean time. On Wed, Mar 14, 2018 at 12:36 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Wed, Mar 14, 2018 at 08:42:20AM -0700, al so wrote: > > > Is there performance issue with Tinc compared to alternatives? > > Performance depends on many variables, it is impossible to say "A is > nn% faster/slower

Just search online why in general that is insecure via CLI vs programmatic for first class automation.. there is a reason why snmp, rest, ... exist. On Thu, Mar 29, 2018 at 3:50 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > You've mentioned security issues in your previous email, but now you're > hopping to management issues. > > Have you tried Ansible, Chef or

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

Because of a security vulnerability in tinc that was recently discovered, we hereby release tinc versions 1.0.21 and 1.1pre7. Here is a summary of the changes in tinc 1.0.21: * Drop packets forwarded via TCP if they are too big (CVE-2013-1428). Here is a summary of the changes in tinc 1.1pre7: * Fixed large latencies on Windows. * Renamed the tincctl tool to tinc. * Simplified changing the

With pleasure we announce the release of tinc version 1.0.23. Here is a summary of the changes: * Start authentication immediately on outgoing connections (useful for sslh). * Fixed segfault when Name = $HOST but $HOST is not set. * Updated the build system and the documentation. * Clean up child processes left over from Proxy = exec. This version of tinc is compatible with 1.0pre8, 1.0

With pleasure we announce the release of tinc version 1.0.23. Here is a summary of the changes: * Start authentication immediately on outgoing connections (useful for sslh). * Fixed segfault when Name = $HOST but $HOST is not set. * Updated the build system and the documentation. * Clean up child processes left over from Proxy = exec. This version of tinc is compatible with 1.0pre8, 1.0

Hi, Guus I referre to the two separate tinc process/network(received same subnet), not Sunbet selection within one tinc process/network. My understanding is if different tinc process comes with exact subnet, as they are not related with each other(they have no idea regarding weights with each other), I guess the routing depends on the host's main routing table, for specific route it depends

With pleasure we announce the release of tinc version 1.0.25. Here is a summary of the changes: * Documentation updates. * Support linking against -lresolv on Mac OS X. * Fix scripts on Windows when using the ScriptsInterpreter option. * Allow a minimum reconnect timeout to be specified. * Support PriorityInheritance on IPv6 sockets. Thanks to David Pflug, Baptiste Jonglez, Alexis

With pleasure we announce the release of tinc version 1.0.25. Here is a summary of the changes: * Documentation updates. * Support linking against -lresolv on Mac OS X. * Fix scripts on Windows when using the ScriptsInterpreter option. * Allow a minimum reconnect timeout to be specified. * Support PriorityInheritance on IPv6 sockets. Thanks to David Pflug, Baptiste Jonglez, Alexis

With pleasure we announce the release of tinc version 1.1pre13. Here is a summary of the changes: * Fix BSD tun device support that was broken in 1.1pre12. * Speed up AutoConnect when there are many host config files present without an Address. Please note that although tinc 1.1pre13 is backwards compatible with tinc 1.0.x, it is NOT compatible with tinc 1.1pre1 through 1.1pre10. -- Met

With pleasure we announce the release of tinc version 1.1pre13. Here is a summary of the changes: * Fix BSD tun device support that was broken in 1.1pre12. * Speed up AutoConnect when there are many host config files present without an Address. Please note that although tinc 1.1pre13 is backwards compatible with tinc 1.0.x, it is NOT compatible with tinc 1.1pre1 through 1.1pre10. -- Met