search for: ezrac

1. The UDT library is a BSD-licensed accelerated UDP-based transport. Would tinc be able to use this for UDP-based connections and would the licensing be acceptable? http://udt.sourceforge.net/index.html 2. I would like to see a 3rd compression protocol added to tinc: one based on the Mahoney compression schemes would be worth investigating (need something fast and uses small RAM on

...ference is that I don't use quagga but radvd for autoconfiguration at the sites. The setup as a whole is working quite well I must say! It would be awesome if you could shed some light on how your setup is working now. Thank you! Philipp On 23 January 2012 00:44, Michael Adams <madams at ezrac.com> wrote: > Updated IPv6 tutorial for your consideration: I abandoned use of the one > described on the tinc site some years back. > > http://unquietwiki.com/ipv6/tinc_quagga_ipv6.html

For tinc users on OpenWRT: https://dev.openwrt.org/changeset/29137 ciao :) Saverio

Sorry for the delayed response: been a busy weekend. SCTP looks very promising, and would make a hopefully stable mesh: I agree with your assessment in that regard vs optimized UDP setups. http://en.wikipedia.org/wiki/SCTP As for my request for improved compression, the "zpipe" implementation looks promising, as it is a high-level streaming compressor. I know most of the developers

I was looking up zlib files for another project, and noticed zlib was updated significantly this Spring, particularly in March & April of 2010. Any plans to recompile tinc to use it? http://www.zlib.net/ The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not

Ah, very good then. There does seem to be some changes in zip compression behavior with the new lib & a build of OptiPNG I use, so I'm curious how it'd affect tinc traffic on compressed links. Then again I use LZO on my links, so I don't expect to see any changes for myself. -----Original Message----- From: tinc-devel-request at tinc-vpn.org To: tinc-devel at tinc-vpn.org

Kernel 2.6.38 has adopted a format called XZ for kernel use, as well as some filesystems. Format appears to be optimized for streaming and embedded use. I'll happily test it if anyone wants to plug in some code for it. http://tukaani.org/xz/format.html http://kernelnewbies.org/LinuxChanges -------------- next part -------------- An HTML attachment was scrubbed... URL:

http://code.google.com/p/snappy/ Google's methodology on this is to compress fast by taking advantage of 64-bit processing for volume, and stripping out secondary analysis for speed. I am using tinc on a mix of 32-bit and 64-bit routers: this may be useful for at least inter-x64 links (it will still work on 32-bit chips, just slower). -------------- next part -------------- An HTML

http://www.open-mesh.org/ Idea #1: is BATMAN worth considering using as part of the layer 2 routing in Tinc? Idea #2: would it be possible to embed BATMAN as an option to avoid having to use Quagga for routing v6 subnets? -------------- next part -------------- An HTML attachment was scrubbed... URL:

A while back I expressed interest in trying to add additional compression formats (XZ, ZPAQ-derived). What would be the best way for me to try these with the 1.1 codebase? And can 1.1 be used with 1.0.x nets out-of-box? http://en.wikipedia.org/wiki/Xz http://mattmahoney.net/dc/zpaq.html -------------- next part -------------- An HTML attachment was scrubbed... URL:

I know I have some quirky behavior involving my layer two tinc host, and the IPv6 subnet that runs off of it. Facebook just issued a kernel patch that changes the behavior of the IPv6 tunnel mechanism: I can't tell from the patch itself, if it might also improve functionality for non IP6-IP6 tunnels.

Some of my Windows hosts where the main tinc router is, can't ping out to IPv6 external sites. I don't think its a tinc problem though: I use Quagga for routing. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20120612/0dd54f13/attachment.html>

Hello all. I've constructed a tutorial for how to setup an IPv6-based VPN for tinc, using Linux routers and "switch" mode. http://www.wolfsheep.com/technical/tinc_ipv6/ The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any

Updated IPv6 tutorial for your consideration: I abandoned use of the one described on the tinc site some years back. http://unquietwiki.com/ipv6/tinc_quagga_ipv6.html -----Original Message----- From: tinc-request at tinc-vpn.org To: tinc at tinc-vpn.org Date: Sat, 14 Jan 2012 12:00:02 +0100 Subject: tinc Digest, Vol 87, Issue 6 Send tinc mailing list submissions to tinc at

A while back, I suggested adding some compressors to tinc to increase the options available for its use: never had the time to take a crack at doing such adding. I have found something else that may or may not be a good fit with tinc: a WAN-optimization/delta compression mechanism. Such mechanisms reduce the amount of traffic carried over a network, by detecting and omitting duplicate

1. Compress should be in your hosts file, not your config file. 2. Since its a low-end CPU on the router, try using Compression=10 or 11 (fast/best lzo); I use 9 (max zlib) on my ASUS OpenWRT routers & ClearOS boxes. 3. If you're using Backfire OpenWRT, you should be able to use the version of tinc compiled in trunk http://downloads.openwrt.org/snapshots/trunk/ On 9/20/2010 5:22 PM,