Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Christopher Robin <pheoni@gmail.com>
Cc: "dpreed@reed.com" <dpreed@reed.com>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Fri, 9 Jun 2017 07:02:47 -0700	[thread overview]
Message-ID: <CAA93jw6UjTKGTx4V7O97ZuoQqnNFQMUOnBeP=iHKrBaBLmxndw@mail.gmail.com> (raw)
In-Reply-To: <CAPjrEw8dRsScqy-r0qiLBEBKUNseqCyBwNCtB-MxM+P_yX54eA@mail.gmail.com>

My use case used to be covering hundreds of km in the Nicaraguan
jungle. The prototype for that covers a mere 110 acres in the los
gatos hills, trying to get stuff deep into ravines and so on.

I have at least a dozen areas where a wifi repeater would be useful,
but I tend to meshy route things, so rather than repeaters, I have
routers.

the ubnt radios I presently use tolerate 6-24v, and eat less than 5w -
so some of the things I've been watching rathole here don't apply.
What I'd hoped for was an "all-in-one unit" much like the wifi camera
that kicked off the thread.

I'm NOT going to put a wndr3800 in a tree, and while offering usb
recharging might be a good thing to a campsite, not planning on it at
the moment.

So I'm back to building a custom enclosure for edison batteries, a
solar panel hopefully lacking in charge controller, and a nanostation
m5 or rocket m5 as the gear.

>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.

  reply	other threads:[~2017-06-09 14:02 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
2017-06-09 14:02       ` Dave Taht [this message]
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='CAA93jw6UjTKGTx4V7O97ZuoQqnNFQMUOnBeP=iHKrBaBLmxndw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=pheoni@gmail.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