[ale] Slightly OT: PI/Raspian Mesh Network Strategy?

[SpaXpert, Inc.]

This seems like a lot of overkill for a simple task these days.  All you
need is a wifi hotspot from a cell phone, and use a device like this:
https://squareup.com/us/en/hardware/terminal

On Fri, Jun 25, 2021 at 7:16 PM Neal Rhodes via Ale <ale at ale.org> wrote:

> So considering the following Physical layout:
>
> Business Comcast
>        |
> regular untinted Window in Building we can get Cat6 to
>        |
> 100 feet of parking lot
>        |
> Storage Building with power and overhang to protect from rain
>        |
> 150 feet of grass/trees - could run Cat6 wire easily
>        |
> Tent selling German beer with credit card readers needing Wifi (do I
> have your attention now?)
>
> And assuming we'd like for people to be able to buy beer, and we have a
> modest budget for networking, are there reasonable mesh networking
> products that would work?
>
> I have never put in a mesh network; if you read the fine print, they
> seem to assume all the nodes are clustered around a central node, not
> strung out in a line.   (i.e. no backhaul)
>
> I was initially advised to research ESP32 boards, but the paint doesn't
> seem quite dry on those.  More of a Proof-of-Concept than a real
> internet sharing strategy.
>
> OTOH, efforts to do that with Raspberry PI does seem like a real thing,
> eg
>
> https://github.com/binnes/WiFiMeshRaspberryPi/blob/master/README.md
>
> Which is extra handy for us, since we put up about a dozen PI units a
> people's homes for the Virtual Studio music thing, and aren't using them
> as much now.
>
> Has anyone does this and have results to report?
>
> regards,
>
> Neal
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> https://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20210625/7d5826b1/attachment.htm>