Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement
Date: Wed, 26 Mar 2014 15:11:55 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1403261455030.2190@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw7MTv0Hxv=dt6zm2CJg5-9QhtxXLxTFk0uk3Qy5mVWreQ@mail.gmail.com>

One item that has been very nice about the 3800 is the unbricking is so 
bulletproof. this looks like it has a similar capability.

also, the amazon review talks about it having a Freescale P1014 cpu

If the openwrt folks could figure out how they are going to deal with NAND 
flash, it would be nice to be able to use one of the many routers that is 
shipping with more flash (128M in the newer netgear routers would be nice)

if I were to get my hands on one, what sort of testing would you want to do to 
it to tell if it looks like it would hold up?

David Lang

On Tue, 25 Mar 2014, Dave Taht wrote:

> From: Mikael Abrahamsson
>
>
> What do you think of http://wiki.openwrt.org/toh/tp-link/tl-wdr4900 as
> wndr3800 replacement?
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
>
> + seems to have decent openwrt support, has anyone tried one?
>
> +/- I used to like powerpc. Then apple got off it. It seems like arm
> has most of the momentum nowadays.
> +/- I am mostly in search of something that can honestly hit gigE
> forwarding rates, and run htb
> at 500Mbits/sec. Don't know if ANYTHING has that amount of oomph besides x86.
> - I care about build quality and temp range for a long lasting device.
> The wndr3800 was flown to 120k feet,
> for example and I've seen it running in 100F+ weather. tp-link does
> not strike me as devices that do that.
>
> Other opinions welcomed.
>
>

  reply	other threads:[~2014-03-26 22:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.02.1403251259390.747@uplift.swm.pp.se>
2014-03-25 15:16 ` Dave Taht
2014-03-26 22:11   ` David Lang [this message]
2014-03-27 12:50     ` Aaron Wood
2014-03-27 14:39       ` David Lang
2014-03-28  8:36         ` Mikael Abrahamsson
2014-03-28  9:33           ` Sebastian Moeller
2014-03-28 13:30           ` Aaron Wood
2014-03-28 18:40           ` Michael Richardson
2014-03-28 19:39             ` Dave Taht
2014-03-28 21:01               ` Aaron Wood
2014-03-29 21:08               ` Michael Richardson
2014-03-29 21:25                 ` Dave Taht
2014-03-30 22:03                   ` Michael Richardson
2014-03-30 22:10                     ` Dave Taht
2014-03-28 19:14           ` Michael Richardson
2014-03-29 19:27 Martin Bailey
2014-03-29 19:52 ` Dave Taht
2014-03-29 19:56 ` Dave Taht
2014-03-29 20:19   ` Martin Bailey

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=alpine.DEB.2.02.1403261455030.2190@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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