From: Steve Newcomb <srn@coolheads.com>
To: Ben Greear <greearb@candelatech.com>,
b.a.t.m.a.n@lists.open-mesh.org, smartwires@gmail.com
Subject: Re: Network stops passing traffic randomly
Date: Wed, 3 Jun 2020 13:56:32 -0400 [thread overview]
Message-ID: <310fffa6-ff96-cb48-355f-00e773c1a4d7@coolheads.com> (raw)
In-Reply-To: <3659b31b-1f8b-1e21-43f5-b47f6e11d338@candelatech.com>
On 6/3/20 12:42 PM, Ben Greear wrote:
> If you are trying to lift up a broad swath of the world, then you need
> scale and vision, and part of that is how
> to make it self sustaining. Giving a few crumbs to folks is less
> useful in my mind than helping give them the means
> to make their own bread. Think someone starting a company that wants
> to deploy 10k hotspots with 40k satellite
> wifi mesh nodes....
Your vision is deeply correct, but so is mine. One difference between
the two ideas is that yours is top-down, with the purpose of offering a
service, while mine is bottom-up, with the purpose of developing
community and neighborliness, regardless of service provider(s). (I'm
an admirer of the late Fred Rogers, and I'm not ashamed to admit it.)
But you are right, too. I'm also an admirer of the Indian cataract
surgery guy (can't remember his name) who insisted that all patients pay
for their surgery "because charity doesn't scale". He ultimately built
a mind-boggling practice that, among other things, presumably now
manufactures most of the world's intraocular lenses.
>
> Open source software (and maybe hardware) with high volume,
> affordable, and solid hardware
> is one of the core aims of TIP. Think of a price and minimum hardware
> that meets your goals,
> if I find someone that can make such a thing at such a price, I'll let
> you know.
Fair enough. How about a *delivered* price, i.e. an out-of-pocket cost,
of $50. Obviously a minimum of 2 radios, 128 Mb, and reasonable CPU
power. Since we're forward-looking, here, with support for the new
channels now presumably forthcoming from the FCC.
> If you want wave-1 ath10k to mesh, my advice is to use 7 virtual
> station vdevs and one AP on each radio. ath10k-ct
> firmware and software will support this nicely. Have those 7 stations
> connect to peers' AP vdevs. Do routing mesh
> magic through this topology. Then you don't care about anything other
> than STA + AP working. This might also scale to other platforms
> that don't support IBSS or MESH well.
Many thanks, Ben. This is a helpful idea, and I daresay not many people
could have come up with it. (Certainly not I!) You have just given me
some homework to do, and I'm grateful for it. Bravo. If I get anywhere
with it, you'll be the first to know.
Steve
prev parent reply other threads:[~2020-06-03 17:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 8:35 Network stops passing traffic randomly smartwires
2020-05-25 8:43 ` Sven Eckelmann
[not found] ` <CAL3ir7+RWLrYOzjNQh1VwiKg1sxSgHZMwwqx=9xSfXFnFjE_KQ@mail.gmail.com>
2020-05-25 13:22 ` Sven Eckelmann
2020-05-25 13:45 ` Sven Eckelmann
2020-05-28 1:05 ` smartwires
2020-05-28 8:46 ` Sven Eckelmann
[not found] ` <cf75d66e-b0ac-632d-34e6-681ed9c6769d@coolheads.com>
2020-05-28 19:31 ` Sven Eckelmann
2020-05-28 21:17 ` Steve Newcomb
2020-05-28 19:03 ` Steve Newcomb
2020-05-28 19:19 ` Sven Eckelmann
2020-05-28 19:22 ` Ben Greear
2020-05-28 20:59 ` Steve Newcomb
2020-05-28 21:28 ` Ben Greear
2020-06-02 1:41 ` Steve Newcomb
2020-06-02 12:40 ` Steve Newcomb
2020-05-29 0:13 ` smartwires
2020-06-02 2:05 ` Steve Newcomb
2020-06-02 20:02 ` Ben Greear
2020-06-03 2:06 ` Steve Newcomb
2020-06-03 12:48 ` Ben Greear
2020-06-03 15:35 ` Steve Newcomb
2020-06-03 16:42 ` Ben Greear
2020-06-03 17:56 ` Steve Newcomb [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=310fffa6-ff96-cb48-355f-00e773c1a4d7@coolheads.com \
--to=srn@coolheads.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=greearb@candelatech.com \
--cc=smartwires@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