[142494] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: [pfSense Support] Strange TCP connection behavior 2.0 RC2 (+3)

daemon@ATHENA.MIT.EDU (Leigh Porter)
Tue Jun 28 12:10:46 2011

From: Leigh Porter <leigh.porter@ukbroadband.com>
To: Cameron Byrne <cb.list6@gmail.com>
Date: Tue, 28 Jun 2011 16:11:23 +0000
In-Reply-To: <BANLkTi=KuAnuvwXkOi2wU=nXQuuWOLEg3JD3F4xR7uVc-9Gw3g@mail.gmail.com>
Cc: "williamejsalt@googlemail.com" <williamejsalt@googlemail.com>,
	NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org



> -----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/
>=20
> I am hoping it gets more default traction, especially in wireless
> where the radio link is a pretty big latency source
>=20
> 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 havi=
ng to worry about it.

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.

--
Leigh


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email=20
______________________________________________________________________


home help back first fref pref prev next nref lref last post