From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] supplies of the wndr3800 seem to be drying up
Date: Mon, 10 Dec 2012 20:11:23 +0100 [thread overview]
Message-ID: <CAA93jw5afPgSnAW2Us8SD4_3Y432D4Fx6ppzqyvqcwuCdS46LA@mail.gmail.com> (raw)
I haven't seen the 3800 in any store for months. It's not at
frys...there are only two available via amazon...
too bad, we're almost done debloating it, with just the wifi left to go.
I've been dreading this... I know there are tons of other routers on
the market with this chipset, but I imagine those will dry up soon,
too.... suggestions?
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2012-12-10 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 19:11 Dave Taht [this message]
2012-12-10 20:02 ` William Katsak
2012-12-10 20:18 ` Guillaume Fortaine
2012-12-17 10:09 ` David Lang
[not found] <mailman.4.1355774401.18176.cerowrt-devel@lists.bufferbloat.net>
2012-12-17 20:26 ` Richard Brown
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=CAA93jw5afPgSnAW2Us8SD4_3Y432D4Fx6ppzqyvqcwuCdS46LA@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