From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cake] [Make-wifi-fast] Airtime fairness patch merged upstream, and the Turris Omnia debloated
Date: Fri, 23 Dec 2016 18:18:21 -0800 [thread overview]
Message-ID: <CALQXh-PyBWcrj_xDqMB80GYoAyHdCz=abzcanqZmvkY2dmJqSA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4-ZoOQHj6RiZ5NW5un1uBe5ankWf6zAjBNQu_kzOk-6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Fri, Dec 23, 2016 at 6:07 PM, Dave Taht <dave.taht@gmail.com> wrote:
> your 3800 is outperforming the ac1900 across the board at this distance????
>
Wired, 3800 running the latest LEDE snapshot, and the ac1900 running the
OpenWRT CC release. They have _slightly_ different SQM settings, though:
3800:
LEDE 2016/12/22 snapshot
"piece of cake"
135Mbps down
12Mbps up
DSCP no squash, don't ignore on ingress
ECN
wrt1900ac:
OpenWRT Chaos Calmer rc2
simple.qos
160Mbps down
12Mbps up
DSCP no squash, allow on ingress
ECN
So I'm running a single-queue on the 3800, and multi-queue on the wrt. The
WRT has always counted bytes in an "off" manner, limiting to _far_ below
the set level. Unlimited on this modem is up at 180Mbps downstream today.
Today's tests with LEDE on the 3800 were a warm-up for moving the wrt1900ac
over to LEDE. But I wanted a backup in case something goes awry (nearly
bricked the 3800 as I forgot to uncheck "keep settings" on the
OpenWRT->LEDE upgrade.
-Aaron
[-- Attachment #2: Type: text/html, Size: 1597 bytes --]
next prev parent reply other threads:[~2016-12-24 2:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 22:31 [Cake] " Toke Høiland-Jørgensen
2016-12-20 0:10 ` Dave Taht
2016-12-20 1:23 ` Dave Taht
2016-12-20 8:46 ` Kevin Darbyshire-Bryant
2016-12-20 8:49 ` Kevin Darbyshire-Bryant
2016-12-20 11:09 ` Sebastian Moeller
2016-12-20 1:22 ` Dave Taht
2016-12-24 1:32 ` [Cake] [Make-wifi-fast] " Aaron Wood
2016-12-24 1:41 ` Dave Taht
2016-12-24 1:48 ` Aaron Wood
2016-12-24 1:59 ` Dave Taht
2016-12-24 2:01 ` Jonathan Morton
2016-12-24 2:03 ` Dave Taht
2016-12-24 2:18 ` Aaron Wood
2016-12-24 2:29 ` Dave Taht
2016-12-24 2:51 ` Aaron Wood
2016-12-24 3:17 ` Dave Taht
2016-12-24 14:03 ` Valent Turkovic
2016-12-25 17:06 ` Toke Høiland-Jørgensen
2016-12-24 2:07 ` Dave Taht
2016-12-24 2:15 ` Dave Taht
2016-12-24 2:18 ` Aaron Wood [this message]
2016-12-24 2:22 ` Aaron Wood
2016-12-24 2:24 ` Dave Taht
2016-12-24 2:25 ` Aaron Wood
2016-12-24 2:33 ` Dave Taht
2016-12-24 2:49 ` Aaron Wood
2016-12-24 2:31 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-PyBWcrj_xDqMB80GYoAyHdCz=abzcanqZmvkY2dmJqSA@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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