From: Kenyon Ralph <kenyon@kenyonralph.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] how to fix modem buffer bloat?
Date: Mon, 26 Aug 2013 12:01:55 -0700 [thread overview]
Message-ID: <20130826190155.GI23831@kenyonralph.com> (raw)
In-Reply-To: <CAFO84S5Ym=2C7VfKbNFd-Cgt6qO=7_GwWxYMVgEC3U=qt45B+Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On 2013-08-26T14:53:44-0400, Collin Anderson <cmawebsite@gmail.com> wrote:
> 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?
WNDR3800 with OpenWrt and properly configured and activated
/etc/config/qos which uses fq_codel has been working great for my
house. Solves the bufferbloat problem to my satisfaction on my Cox
cable connection.
> Thanks,
> Collin
>
> [1] http://www.ietf.org/proceedings/87/slides/slides-87-aqm-6.pdf
--
Kenyon Ralph
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-26 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 1:03 Collin Anderson
2013-08-26 18:53 ` Collin Anderson
2013-08-26 19:01 ` Kenyon Ralph [this message]
2013-08-26 19:28 ` Dave Taht
2013-08-26 20:18 ` Collin Anderson
2013-08-27 13:31 ` Naeem Khademi
2013-08-27 18:11 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130826190155.GI23831@kenyonralph.com \
--to=kenyon@kenyonralph.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox