similar to: [Announcement] Version 1.0.10 released

I'm been experiencing a very very odd problem for the past several weeks and am throwing it out in case someone can shed some light on it for me. There is a single box on our tinc mesh which can be pinged from all hosts, but cannot ping any. It is not limited to ping, the box cannot communicate over tinc. tinc is running in router mode for this mesh. ~30 other nodes function normally,

Hello, I've managed to create a tinc build for IPhone and IPod touch. Since the device does not support TUN interface, TUNEMU was used: http://code.gerade.org/tunemu/ Please find the patch in the attachment (to be used with tinc-1.0.9). The patch does the following: - updates src/Makefile.in & src/Makefile.am so required libraries are attached and tunemu.c is compiled - updates

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

Hello again :) Thank you all for your reply's. Below are the config files of the 3 hosts. I use  tinc in router mode. I do not have a kernel mode config lines anywhere so tinc must be using the default settings here. I added the ipaddressx to subnets on hostc and this works. Traffic to that ip is now routed via hostc. But since this ipaddressx address changes often I need to resolve it

Hi, I´m using Tinc for several years, but I didn´t fix a performance problem. There a about 20 nodes in this network. Master: 10.0.0.12 (dedicated host in a datacenter, debian, 100mBit port) tinc.conf: Name = TincKnoten12 AddressFamily = ipv4 Interface = tun ProcessPriority=high mode = router #DirectOnly = no Compression=0 PMTUDiscovery = yes #IndirectData = yes #ReplayWindow = 64 #ConnectTo

With pleasure we announce the release of version 1.0.3. Here is a summary of the changes: * Show error message when failing to write a PID file. * Ignore spaces at end of lines in config files. * Fix handling of late packets. * Unify BSD tun/tap device handling. This allows IPv6 on tun devices and anything on tap devices as long as the underlying OS supports it. * Handle IPv6 on Solaris tun

With pleasure we announce the release of version 1.0.3. Here is a summary of the changes: * Show error message when failing to write a PID file. * Ignore spaces at end of lines in config files. * Fix handling of late packets. * Unify BSD tun/tap device handling. This allows IPv6 on tun devices and anything on tap devices as long as the underlying OS supports it. * Handle IPv6 on Solaris tun

With pleasure we announce the release of version 1.0.15. Here is a summary of the changes: * Improved logging to file. * Reduced amount of process wakeups on platforms which support pselect(). * Fixed ProcessPriority option under Windows. Thanks to Lo?c Greni? for his contribution to this version of tinc. This version of tinc is compatible with 1.0pre8, 1.0 and later, but not with earlier

With pleasure we announce the release of version 1.0.15. Here is a summary of the changes: * Improved logging to file. * Reduced amount of process wakeups on platforms which support pselect(). * Fixed ProcessPriority option under Windows. Thanks to Lo?c Greni? for his contribution to this version of tinc. This version of tinc is compatible with 1.0pre8, 1.0 and later, but not with earlier

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

On 11 April 2018 at 11:30, Hans de Groot <hansg at dandy.nl> wrote: > Hello again :) > > Thank you all for your reply's. Below are the config files of the 3 hosts. > I use tinc in router mode. I do not have a kernel mode config lines > anywhere so tinc must be using the default settings here. > > I added the ipaddressx to subnets on hostc and this works. Traffic

Hi, All Recently, one of my tinc client always suffer connection drop, I was suspect the connection was not stable to cause this issue, and BTW, I’ve set the PingTimeout to 10 seconds already, but this situation still happens a lot sometimes, but when the connection drop happens, the connection recovery pretty fast, normally in a minutes. In order to deep dive into the cause, or proven the

Well i currently try to set up tinc between two hosts, one with normal dsl connection one behind some kind of unknown firewall (Note since OpenVp is able to connect when the normal one is the Server I guess tinc should be able, too) start.bat-------------------------------tincd -n Empire-Network -D -d4 --bypass-security (Bypass is only currently because tis not working yet)

Hello! We switched to VPN tinc, a network of about 20 machines in cloud, setting TCPOnly = yes, everything works fine, except for one host on Windows, which is loaded with traffic, losses amount to about 20%, set the setting ProcessPriority = high, no changes, before it used OPENVpn loss did not occur, do not tell me what settings can change to avoid losses? -- Andrei Rubtsov -------------- next

Hi, We have a tinc network of about ~200 hosts and in the full mesh configuration we've had a lot of problems with the edge propagation storms taking the entire network down. Recently we had a setup with a small number of "hubs" to which all the other nodes connected to, which limited the number of meta connections, but that didn't help much with the edge propagation issues.

On Fri, Jul 10, 2015 at 5:57 PM Michael <cuscotravelservices at gmail.com> wrote: > However, given the warning messages I saw, maybe this is not the > correct (elegant and most efficient) way for the secondary files to > reference "libintl.h". > The best place to add that include and the gettext define would be to put them in rsync.h somewhere, which would make the

Hello, Here is a patch for protocol_subnet.c with two modifications : - in tunnelserver mode, tinc must check subnets in the ".../hosts/owner" config file, not in "c->config_tree" (which is the configuration of the meta-connection from which we receive the ADD_SUBNET message). - this checking can be made before the check of the owner, especially before any

Hi Folks, Well, it has only been more than 6 weeks and still no response to my "No localisation for rsync?" topic. :( So far, I have determined that there are at least 4 files that need translations for rsync. They are the following. main.c flist.c log.c progress.c For my initial test I only made the following modifications. main.c ------ I added the following line ... #include

Thank you for the helpful advice. We will try to group the servers with different ConnectTo servers first. If this does not help we will look at the TunnelServer solution. Just to make sure we understand TunnelServer correctly: do you need to specify every host as ConnectTo that the host should be able to communicate with or is it sufficient to just provide the hosts files? Thanks, Hendrik