From: Dave Taht <dave.taht@gmail.com>
To: William Katsak <wkatsak@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 3.8.8-4 Question/Issue
Date: Wed, 22 May 2013 13:11:17 -0700 [thread overview]
Message-ID: <CAA93jw751OQx6+HeQ3HbdXtfvGebCBS21B8sz+ogRH_J7TbHQg@mail.gmail.com> (raw)
In-Reply-To: <CAPFzYAJu3cWq85-gW+3n-NPTeZdyvpm_BahcYsbnRxgAVx6hbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
I recommend fq codel over nfq codel at this point and there were a few bugs
in simple QoS that are fixed now but in the latest buggy versions of cero.
There was a DSL bug in particular on ingress. If you are using DSL delete
the ADSLL variable from the htb ingress setup lines.
There were also bugs in htb's quantum setup and based on the data thus far
it seems likely that disregarding and over writing diffserv classification
on ingress is also the right thing...
Let us know if fq codel works better on that build... And I just landed in
Philly and will try to stablize the current 3.8.13 series over the weekend.
Good stuff in the queue but need to get back to Eric's basement to
stabilize the karma.
On May 22, 2013 7:40 AM, "William Katsak" <wkatsak@gmail.com> wrote:
> Hello,
>
> I finally updated my main home router from an OLD cero build
> (pre-Sugarland, it had been running perfectly, so I left it alone). I
> figured I would be adventurous and go to 3.8.8-4.
>
> After reconfiguring everything, it seems to work fine, other than one
> issue: I use Amazon VOD, Netflix, Hulu, etc. at lot at home, and in
> particular, Amazon VOD has started to have a little stutter often enough to
> be annoying.
>
> Am I missing a parameter someplace, or is it likely that there is a bug?
> How to determine?
>
> I am using the GUI AQM interface, with nfq_codel/simple.qos. I have tried
> a few permutations of these settings, nothing seems to help, so I assume it
> is something internal, or on the wireless side.
>
> Anything I should try tweaking?
>
> Thanks,
> Bill Katsak
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
[-- Attachment #2: Type: text/html, Size: 2393 bytes --]
prev parent reply other threads:[~2013-05-22 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 11:39 William Katsak
2013-05-22 20:11 ` Dave Taht [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=CAA93jw751OQx6+HeQ3HbdXtfvGebCBS21B8sz+ogRH_J7TbHQg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=wkatsak@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