Hello Folks,
It has been several days now that I am not on PON. The private network is
fine, it is just the mesh side that is down.
And, I feel that perhaps the latest patches may have broke this particular
node model. I have a TP-Link TL-WDR3500.
If someone in this list has the same node model, please, let me know if
yours is working.
Many thanks in advance,
--
Daniel Arauz
Signal Messenger: 415.336.9143 <https://www.signal.org/>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - -
Please donate to help Escuela Chajsaquil Recover From Flood <3
https://www.youcaring.com/help-escuela-chajsaquil-recover-from-flood
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - -
You have all probably already heard about the wifi KRACK attack. If not,
here is the lowdown:
https://www.krackattacks.com/
sudowrt is also affected. What this means is that your private wifi network
is... potentially a lot less private.
I started work on a fix here:
https://github.com/sudomesh/sudowrt-firmware/issues/109
but I ran into a build issue which maybe Grant knows how to fix?
https://github.com/sudomesh/sudowrt-firmware/issues/110
Hopefully we can sort this out over the next day or two.
In the mean time node-operates may want to disconnect any sensitive devices
from their private network. As always you should be using end-to-end
encryption for all communications. Install the HTTPS Everywhere
<https://www.eff.org/https-everywhere> browser extension if you haven't.
For situations where end-to-end encryption is not viable, using a VPN like
Mullvad <https://www.mullvad.net/> is a good idea.
--
marc/juul
Hi y'all,
So I've been out of touch for a little while. During my trip, I had a lot
of time to clear my head and talk with people outside our little bubble in
the Bay. Specifically, I had the good grace to meet with some of the folks
working on TOmesh in Toronto. They had lots of great ideas and an
interesting perspective on what it means to be a "mesh network project",
I'm excited to get back to Oakland and try to share some of their thoughts.
Anyway, one idea from TOmesh I really liked, was the their mission to make
all of their hardware, software, and code entirely ship-able. It's an idea
that has bounced around our group a number of times under the nym,
"mesh-in-a-box". For us, we are so far along, that we would have to
completely rethink, or at least simplify, our project to make it fit in a
box (quite literally). TOmesh has the benefit of being a younger project,
but also they started, from my understanding, with different base
assumptions. That is, they did not assume that everyone has access to (or
knows how to use) git or can reach openwrt packages or fulfill docker's
strange dependencies (an irony considering docker's raison d'etre). So they
have assumed positions as educators, teaching the skills and concepts
related to networking, privacy, and security with a limited focus on the
real, physical implementation.
Then I saw the recent difficulties with building the firmware. This all got
me thinking about the way we share knowledge and collaborator with one
another. It has also has encouraged me to propose a project that has been
mentioned countless times. I would like to try building a firmware building
machine. I realize some of the group might see this as constructing big-bad
centralized-server that controls all the firmware running on the mesh.
However, I encourage you to read my proposed requirements or add your own
to the issue or by responding to this email thread.
https://github.com/sudomesh/sudowrt-firmware/issues/111
I've previously worked on similar projects (albeit in a Windows
environment), and I think I'll have a good amount of time to work on it
come November(post-disaster radio proposal). We'll be needing help with
hardware selection, *nix sys admin knowledge, and content creation and
documentation writing.
Key to this idea, is that it should not be seen as centralized solution to
a decentralized problem, but rather a way of off-loading some of the
knowledge currently centralized in a few individuals.
Hope everyone is doing well in the Bay, I look forward to getting back.
Thanks,
-grant_____(@paidforby)
So there is not much bandwidth beyond text, but what would be the difference between more bandwidth? Is it simply a space/antennae size issue or can this be tackled with software?
Is anyone coordinating satellite launches for our own antennae into space yet? Do you have a minimum size/effectual range quotient?
Sending all my love sudo
A
Thanks for this good advice, Marc!
Meanwhile I will be out for a few weeks, sick this week & running
weirdfilmfest next Tuesday, and possibly/probably in Unsafe Networks, where
the advice will come in handy.
On Wed, Oct 18, 2017 at 12:00 PM, <mesh-request(a)lists.sudoroom.org> wrote:
> Send mesh mailing list submissions to
> mesh(a)lists.sudoroom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://sudoroom.org/lists/listinfo/mesh
> or, via email, send a message with subject or body 'help' to
> mesh-request(a)lists.sudoroom.org
>
> You can reach the person managing the list at
> mesh-owner(a)lists.sudoroom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mesh digest..."
>
>
> Today's Topics:
>
> 1. KRACK attack (Marc Juul)
> 2. Re: KRACK attack (danarauz(a)gmail.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 17 Oct 2017 15:52:57 -0700
> From: Marc Juul <juul(a)labitat.dk>
> To: "mesh(a)lists.sudoroom.org" <mesh(a)lists.sudoroom.org>
> Subject: [Mesh] KRACK attack
> Message-ID:
> <CAL4ejvQ4hPDyuMGDWwKd4wL-c0ZTLtP28+mde7dqo2b2=RQ01A@
> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> You have all probably already heard about the wifi KRACK attack. If not,
> here is the lowdown:
>
> https://www.krackattacks.com/
>
> sudowrt is also affected. What this means is that your private wifi network
> is... potentially a lot less private.
>
> I started work on a fix here:
>
> https://github.com/sudomesh/sudowrt-firmware/issues/109
>
> but I ran into a build issue which maybe Grant knows how to fix?
>
> https://github.com/sudomesh/sudowrt-firmware/issues/110
>
> Hopefully we can sort this out over the next day or two.
>
> In the mean time node-operates may want to disconnect any sensitive devices
> from their private network. As always you should be using end-to-end
> encryption for all communications. Install the HTTPS Everywhere
> <https://www.eff.org/https-everywhere> browser extension if you haven't.
> For situations where end-to-end encryption is not viable, using a VPN like
> Mullvad <https://www.mullvad.net/> is a good idea.
>
> --
> marc/juul
>
