From: Richard Smith <smithbone@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Linksys wrt1900acs rrul traces
Date: Fri, 8 Apr 2016 07:51:02 -0400 [thread overview]
Message-ID: <57079B26.6040208@gmail.com> (raw)
In-Reply-To: <CAA93jw62Exd7Ac4zC+qjn-daW0MAiwgH_wkExgZVgLZafo_niw@mail.gmail.com>
On 04/07/2016 11:24 AM, Dave Taht wrote:
> The default firmware is quite horrificly bad, isn't it?
:) Yeah. I had high hopes that they might have done something better
out of the gate.
> Total
> starvation of anything but the first flow, for example, in the native
> tests.
> Do you have the exact version number of the 1900ac's default firmware
> you tested.
1900ACS not AC. Slightly different hardware. ACS is a faster CPU (
(1.6Ghz) and more RAM.
Firmware version is in the directory name. :)
'wrt1900acs_stockfw_1.0.0.169041' It was the latest firmware on the
website when I ran the tests.
> However, I'd have recommended you try 900mbit to see if cake/etc does
> the right things, not 975mbit.
Ok. I'll use 900 next time.
--
Richard A. Smith
next prev parent reply other threads:[~2016-04-08 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 13:58 Richard Smith
2016-04-07 15:24 ` Dave Taht
2016-04-08 11:51 ` Richard Smith [this message]
2016-04-07 16:16 ` moeller0
2016-04-07 16:40 ` Dave Taht
2016-04-08 11:51 ` Richard Smith
2016-04-08 13:17 ` Sebastian Moeller
2016-04-08 13:55 ` John Yates
2016-04-08 19:20 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces ko Sebastian Moeller
2016-04-07 17:42 ` [Cerowrt-devel] Linksys wrt1900acs rrul traces Aaron Wood
2016-04-07 17:48 ` Dave Taht
2016-04-07 17:50 ` moeller0
2016-04-07 18:05 ` Dave Taht
2016-04-07 20:36 ` Aaron Wood
2016-04-08 11:51 ` Richard Smith
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=57079B26.6040208@gmail.com \
--to=smithbone@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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