From: Guillaume Fortaine <guillaume.fortaine@devopspace.com>
To: William Katsak <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] supplies of the wndr3800 seem to be drying up
Date: Mon, 10 Dec 2012 21:18:16 +0100 [thread overview]
Message-ID: <CAOKokz9n-28wH5Lb_HW5jk0nrF3e1FBjT-uCyJJQ6BrLZSXrYw@mail.gmail.com> (raw)
In-Reply-To: <-5751424690361757427@unknownmsgid>
> Do we know what chip the 4300 (that Amazon is suggesting instead) is using?
http://www.wikidevi.com/wiki/Netgear_WNDR4300
CPU1: Atheros AR9344 (560 MHz)
On Mon, Dec 10, 2012 at 9:02 PM, William Katsak <wkatsak@gmail.com> wrote:
> Do we know what chip the 4300 (that Amazon is suggesting instead) is using?
>
> Bill Katsak
>
> Sent from my iPhone
>
> On Dec 10, 2012, at 2:11 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> 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
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2012-12-10 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 19:11 Dave Taht
2012-12-10 20:02 ` William Katsak
2012-12-10 20:18 ` Guillaume Fortaine [this message]
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=CAOKokz9n-28wH5Lb_HW5jk0nrF3e1FBjT-uCyJJQ6BrLZSXrYw@mail.gmail.com \
--to=guillaume.fortaine@devopspace.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=wkatsak@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