On Tue, Jun 28, 2011 at 9:11 AM, Leigh Porter <leigh.porter@ukbroadband.com> wrote:
-----Original Message----- From: Cameron Byrne [mailto:cb.list6@gmail.com] Sent: 28 June 2011 16:53 To: Leigh Porter Cc: Andreas Ott; Eugen Leitl; williamejsalt@googlemail.com; NANOG list Subject: Re: [pfSense Support] Strange TCP connection behavior 2.0 RC2 (+3) In the 3G world, i have had good results overcoming longish RTT by using the Hybla TCP algorithm http://hybla.deis.unibo.it/
I am hoping it gets more default traction, especially in wireless where the radio link is a pretty big latency source
Cameron
How do you implement this for lots of clients and servers that have out of the box implementations? The FastSoft box is a TCP man-in-the-middle box that essentially implements the FAST TCP algorithm without either end having to worry about it.
You don't, the full benefits only come with a Linux kernel patch. The good news is that it only has to be implemented on the client end.
I have also used home-fudged TCP proxies with some success.
Some 3G/wireless/VSAT vendors implement their own TCP modification stacks but they usually only fiddle with window sizes and such.
That's why i said i hope it catches on as default :) If Android implemented Hybla, i think it would be a great improvement for user experience. Nobody likes the middleboxes that proxy TCP.... they cost money, don't scale well, and are generally fragile. Hybla is not a solution for the OPs issue, just a solution for high RTT links where the client can do Hybla. It an evolutionary step that i think would make a great fit in smartphones like Android. Cameron
-- Leigh
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________