similar to: [Announcement] Version 1.0.3 released

I get a lot of these in my log, especially when I am moving lots of traffic across the vpn: Sep 20 10:45:11 titan tinc.tdvpns[16152]: Got late or replayed packet from holden (xx.yy.zz.ww port 655), seqno 37609, last received 37610 (sequence numbers displayed generally differ by only one) What exactly is this trying to say? Surely this doesn't simply mean that the udp packets arrived in a

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,

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. Finally I discovered the mailinglists and subscribed. Before, I were in #tinc, pinging guus all the time with various stuff/problems/patches/etc. So... the problems, in no particular order. 1) Quite often, after re-starting a client (I run in tunnelserver mode), no packets are flowing. Tcpdump shows packets being sent from client but nothing gets received, and on the server both send

With pleasure we announce the release of version 1.0.10. Here is a summary of the changes: * Fixed potential crashes during shutdown and (in rare conditions) when other nodes disconnected from the VPN. * Improved NAT handling: tinc now copes with mangled port numbers, and will automatically fall back to TCP if direct UDP connection between nodes is not possible. The TCPOnly option

With pleasure we announce the release of version 1.0.10. Here is a summary of the changes: * Fixed potential crashes during shutdown and (in rare conditions) when other nodes disconnected from the VPN. * Improved NAT handling: tinc now copes with mangled port numbers, and will automatically fall back to TCP if direct UDP connection between nodes is not possible. The TCPOnly option

Here's a patch that does the steps I mentioned in my last email: - remove BlockingTCP - make send_meta return true on EWOULDBLOCK - add logic to main_loop to watch for write availability of meta connections with non-empty buffers and flush them. It fixes the extra packets with TCPOnly and should resolve the problems that made BlockingTCP necessary also. (No testing of that last bit.)

> Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. Hello, these features were introduced in 1.0.13 correct ?? I also understand that the two settings are by default "yes" if not explictly set to "no" in the config file. what may happen if I have a network with mixed versions from 1.0.11 and 1.0.13, where the older daemons do not implement that feature

Hi guys, I can't see virtio in releng/9.1, is there any particular reason why it isn't going to be included given that it works reasonable well (and is optional anyway, so not likely to be detrimental)? Thanks, Joe

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.

.PLS files should work for iOS devices. See sample text: [playlist] numberofentries=1 File1=http://91.121.91.172:31090/LG73 Title1=LG73 Vancouver's Best Music Mix! Length1=-1 Version=2 On Wed, Jan 20, 2016 at 1:27 PM, Holden Stanford <hstanford1 at gmail.com> wrote: > You can create a .m3u or .mp3 container linking to the stream URL. I can't > remember the exact tags

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

Short story: cannot get Kerberized NFSv4 to work. I've googled a great deal and cannot find where I have goofed (and there sure is a lot of misleading and just plain incorrect information out there), so would appreciate another pair of eyes. NFSv4 without Kerberos does work fine, as does ID mapping. We're using NFSv4 in production with sec=sys, but I'm not happy with that. My

Short story: cannot get Kerberized NFSv4 to work. I've googled a great deal and cannot find where I have goofed (and there sure is a lot of misleading and just plain incorrect information out there), so would appreciate another pair of eyes. NFSv4 without Kerberos does work fine, as does ID mapping. We're using NFSv4 in production with sec=sys, but I'm not happy with that. My

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

Hi all, I'm trying to do an example in Deepayan Sarkar's Lattice book. It involves making a barchart based on the Titanic dataset. I can get the barchart to plot fine; however, when I try to edit panel.grid, I get an error: > titan<-barchart(Class ~ Freq | Age + Sex, data = as.data.frame(Titanic), groups=Survived, stack=TRUE, layout=c(4,1),

With pleasure we announce the release of tinc versions 1.0.33. Here is a summary of the changes in tinc 1.0.33: * Allow compilation from a build directory. * Source code cleanups. * Fix some options specified on the command line not surviving a HUP signal. * Handle tun/tap device returning EPERM or EBUSY. * Disable PMTUDiscovery when TCPOnly is used. * Support the --runstatedir option of

With pleasure we announce the release of tinc versions 1.0.33. Here is a summary of the changes in tinc 1.0.33: * Allow compilation from a build directory. * Source code cleanups. * Fix some options specified on the command line not surviving a HUP signal. * Handle tun/tap device returning EPERM or EBUSY. * Disable PMTUDiscovery when TCPOnly is used. * Support the --runstatedir option of

With pleasure we announce the release of tinc version 1.1pre16. Here is a summary of the changes in tinc 1.1pre16: * Fixed building with support for UML sockets. * Documentation updates and spelling fixes. * Support for MSS clamping of IP-in-IP packets. * Fixed parsing of the -b flag. * Added the ability to set a firemall mark on sockets on Linux. * Minor improvements to the build system.

With pleasure we announce the release of tinc version 1.1pre16. Here is a summary of the changes in tinc 1.1pre16: * Fixed building with support for UML sockets. * Documentation updates and spelling fixes. * Support for MSS clamping of IP-in-IP packets. * Fixed parsing of the -b flag. * Added the ability to set a firemall mark on sockets on Linux. * Minor improvements to the build system.