Re: [aqm] fixing bufferbloat on bigpond cable...

Mark Nottingham <mnot@mnot.net> Thu, 12 March 2015 02:14 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82A31A89B5 for <aqm@ietfa.amsl.com>; Wed, 11 Mar 2015 19:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DCehZ-vR6DSw for <aqm@ietfa.amsl.com>; Wed, 11 Mar 2015 19:14:12 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 494F91A89B8 for <aqm@ietf.org>; Wed, 11 Mar 2015 19:14:12 -0700 (PDT)
Received: from [192.168.0.154] (unknown [120.149.147.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D30B722E263; Wed, 11 Mar 2015 22:14:05 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAA93jw59q6sWCfEjD2giY2GbMMTuSBDrAXYQLAir_fnnSoE7Ww@mail.gmail.com>
Date: Thu, 12 Mar 2015 13:14:03 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7681518-1B51-4E1D-88FF-83811EDA2563@mnot.net>
References: <CAA93jw59q6sWCfEjD2giY2GbMMTuSBDrAXYQLAir_fnnSoE7Ww@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/amTu7W_fqJFB2aEdjApU4QZCfJs>
X-Mailman-Approved-At: Wed, 11 Mar 2015 19:22:40 -0700
Cc: "aqm@ietf.org" <aqm@ietf.org>, netalyzr <netalyzr@icsi.berkeley.edu>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [aqm] fixing bufferbloat on bigpond cable...
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2015 02:14:13 -0000

Hi,

Just to clarify -- the credit goes to 'saltspork' on that thread, not I :)

Cheers,


> On 12 Mar 2015, at 1:11 pm, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I was very pleased to see this tweet go by today:
> 
> https://twitter.com/mnot/status/575581792650018816
> 
> where Mark Nottingham fixed his bufferbloat on bigpond cable
> using a very simple htb + fq_codel script. (I note ubnt edgerouters
> also have a nice gui for that, as does openwrt)
> 
> But: he does point out a flaw in netanalyzr's current tests[1], in that
> it does not correctly detect the presence of aqm or FQing on the link,
> (in part due to not running long enough, and also in not using
> multiple distinct flows) and like the "ping loss considered harmful"
> thread last week on the aqm and bloat lists, matching user
> expectations and perceptions would be good with any public
> tests that exist.
> 
> There is some stuff in the aqm evaluation guide's "burst tolerance"
> tests that sort of applies, but... ideas?
> 
> [1] I am not aware of any other tests for FQ than mine, which are still
> kind of hacky. What I have is in my isochronous repo on github.
> 
> -- 
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
> 
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

--
Mark Nottingham   https://www.mnot.net/