From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 7663921F1D6 for ; Mon, 26 Aug 2013 12:28:17 -0700 (PDT) Received: by mail-qe0-f51.google.com with SMTP id cy11so2051113qeb.10 for ; Mon, 26 Aug 2013 12:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IIWP/wGwiSjIK5+Jmx0whPphm2USTSNa8nMKHdX6ctk=; b=mrC9HtYSDi+g7jDe72gBBlFETb/bZLVfEQd4bE7n0tTQAuJ1nc+KPNRKfzAdNy6RS2 lvQ149pDmgF5YcvRP1ptJ5B7+00RCJMQBBELwTwEvvFutrfrynM8OwxrpbMAJtcXBJWI VpWsKLUDIfCboYlKMTAWxVAKcoLmg9CdEQbSLe7P6sX65x9yv6vwcr7RtBZKUT7o8AHA TEA0ulWHifICKWU47ixH9vpLq5G5QcSNueOKSnb3KxKt2BdFy8ukv7UPcq9dkEFkVxx4 zwYuSyVkzRpKDkUeRlTEHModFQfPAOvzftzEQox2PEZM1V620Xcf4i28dhsO4i6qxk13 Gs8Q== MIME-Version: 1.0 X-Received: by 10.224.147.141 with SMTP id l13mr3271554qav.102.1377545295953; Mon, 26 Aug 2013 12:28:15 -0700 (PDT) Received: by 10.224.60.137 with HTTP; Mon, 26 Aug 2013 12:28:15 -0700 (PDT) In-Reply-To: References: Date: Mon, 26 Aug 2013 12:28:15 -0700 Message-ID: From: Dave Taht To: Collin Anderson Content-Type: multipart/alternative; boundary=089e0149cdb40720e704e4dec2c6 Cc: bloat Subject: Re: [Bloat] how to fix modem buffer bloat? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Aug 2013 19:28:17 -0000 --089e0149cdb40720e704e4dec2c6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The advantage of cerowrt is that it runs about 3-4 months ahead of openwrt on improvements to the bloat problem, and fixing bugs. The disadvantage is that it runs about 3-4 months ahead of openwrt on having new bugs. Example: We just finished (with the aid of multiple parties ) finally fixing a problem in HTB's atm DSL compensation that has existed for a year (and probably several years before that), and I think the final set of fixes will land in Linux 3.10.10 or .11 soon. Right now it's very possible to merely layer two components of cero on top of openwrt to get most of the benefit of the current work. (the aqm-scripts and gui, and if you are daring, a couple patches to codel and fq_codel) Sadly, I wouldn't recomend the current dev builds of cero for day-to-day use at this point, although I hope to get to a new stable release by the end of september. There's a ton of outstanding bugs left to fix. While openwrt runs fq_codel by default on all interfaces, it's mildly premature to be doing so on the wifi front. Work is in progress. However in the general case, at the moment the principal use for fq_codel in a home router is on the gateway to the internet - the fq_codel QoS system in openwrt and dd-wrt works extremely well (with the exception of ipv6 native). I believe the package in cerowrt is better in most respects (notably on ipv6), but limited in others. Gargoyle is using a prior effort (improved sfq + an automatic rate measurement system called ACC). There are other options like using small atom boxes, ipfire, and several commercial products.... The stable (feburary) release of cero is pretty usable, but lacks the modernized aqm scripts, the htb fix, a bunch of ipv6 fixes, etc, etc. I wish I could give firm advice, but we're kind of in the middle of a ton of stuff right now, all I can do is encourage you to leap in, fix things for yourself, and help out where you can. On Mon, Aug 26, 2013 at 11:53 AM, Collin Anderson wro= te: > Hi All, > > > Any recommendations for solving the bufferbloat on my Comcast SMC cable > modem? > > Looking at it more, a workaround is probably all I can hope for at > this point. I first started keeping a ping session open back in 2008 > to debug the internet, and I see bufferbloat almost every day at home > and at work. Anything to avoid the symptoms sounds great. > > I want something reliable and have minimal configuration. I'm thinking > about buying a WNDR3800 and installing CeroWRT, or is there better > recommended hardware? > > Also, isn't fq_codel "on by default" [1] in OpenWRT? If so, what's the > advantage of CeroWRT? > > Thanks, > Collin > > [1] http://www.ietf.org/proceedings/87/slides/slides-87-aqm-6.pdf > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html --089e0149cdb40720e704e4dec2c6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The advantage of cerowrt is that = it runs about 3-4 months ahead of openwrt on improvements to the bloat prob= lem, and fixing bugs.

The disadvantage is that it runs about 3-4 mon= ths ahead of openwrt on having new bugs.

Example: We just finished (with the aid of multiple parties ) fin= ally fixing a problem in HTB's atm DSL compensation that has existed fo= r a year (and probably several years before that), and I think the final se= t of fixes will land in Linux 3.10.10 or .11 soon.

Right now it's very possible to merely layer two components o= f cero on top of openwrt to get most of the benefit of the current work. (t= he aqm-scripts and gui, and if you are daring, a couple patches to codel an= d fq_codel)

Sadly, I wouldn't recomend the current dev builds of cero for day-t= o-day use at this point, although I hope to get to a new stable release by = the end of september. There's a ton of outstanding bugs left to fix.
While openwrt runs fq_codel by default on all interfaces, it'= s mildly premature to be doing so on the wifi front. Work is in progress. H= owever in the general case, at the moment the principal use for fq_codel in= a home router is on the gateway to the internet - the fq_codel QoS system = in openwrt and dd-wrt works extremely well (with the exception of ipv6 nati= ve). I believe the package in cerowrt is better in most respects (notably o= n ipv6), but limited in others. Gargoyle is using a prior effort (improved = sfq + an automatic rate measurement system called ACC). There are other opt= ions like using small atom boxes, ipfire, and several commercial products..= ..

The stable (feburary) release of cero is pretty usable, but lacks= the modernized aqm scripts, the htb fix, a bunch of ipv6 fixes, etc, etc.<= br>
I wish I could give firm advice, but we're kind of in the = middle of a ton of stuff right now, all I can do is encourage you to leap i= n, fix things for yourself, and help out where you can.



On Mon, Aug 26, 2013 at 11:53 AM, Collin Anderson <c= mawebsite@gmail.com> wrote:
Hi All,

> Any recommendations for solving the bufferbloat on my Comcast SMC cabl= e modem?

Looking at it more, a workaround is probably all I can hope for at this point. I first started keeping a ping session open back in 2008
to debug the internet, and I see bufferbloat almost every day at home
and at work. Anything to avoid the symptoms sounds great.

I want something reliable and have minimal configuration. I'm thinking<= br> about buying a WNDR3800 and installing CeroWRT, or is there better
recommended hardware?

Also, isn't fq_codel "on by default" [1] in OpenWRT? If so, w= hat's the
advantage of CeroWRT?

Thanks,
Collin

[1] http://www.ietf.org/proceedings/87/slides/slides-87-aq= m-6.pdf
___________________________________= ____________
Bloat mailing list
Bloat@lists.bufferbloat.net<= /a>
= https://lists.bufferbloat.net/listinfo/bloat



--
Dave T=E4ht=

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/= subscribe.html=20
--089e0149cdb40720e704e4dec2c6--