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 routers). http://mattmahoney.net/dc/ 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 disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The contents of this email do not necessarily represent the views or policies of E-Z Rent-A-Car or employees. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20091108/42d39593/attachment.html>
Why additional compression method? These days bandwidth is quite cheap. Encryption already eats enough CPU cycles. Using compression on 10Mbit+ is quite pointless? ---------- Original message ---------- From: Michael Adams <madams at ezrac.com> To: "tinc-devel at tinc-vpn.org" <tinc-devel at tinc-vpn.org> Subject: Suggested additions for TINC Date: Sun, 08 Nov 2009 02:50:47 -0500 Message-ID: <WC20091108075047.3700E6 at ezrac.com> 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 routers). http://mattmahoney.net/dc/ 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 disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The contents of this email do not necessarily represent the views or policies of E-Z Rent-A-Car or employees.
On Sun, Nov 08, 2009 at 02:50:47AM -0500, Michael Adams wrote:> 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.htmlUDT implements its own congestion and retransmission algorithms, so using this for VPNs would still give you all the problems decribed on this page: http://sites.inka.de/~W1011/devel/tcp-tcp.html If we are at a point where we can work on the transport layer of tinc, I'd rather implement support for SCTP first.> 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 routers). > > http://mattmahoney.net/dc/I cannot quickly find a comparison between Matt's algorithms and Zlib or LZO algorithms. I will gladly accept a patch to support other compressors, but I personally do not see much value in yet another one. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20091108/e47d569a/attachment.pgp>