From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] USB3 or HDMI ethernet? - Are wires dead?
Date: Mon, 18 Apr 2016 16:10:52 -0700 [thread overview]
Message-ID: <CAA93jw7SquZKCVZsV85oW6ke3-e4UOc7Bh_W-dZiJta=oAV+Sg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw47yqrETEjC0w-5MFf+PA1q1FfP7LzEdG_zq2HtRMRX4w@mail.gmail.com>
On Mon, Apr 18, 2016 at 7:50 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I wanted to be able to do wifi aircaps at scale, So I figured I'd
> load up a nuc with a bunch of usb wifi sticks. I got a w(hole bunch of
> those - the horrors! the horrors that the drivers revealed...
>
> then I ran across the compute stick phenomenon,
>
> Holy cow, 59 dollars for an entire computer - with wifi on board.
>
> http://www.amazon.com/Intel-Compute-STCK1A8LFC-Z3735F-Ubuntu/dp/B00W7KAABK/ref=sr_1_1?ie=UTF8&qid=1460990238&sr=8-1&keywords=ubuntu+compute+stick
So I got one of these older models to play with. It came in a nice
box. It was marvelous to plug the male hdmi port directly into my
stereo A/V amp and have it automatically install and configure ubuntu
14.04LTS (kernel 3.16). It took a while to install itself, but after
about 15 minutes of updating I had got it up and running. It's pretty
neat as a desktop, not particularly fast, but once an app is loaded
it's "good enough" for day to day work.
I added a 19 dollar 32Gbyte SDHC card to use as my "home" directory,
as there is only about 5GB usable on the stick itself (71% of the
internal emmc used by default), bringing my total cost to under a
hundred bucks.
I played with it a bit...
Sound doesn't work, which eliminates my musical use case (at least for
now). I thought maybe this would be a good option for a midi
controller, also, might try that.
The wifi does ~10Mbits in my admittedly crowded spectrum. The linux
log fills with all sorts of RTL871X debug messages, and the thing is
about as bloated as the ath9k can be - 344-500ms delay on the up in
netperf.
The wifi is a realtek chip, ironically, I guess, intel couldn't fit
one of their wifi cards into it: rtl8723bs
And my original use case of having a compute stick I could use to
sample the air with? So far with various tools I haven't been able to
get a monitor interface to work. :(
Overall it's kind of nice to have an intel architecture box that costs
about the same as a tricked out raspberry pi. I'd like it if I could
power it via a conventional usb port and network it that way, but
haven't tried that yet.
I am tempted to pick up one of the windows versions to play with.
> --
> Dave Täht
> Save BoatyMcBoatFace from extinction by humorless science ministers!
> https://twitter.com/hashtag/boatymcboatface
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next parent reply other threads:[~2016-04-18 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw47yqrETEjC0w-5MFf+PA1q1FfP7LzEdG_zq2HtRMRX4w@mail.gmail.com>
2016-04-18 23:10 ` Dave Taht [this message]
2016-04-19 17:51 ` Dave Taht
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7SquZKCVZsV85oW6ke3-e4UOc7Bh_W-dZiJta=oAV+Sg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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