From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] bugs using the 1200ac as a target
Date: Mon, 25 Apr 2016 20:56:52 -0700 [thread overview]
Message-ID: <CAA93jw7Hxse6A=D+VCzDDm7JWH6AnPoociYt6NHTEP+2mq8S5Q@mail.gmail.com> (raw)
it has something deeply wrong in it at a gbit. In this test I'd failed
over to a faster link at a gigE to show WTF it does - one flow totally
wipes out the others.
http://blog.cerowrt.org/flent/failing_over_faster/linksys_1200_majorly_headblocking.svg
I've seen this behavior from this device since the very first one I
got 6 months back.
In other news:
http://blog.cerowrt.org/post/failing_over_faster/
http://blog.cerowrt.org/post/some_hackerboards_for_wifi/
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-04-26 3:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 3:56 Dave Taht [this message]
2016-04-27 22:04 ` Richard Smith
2016-04-27 22:08 ` Dave Taht
2016-04-27 22:34 ` Aaron Wood
2016-05-02 17:03 ` 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='CAA93jw7Hxse6A=D+VCzDDm7JWH6AnPoociYt6NHTEP+2mq8S5Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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