From: Dave Taht <dave.taht@gmail.com>
To: Outback Dingo <outbackdingo@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] curious.....
Date: Tue, 3 Dec 2013 16:38:51 -0800 [thread overview]
Message-ID: <CAA93jw50fFyrrRyAmK29nv5Pq33EATV3dvDssX-M6Z_xiG5D9w@mail.gmail.com> (raw)
In-Reply-To: <CAKYr3zyNZaSmNWVgA7+XgvnMjF3CiQn3jiJ15p-StwtQAGHZ2g@mail.gmail.com>
On Tue, Dec 3, 2013 at 4:25 PM, Outback Dingo <outbackdingo@gmail.com> wrote:
>
>
>
> On Tue, Dec 3, 2013 at 5:25 PM, Kenyon Ralph <kenyon@kenyonralph.com> wrote:
>>
>> On 2013-12-03T13:40:00-0500, Outback Dingo <outbackdingo@gmail.com> wrote:
>> > found this blog about bufferbloat..... and their answer.
>> >
>> > http://blog.lxgr.net/posts/2013/01/28/my-openwrt-setup/
>>
>> OpenWrt's qos-scripts package uses fq_codel, so his manual approach is
>> not really necessary. Just install the qos-scripts package and
>> configure /etc/config/qos. Documentation is here, but site seems to be
>> down at the moment: http://wiki.openwrt.org/doc/uci/qos
>
>
> Yeah i know how to achieve it, i was just thinking some of us might get a
> chuckle from it. :) but thanks
It's simple and illustrates the idea, so I applaud the blog post. I
wish that the
constants were better explained.
I note that openwrt's qos-scripts still do not do ipv6 properly, and I think
cerowrt's aqm system is better in most respects, and it's easy to
include on an openwrt system.
>>
>>
>>
>> --
>> Kenyon Ralph
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-12-04 0:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04 0:25 ` Outback Dingo
2013-12-04 0:38 ` Dave Taht [this message]
2013-12-06 17:19 ` Juliusz Chroboczek
2013-12-06 18:15 ` Dave Taht
2013-12-07 11:24 ` Sebastian Moeller
2013-12-10 19:05 ` Dave Taht
2013-12-11 10:44 ` Sebastian Moeller
2013-12-07 12:59 ` Juliusz Chroboczek
2013-12-08 1:27 ` Steinar H. Gunderson
2013-12-08 5:24 ` Mikael Abrahamsson
2013-12-08 11:00 ` Mark Constable
2013-12-08 14:01 ` Outback Dingo
2013-12-08 14:03 ` Outback Dingo
2013-12-08 16:44 ` Mark Constable
2013-12-08 19:00 ` Sebastian Moeller
2013-12-08 13:12 ` Juliusz Chroboczek
2013-12-08 16:46 ` Jonathan Morton
2013-12-08 16:51 ` Dave Taht
2013-12-08 17:56 ` Juliusz Chroboczek
2013-12-08 21:05 ` Jonathan Morton
2013-12-08 14:22 ` Aaron Wood
2013-12-08 14:41 ` Jim Gettys
2013-12-08 10:40 ` Sebastian Moeller
2013-12-08 13:25 ` Juliusz Chroboczek
2013-12-08 16:26 ` Sebastian Moeller
2013-12-08 17:47 ` Juliusz Chroboczek
2013-12-08 19:02 ` Sebastian Moeller
2013-12-22 1:38 ` Dan Siemon
2013-12-22 3:46 ` Stephen Hemminger
2013-12-08 19:01 ` Jonathan Morton
2013-12-08 19:21 ` Sebastian Moeller
2013-12-08 16:01 ` Neil Davies
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09 9:51 ` Sebastian Moeller
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=CAA93jw50fFyrrRyAmK29nv5Pq33EATV3dvDssX-M6Z_xiG5D9w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=outbackdingo@gmail.com \
/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