From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: "Eric S. Johansson" <esj@eggo.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] looking for gold standard for deploying bufferbloat remediation
Date: Sun, 20 Dec 2015 09:15:05 +0000 [thread overview]
Message-ID: <CANmMgnGJBCtqz0fN205OLP8PSpSzgdWeX5KUK3NSqJ8bF-Y5tQ@mail.gmail.com> (raw)
In-Reply-To: <56748E39.9070901@eggo.org>
On 18/12/2015, Eric S. Johansson <esj@eggo.org> wrote:
> my attention drifted and I lost track of which path I should take to
> implement bufferbloat remediation (fq_codl+cake?). link is FIOS 25/25
> Mbps. I have a wndr 3800 on the shelf I can use. is there a better
> device, cerowrt or openwrt?
>
> I need a setup and forget style solution since this is for a paying
> customer, not my home why-is-the-internet-acting-funky-dammit setup. :-)
W.r.t the software, I think Rich did a great job on the howto.
http://wiki.openwrt.org/doc/howto/sqm
prev parent reply other threads:[~2015-12-20 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 22:52 Eric S. Johansson
2015-12-18 22:57 ` Jonathan Morton
2015-12-20 9:15 ` Alan Jenkins [this message]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANmMgnGJBCtqz0fN205OLP8PSpSzgdWeX5KUK3NSqJ8bF-Y5tQ@mail.gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=esj@eggo.org \
/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