similar to: Who is offering commercial support for tinc?

Thanks Guus for the quick answer, I will give a try now. Рысь, In my case we don't want to restart tinc "server" at all, therefore what might happen is that the client is still connected to server while its public key was already removed from server. I will try the signal approach. Heng On Mon, Jul 25, 2016 at 12:42 PM, <tinc-request at tinc-vpn.org> wrote: > Send tinc

On Tue, Jan 26, 2016 at 08:52:29PM +0100, Guus Sliepen wrote: > > My intention was to sign the content of export-all with the nodes' public key, which would require the corresponding private key to verify. > > > > Does this make sense ? > > Yes, that does make a lot of sense. I'll see if I can add a safe way to > sign/verify arbitrary data with the tinc

Hello, It's almost time for a new release: 1.0. We would like this release to support all the platforms supported by 1.0pre8: GNU/Linux, FreeBSD, OpenBSD, NetBSD, MacOS/X (Darwin) and Solaris (SunOS). Furthermore, we also would like to see tinc ported to the following platforms: GNU/Hurd, Windows (Cygwin/MingW/native) However, all the main developers work mainly with Linux and have little

Would it not make more sense to have this on packagers responsiblity instead like you were saying adding it into the upstream repo. Maybe have a secondary repo that people can contribute to for distribution specific files and install scripts. On 24 September 2015 at 21:30, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: >

On Thu, Sep 24, 2015 at 05:45:36PM +0200, Guus Sliepen wrote: > On Thu, Sep 24, 2015 at 05:51:30PM +0300, R?zvan Sandu wrote: > > > IMHO, we need: > > > > 1. A proper tinc.service file, included by default (prepackaged) in the > > stock .deb and .rpm packages in Fedora, Debian, Ubuntu, CentOS, etc. > > > > By "proper" I mean it will start

Thanks Guus! Looking forward to trying out tinc 1.1pre15. Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Nirmal On Sat, Sep 2, 2017 at 1:47 PM Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc versions 1.0.32 and > 1.1pre15. > > Here is a summary of the changes in tinc 1.0.32: > > * Fix segmentation fault when using Cipher =

Thanks Guus! Looking forward to trying out tinc 1.1pre15. Can 1.1pre15 nodes coexist with 1.1pre14 nodes? Nirmal On Sat, Sep 2, 2017 at 1:47 PM Guus Sliepen <guus at tinc-vpn.org> wrote: > With pleasure we announce the release of tinc versions 1.0.32 and > 1.1pre15. > > Here is a summary of the changes in tinc 1.0.32: > > * Fix segmentation fault when using Cipher =

Thanks for the answer Guus, One more thing. I can run two tinc daemons one for each group, but I sill need to communicate clients from one group to the other. Clients from group 2 (admin group) need to reach clients from group 1 (remote server group), but clients from group 1 must not be able to reach each other nor the server. If I'm not using TunnelServer and Forwarding, How can I setup

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

Thanks for the reply Guss, So in my case the Amazon VPS server is behind a FULL CONE NAT(static NAT), so is that enough to hole punch other nodes. what all ports will should be opened up on the NAT device? Most of the other nodes are behind cg-nat, so I wont have any control over its nat. Thank you, Regards, Bobby Thomas. On Oct 19, 2015 1:45 AM, "Guus Sliepen" <guus at

Ah, fantastic. With the following config I get a usable tap0: $ sudo cat /etc/tinc/robotvpn/tinc.conf Name = elendur Mode = switch AddressFamily = ipv4 Device = /dev/tap0 Compression = 1 ConnectTo = robot_ph_cpe22_04 Still need to figure out the Avahi side of things for name resolution, but thanks all! On 26 February 2016 at 11:04, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu,

when you say "home server" you want me to do this in tinc "histup" or somewhere else OR on the firewall? similarly do i have to add route on the PC that runs the tinc daemon? Regards Ramesh On Sun, Jan 15, 2017 at 8:57 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Jan 12, 2017 at 09:27:45PM -0500, Ramesh wrote: > > > I have the following setup

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

>Updated support for BSD tun/tap devices. It is broken on FreeBSD tun. tcpdump on tun, 09:05:07.458988 IP0 bad-hlen 0 On Sun, Apr 24, 2016 at 8:16 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > 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

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*

Earlier, my tinc topology is this: https://ibb.co/bP1EJa <https://ibb.co/bP1EJa>, let me explain a little bit: client configuration: Name = client AddressFamily = ipv4 ProcessPriority = high PingTimeout = 10 TunnelServer = yes 1. All tinc nodes configured with “IndirectData = yes”, and the lines shown on the picture with arrow means the directional “ConnectTo”, so all the tinc traffic will

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

On Wed, Apr 27, 2016 at 05:15:57PM +0800, hshh wrote: > >Updated support for BSD tun/tap devices. > It is broken on FreeBSD tun. > > tcpdump on tun, > 09:05:07.458988 IP0 bad-hlen 0 Can you show me your tinc.conf and tinc-up script? Also, which version of FreeBSD are you using? -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org>