From: Aaron Wood <woody77@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: wndr3800 replacement
Date: Fri, 28 Mar 2014 14:30:03 +0100 [thread overview]
Message-ID: <CALQXh-NDRVJ6RQnRdP5NomHsULeyVaFQWU7EFLy4QLjm2S6pRA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403280933530.747@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
On Fri, Mar 28, 2014 at 9:36 AM, Mikael Abrahamsson <swmike@swm.pp.se>wrote:
> On Thu, 27 Mar 2014, David Lang wrote:
>
> using a 3800 or similarly priced ($100-$150 USD) device that's readily
>> available is very good for the second category, the question is if we can
>> find one that's powerful enough for the first.
>>
>
> I would say that it would be desireable to have a device that is available
> world-wide, that doesn't have a lot of different versions of the hardware
> that are different.
>
> I also think that it'll be very hard to find a box that is decently priced
> that also will do gig speeds *and* will do AQM, since most home gateways
> that are this quick has hardware acceleration that in turn requires vendor
> proprietary kernels to drive the hardware.
>
> So if you want to fulfil both, I think we need two platforms. A CPU based
> platform that is quick enough to do AQM in and CPU forwarding in gig speeds
> will most likely have to be Intel based and cost 300 USD or more.
>
Certainly difficult when you bring being a Wifi AP into the mix. This is
where a two-box solution might work better, running something like the wndr
as an internal router/AP, and using a separate box for the high-speed AQM
for the edge routing? A dual-port GigE platform seems like it would be
easier to find (or build via mini-itx).
I'm nearly certain that something like a dual- or quad-codre i.MX6 at >1GHz
could do the work, but those just aren't available in a "home router"
package, which is the killer. The fact that the home routers are commodity
products, and built to cost with a very narrow feature set makes it
exceedingly difficult to locate platforms that are viable for
experimentation.
Basically, we need a high-performance-networking version of a Raspberry Pi.
-Aaron
[-- Attachment #2: Type: text/html, Size: 2367 bytes --]
next prev parent reply other threads:[~2014-03-28 13:30 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
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 [this message]
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=CALQXh-NDRVJ6RQnRdP5NomHsULeyVaFQWU7EFLy4QLjm2S6pRA@mail.gmail.com \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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