From: Outback Dingo <outbackdingo@gmail.com>
To: dpreed@reed.com
Cc: "Dave Täht" <dave@taht.net>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] hardware from hell
Date: Fri, 11 Mar 2016 12:34:42 +0100 [thread overview]
Message-ID: <CAKYr3zyEPFEiwD1_C+SDR9sUMGgE23Q4qnZsQw=+ZH6icp4qSg@mail.gmail.com> (raw)
In-Reply-To: <1457216936.047212077@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 2048 bytes --]
Hey Dave and Users
Just to let all know I am currwently in china so if theres any electronics
people would like sourced for testing let me know, nucs, compute sticks,
wireless routers / APs Im available to take orders and delivery, and
forward on to the states, or EU. I will be returning also to EU in about 8
weeks.
On Sat, Mar 5, 2016 at 11:28 PM, <dpreed@reed.com> wrote:
> My Jetway NU93-2930 board is a NUC with dual Ethernet. It's a bare board,
> but I made my own case quickly enough out of acrylic sheet using my bandsaw
> and glue. Works fine. Takes a wall wart power supply as long as it
> delivers between 12 V and 36 V.
>
> I recommend it highly. Jetway probably sells it in a case, as well, but I
> generally don't like their superexpensive cases.
>
> I added an mSATA drive (which mounts into the board) and RAM. That's all
> you need for a router with two GigE ports. There's also a slot under the
> mSATA slot for whatever mini-PCIe WLAN card you want - I'm not sure yet
> what I want to put on it, any suggestions for an 802.11ac capable with
> either 5 GHz or dual capability?)
>
>
>
>
> On Thursday, March 3, 2016 9:16pm, "Dave Täht" <dave@taht.net> said:
>
> > I am A) still fiddling with alternate web site generators and B) just
> > finished writing up (grousing) about all the hardware I just tried to
> > make work.
> >
> > http://the-edge.taht.net/post/hardware_from_hell/
> >
> > I am about to tear apart the dual ethernet nuc we discussed here, again,
> > swapping out everything in it to see if I can get it to work. I fear I
> > fried it by trying to compile a kernel on it, or something....
> >
> > _______________________________________________
> > 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: 2979 bytes --]
prev parent reply other threads:[~2016-03-11 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 2:16 Dave Täht
2016-03-04 2:47 ` Jonathan Morton
2016-03-04 3:03 ` Jonathan Morton
2016-03-04 3:11 ` Dave Taht
2016-03-04 4:48 ` Jonathan Morton
2016-03-04 12:27 ` Alan Jenkins
2016-03-04 21:57 ` Valent Turkovic
2016-03-05 16:08 ` moeller0
2016-03-05 10:09 ` Laurent GUERBY
2016-03-05 10:40 ` Sébastien Gaggini
2016-03-05 14:03 ` Outback Dingo
2016-03-05 22:28 ` dpreed
2016-03-11 11:34 ` Outback Dingo [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='CAKYr3zyEPFEiwD1_C+SDR9sUMGgE23Q4qnZsQw=+ZH6icp4qSg@mail.gmail.com' \
--to=outbackdingo@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=dpreed@reed.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