Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] notes on going for a stable release/replacement router
Date: Mon, 20 Jan 2014 10:15:26 -0500	[thread overview]
Message-ID: <6D274821-F312-49DB-BA76-995A6FBC1F98@gmail.com> (raw)
In-Reply-To: <CAMZR1YAaHrcU9AyZZpHn293D-trB4keX8hbL79fCH9jWy4i1kQ@mail.gmail.com>


On Jan 20, 2014, at 10:00 AM, Maciej Soltysiak <maciej@soltysiak.com> wrote:

> On Tue, Jan 14, 2014 at 7:07 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> ** The wndr3800 is obsolete and fixing the next generation soon would be good
> On wndr3800 being obsolete... I was asked recently for a router recommendation.
> I wanted to say WNDR3800, but do we have anything better that is still
> that hackable?

The WNDR3800 is still about $100 on Amazon today (in the US). If someone wants to install it this week, it's a good deal. It's eminently hackable, it has an astonishing development team that has really addressed home networking, and they can get the benefit of all that now.

>> But this past christmas everything was 802.11ac, running on arm. The
>> ath10k is out and getting some love, too.
> We still don't know the specs of WRT1900AC, do we?

I received an initial response from Linksys, who said that they were busy taking care of the details after the CES show. They promised to have someone get back to me who could speak to the technical details.

It's the MLK holiday here in the US, so they are probably not working. I'll ping them tomorrow.

> Best regards,
> Maciej

Rich

      reply	other threads:[~2014-01-20 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  6:07 [Cerowrt-devel] notes on going for a stable release Dave Taht
2014-01-14  8:37 ` Christopher Robin
2014-01-14  9:44   ` Toke Høiland-Jørgensen
2014-01-14 12:51     ` David Personette
2014-01-14 13:20       ` Rich Brown
2014-01-14 15:30         ` Dave Taht
2014-01-16  3:20         ` Theodore Ts'o
2014-01-15 15:18   ` Dave Taht
2014-01-14 12:10 ` Juergen Botz
2014-01-14 15:10   ` Dave Taht
2014-01-14 12:36 ` David Personette
2014-01-15  4:11   ` Dave Taht
     [not found]     ` <CAMybZqzs9ES9G23ke-PjU759wxbQNMytYa4EHmv0H8HqpPwwPQ@mail.gmail.com>
2014-01-15 14:47       ` Dave Taht
2014-01-15  0:30 ` David Lang
2014-01-15 17:31 ` Jim Reisert AD1C
2014-01-20 15:00 ` Maciej Soltysiak
2014-01-20 15:15   ` Rich Brown [this message]

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=6D274821-F312-49DB-BA76-995A6FBC1F98@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.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