From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] A stable cerowrt release in sight
Date: Thu, 15 May 2014 23:36:11 -0700 [thread overview]
Message-ID: <CAA93jw48Po25+b1SgJKb=YBHixptSmO8z-7j2vqt9mc3k=hUkQ@mail.gmail.com> (raw)
it is now mid-may, about 3 months after I'd hoped to finally have a
stable release.
and I've spent about 8 months longer on this than I really could
afford. I'm glad that we seem to have a stable release of dnsmasq, the
sqm system is stable, and
aside from bug 442 I haven't hard crashed a box in months and months.
I considered bug 442 to be a showstopper and have spent most of the
last months trying to isolate it. There's some cool code for blowing
up queues in a repo of mine in particular.
So as for fixing 442...
I give up.
Disabling 802.11e entirely appears to fix it in some limited testing,
and as 802.11e is both broken conceptually and operationally, I don't
feel like trying to fix it anymore, I just want a stable release and
to move on to doing something - anything! else.
So hopefully the upcoming 3.10.40-4 build will be stable enough to
freeze on. If there is anything else that people want done before
freezing, let me know soonest.
In other news, availablilty of the 3800 series has dried up almost completely:
http://www.amazon.com/Netgear-WNDR3800-Premium-Gigabit-Wireless/dp/B0058NN6CS/ref=sr_1_1?s=electronics&ie=UTF8&qid=1400221440&sr=1-1&keywords=wndr3800
I have been evaluating multiple pieces of alternate hardware for years
now. In terms of a "continue with cerowrt-with-minimal-changes" play,
the
1) "tp-link archer c7 v2 ac1750" (the v2 part is critical) - uses a
mildly more powerful processor than the wndr3800, has the same amount
of flash and memory, 2 usb ports, and comes with an ath10k chip that
theoretically does 802.11ac with a proprietary firmware blob (but has
an ath9k for 2.4ghz operation). The performance of the ath10k sucks
rocks presently. It costs 99 bucks at frys.
I have been testing using one for a week now (with straight openwrt) and it's
pretty stable. It also doesn't live up to its billing - it can't
forward packets faster than 350mbits, only slightly better than the
wndr3800, and I figure it won't come close to 802.11ac speeds either.
In terms of finding something faster...
2) Am still waiting on the belkin wrt product to show up
3) am mostly hacking on x86 gear to get the speed I wanted to have
I just want a stable release, to sip boat drinks for a while, and try to come up
with a strategy to move forward from here that makes sense.
I'm open to ideas as to how to spend the next year more productively.
In other, other news, the ubnt edgerouter fq_codel test is going fairly well.
--
Dave Täht
next reply other threads:[~2014-05-16 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:36 Dave Taht [this message]
2014-05-16 19:59 ` Török Edwin
2014-05-16 20:54 ` Dave Taht
2014-05-17 6:54 ` Valdis.Kletnieks
2014-05-18 1:15 ` Aristar
2014-05-18 13:48 ` Valdis.Kletnieks
2014-05-18 15:29 ` Dave Taht
2014-05-19 7:30 ` Maciej Soltysiak
2014-05-19 9:57 ` Sebastian Moeller
2014-05-19 16:29 ` Dave Taht
2014-05-19 17:49 ` 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/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='CAA93jw48Po25+b1SgJKb=YBHixptSmO8z-7j2vqt9mc3k=hUkQ@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