From: Christopher Robin <pheoni@gmail.com>
To: "dpreed@reed.com" <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Tue, 06 Jun 2017 23:59:25 +0000 [thread overview]
Message-ID: <CAPjrEw8dRsScqy-r0qiLBEBKUNseqCyBwNCtB-MxM+P_yX54eA@mail.gmail.com> (raw)
In-Reply-To: <1496685154.544113991@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
> <dpreed@reed.com> wrote:
>You are not going to put a good enough system for an AP up in a tree.
Maybe on an antenna mast structure with solid base and guy wires. Roofs and
ground are better choices.
>But I would wonder whether redesigning the AP itself to be
power-conserving would be the place to start. They are not designed to be
"low power" - they are designed to be inexpensive.
Along these lines, would using cellphone chips be viable?
I'm trying to imagine a use case where decade long, maintenance free, tree
mounting would be the preferred solution. The only thing I can think of is
a cheap active repeater in an area with infrequent users. Push as much
logic/processing back to a unit where power is cheap.
-CR
>
[-- Attachment #2: Type: text/html, Size: 1048 bytes --]
next prev parent reply other threads:[~2017-06-06 23:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 0:49 Dave Taht
2017-06-05 1:54 ` Aaron Wood
2017-06-05 2:03 ` Dave Taht
2017-06-05 3:53 ` Aaron Wood
[not found] ` <148921.1496635376@turing-police.cc.vt.edu>
2017-06-05 4:27 ` Dave Taht
2017-06-05 13:12 ` Michael Richardson
2017-06-05 16:01 ` Richard Smith
2017-06-05 17:52 ` dpreed
2017-06-05 18:01 ` dpreed
2017-06-05 18:21 ` Jim Gettys
2017-06-05 18:53 ` Aaron Wood
2017-06-06 23:59 ` Christopher Robin [this message]
2017-06-09 14:02 ` Dave Taht
2017-06-13 11:52 ` Richard Smith
[not found] ` <CAPjrEw9FY9GU3XXMXDTi254nUUDdyVw22+9G-MKuT08ABtTJ9Q@mail.gmail.com>
2017-06-13 13:03 ` Christopher Robin
2017-06-13 16:25 ` Richard Smith
2017-06-13 17:25 ` Dave Taht
2017-06-13 21:09 ` Richard Smith
2017-06-05 20:20 ` David Lang
2017-06-05 20:26 ` Jim Gettys
2017-06-06 12:04 ` Richard Smith
2017-06-06 18:40 ` Richard Smith
2017-06-07 20:15 ` Michael Richardson
2017-06-05 21:51 ` Michael Richardson
2017-06-05 22:49 ` Joel Wirāmu Pauling
2017-06-06 2:00 ` Michael Richardson
2017-06-06 2:03 ` Jim Gettys
2017-06-06 12:04 ` Richard Smith
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=CAPjrEw8dRsScqy-r0qiLBEBKUNseqCyBwNCtB-MxM+P_yX54eA@mail.gmail.com \
--to=pheoni@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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