Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] WNDR alternative for higher capacity
Date: Sun, 09 Feb 2014 19:43:54 +0000	[thread overview]
Message-ID: <52F7DA7A.2060201@imap.cc> (raw)
In-Reply-To: <52F7D953.8080909@imap.cc>

[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]

Before you spend money, perhaps I should point out that Shuttle hardware 
has a reputation for poor reliability.


On 09/02/14 19:38, Fred Stratton wrote:
> http://www.amazon.co.uk/Shuttle-Ultra-DS47-Barebone-System/dp/B00DK06L6O
>
> Clicking on the pictures reveals a Realtek half-height wireless card.
>
>
> On 09/02/14 19:18, Toke Høiland-Jørgensen wrote:
>> Dave Taht<dave.taht@gmail.com>  writes:
>>
>>> At the moment what I think I'm trying to do is divide the problem in
>>> half, find a decent X86 based box with mini-pcie support, and solve
>>> the gigE problem that way, and the wifi problem separately.
>> Right, I was getting that impression.
>>
>>> The cost goes way up... The closest I've found so far to what I wanted
>>> was the latest nuc with sata support. Still want two hardwired
>>> ethernet ports which it doesn't have....
>> Actually, the Shuttle DS47 barebone seems to fit the bill on that score:
>> http://global.shuttle.com/products/productsDetail?productId=1718
>>
>> It's a celeron sandy bridge chip on the NM70 express chipset. Two
>> minipcie slots, one half size and one full size. It comes with a wlan
>> card in the half-size port, but can't find anywhere where it says which
>> one. Also it has a slot for a 2.5" drive (so you don't have to use the
>> big minipcie for msata), and dual Realtek 8111G Gbit ethernet. Even has
>> two external serial ports. The only thing missing is external antennae,
>> I think.
>>
>> Also not *that* pricey (compared to other x86 boxes). I can get it for
>> ~$290 retail here in Sweden (without disk and RAM)... Was going to go
>> for that unless someone comes up with a better idea :)
>>
>> -Toke
>>
>>
>> _______________________________________________
>> 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


[-- Attachment #2: Type: text/html, Size: 3818 bytes --]

  reply	other threads:[~2014-02-09 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 21:22 Toke Høiland-Jørgensen
2014-02-08 22:45 ` Dave Taht
2014-02-08 23:22   ` Toke Høiland-Jørgensen
2014-02-08 23:32     ` Fred Stratton
2014-02-09 17:22 ` Bill Merriam
2014-02-09 18:51   ` Toke Høiland-Jørgensen
2014-02-09 19:06     ` Dave Taht
2014-02-09 19:18       ` Toke Høiland-Jørgensen
2014-02-09 19:38         ` Fred Stratton
2014-02-09 19:43           ` Fred Stratton [this message]
2014-02-09 19:45           ` Dave Taht
2014-02-09 19:56           ` Toke Høiland-Jørgensen
2014-02-09 20:10             ` Dave Taht
2014-02-10 13:14       ` Rich 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=52F7DA7A.2060201@imap.cc \
    --to=fredstratton@imap.cc \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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