So it's true, my home node is plugged into my comcast, which is presently
working. And i'm presently on the private network and my IP address is
172.30.0.172 and everything is working. And I can ssh into the home node.
but if i connect to the "peoplesopen.net 65.146.129" network, I can ping the
router at 100.65.146.129 but I can't ping anywhere else, even 8.8.8.8
the monitor shows it in the map and it seems to be directly connected to a
bunch of other nodes.
any ideas what's going on? …
[View More]Should I run any commands in the shell on the home
node? I ran babeld -i and ip route and these are the results:
root@sudomesh-node:~# babeld -i
Listening on interfaces: l2tp0 mesh2 mesh5 eth0.1 eth0.2
My id 02:90:a9:ff:fe:ae:8c:61 seqno 16739
Neighbour fe80::641f:aff:fe3a:bffb dev l2tp0 reach ffff rxcost 96 txcost 96 rtt 0.000 rttcost 0 chan -2.
Neighbour fe80::de9f:dbff:fe15:5eb3 dev eth0.2 reach ffff rxcost 96 txcost 96 rtt 0.000 rttcost 0 chan -2.
100.65.146.128/26 metric 128 (exported)
0.0.0.0/0 metric 831 (729) refmetric 735 id 06:01:52:ff:fe:32:8a:01 seqno 64122 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
10.12.0.0/16 metric 831 (739) refmetric 735 id 06:01:52:ff:fe:32:8a:01 seqno 64122 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.64.0.42/32 metric 96 (96) refmetric 0 id 02:a0:d1:ff:fe:e7:a0:74 seqno 51025 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.64.22.64/26 metric 320 (320) refmetric 224 id 62:e3:27:ff:fe:72:62:c3 seqno 33549 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.64.36.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0e:38:ab seqno 29920 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.64.54.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:77:3b seqno 27507 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.17.192/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0d:c1:01 seqno 58007 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.38.128/26 metric 1184 (1094) refmetric 1088 id 02:90:a9:ff:fe:0b:ce:51 seqno 32658 chan (255) age 16 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.41.64/26 metric 927 (835) refmetric 831 id 02:90:a9:ff:fe:0c:6c:ab seqno 40148 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.91.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6e:1b seqno 999 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.95.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:4b:bb seqno 32853 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.96.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6e:a6 seqno 24597 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.97.64/26 metric 927 (837) refmetric 831 id 02:90:a9:ff:fe:0c:6c:1b seqno 48619 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.98.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6d:66 seqno 46253 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.98.2/32 metric 288 (288) refmetric 192 id 02:27:22:ff:fe:52:43:3b seqno 7735 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.99.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:05:ef:c6 seqno 14092 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.99.66/32 metric 288 (288) refmetric 192 id 26:a4:3c:ff:fe:b8:a9:cd seqno 27268 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.127.128/26 metric 735 (638) refmetric 639 id 02:90:a9:ff:fe:0c:4d:cb seqno 44003 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.127.130/32 metric 703 (606) refmetric 607 id 06:18:d6:ff:fe:4b:90:e6 seqno 32090 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.127.131/32 metric 511 (418) refmetric 415 id 02:27:22:ff:fe:1e:60:da seqno 57966 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.131.192/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6b:b6 seqno 5647 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.132.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6c:e6 seqno 39294 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.133.64/26 metric 927 (827) refmetric 831 id 02:90:a9:ff:fe:0c:6e:31 seqno 12454 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.137.128/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:11:f1:c1 seqno 65256 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.139.128/26 metric 416 (416) refmetric 320 id 02:90:a9:ff:fe:0b:dd:cb seqno 23212 chan (255) age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.141.128/26 metric 1308 (1209) refmetric 1212 id 02:90:a9:ff:fe:09:a7:8b seqno 13030 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.141.131/32 metric 1276 (1174) refmetric 1180 id 6a:72:51:ff:fe:54:9d:1a seqno 59841 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.141.192/26 metric 2414 (2308) refmetric 2318 id 02:90:a9:ff:fe:ae:98:b6 seqno 579 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.141.195/32 metric 1851 (1757) refmetric 1755 id 6a:72:51:ff:fe:54:9c:78 seqno 18873 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.143.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:12:07:cb seqno 18624 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.144.64/26 metric 1146 (1041) refmetric 1050 id 02:90:a9:ff:fe:0b:dc:a6 seqno 3005 chan (255) age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.145.128/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:6b:86 seqno 27913 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.146.131/32 metric 96 (96) refmetric 0 id de:9f:db:ff:fe:14:5e:b3 seqno 64557 age 1 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
100.65.148.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0c:70:bb seqno 23511 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.148.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0a:f5:51 seqno 32644 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.159.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0b:dd:a1 seqno 13573 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.159.2/32 metric 288 (288) refmetric 192 id 26:a4:3c:ff:fe:b8:b2:b3 seqno 63433 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.160.192/26 metric 416 (416) refmetric 320 id 02:90:a9:ff:fe:0c:6d:86 seqno 1951 chan (255) age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.161.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0b:dd:d6 seqno 48380 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.162.64/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:cb:ce:3b seqno 23331 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.165.0/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:cd:15:46 seqno 48317 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.165.128/26 metric 320 (320) refmetric 224 id 02:90:a9:ff:fe:0b:dc:fb seqno 34400 age 2 via l2tp0 neigh fe80::641f:aff:fe3a:bffb nexthop 100.64.0.42 (installed)
100.65.166.128/26 metric 927 (838) refmetric 831 id 02:90:a9:ff:fe:a6:0a:06 seqno 58957 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
107.170.208.0/20 metric 831 (739) refmetric 735 id 06:01:52:ff:fe:32:8a:01 seqno 64122 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 nexthop 100.65.146.131 (installed)
2604:a880:1:20::/64 metric 831 (730) refmetric 735 id 06:01:52:ff:fe:32:8a:01 seqno 64122 chan (255) age 19 via eth0.2 neigh fe80::de9f:dbff:fe15:5eb3 (installed)
root@sudomesh-node:~# ip route
default via 10.0.0.1 dev eth1 proto static src 10.0.0.163
10.0.0.0/24 dev eth1 proto kernel scope link src 10.0.0.163
10.0.0.1 dev eth1 proto static scope link src 10.0.0.163
100.65.146.128/26 dev br-open proto kernel scope link src 100.65.146.129
172.22.0.0/24 dev eth1 proto kernel scope link src 172.22.0.1
172.30.0.0/16 dev br-priv proto kernel scope link src 172.30.0.1
root@sudomesh-node:~#
On Sun, 5 Apr 2020, Benny Lichtner wrote:
> Hey, Jake.
>
>> My node should be connecting to an extender on the roof, and
> then to an extender on livelabs roof, and then to The Internet, and then to
> an
> exit node?
>
> Yep that sounds plausible. But...
>
> When I hover over your node (65.146.129) it appears to be directly
> connected to the orange exit node. So I think you do have a direct
> connection to the internet. Is that possible?
>
> The diagram is based entirely on the routing table entries at each exit
> node (these are the big tables below the diagram).
>
> The diagram has been getting pretty crowded and hard to read. I just pushed
> an update that makes it easier to read which nodes are connected where.
> (Thank you for motivating this!)
>
> --Benny
>
> On Sun, Apr 5, 2020, 1:00 AM Jake <jake(a)spaz.org> wrote:
>
>> thank you, I see it now.
>>
>> i guess i just don't understand how the network works, or how the
>> diagram works. My node should be connecting to an extender on the roof,
>> and
>> then to an extender on livelabs roof, and then to The Internet, and then
>> to an
>> exit node?
>>
>> On Sun, 5 Apr 2020, Marc Juul wrote:
>>
>>> I don't know but it's there now. See attachment.
>>>
>>>
>>> On 4/3/20, Jake <jake(a)spaz.org> wrote:
>>>> Hi, I just saw this post to the consensus list and went to the
>> monitor...
>>>>
>>>> but i don't see my node on the chart?
>>>> peoplesopen.net fast 65.146.129
>>>>
>>>> i'm connected to it right now and it's working. It doesn't have a
>> direct
>>>> line
>>>> to "the internet" at my house, but rather beams through an extender
>> node to
>>>> livelabs.
>>>>
>>>> why isn't it on the chart?
>>>>
>>>> -jake
>>>>
>>>> On Fri, 3 Apr 2020, Squeesh wrote:
>>>>
>>>>> Hi everyone from the delegates meeting and other assorted omninoms! It
>> was
>>>>> good to talk with you last night. If you guys want to see the nodes
>>>>> currently online and how they are connected to one another, go to
>>>>> peoplesopen.net/monitor. Here's the jitsi link for our Tuesday
>> informal
>>>>> [sudomesh hangout, discussion, and question
>>>>> time!](https://meet.jit.si/sudomesh2020)
>>>>>
>>>>> In solidarity,
>>>>> L
>>>>>
>>>>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>>> _______________________________________________
>>>> mesh mailing list
>>>> mesh(a)lists.sudoroom.org
>>>> https://sudoroom.org/lists/listinfo/mesh
>>>>
>>>
>> _______________________________________________
>> mesh mailing list
>> mesh(a)lists.sudoroom.org
>> https://sudoroom.org/lists/listinfo/mesh
>>
>
[View Less]
I am trying to hook up to Monkeybrains without making them come get on my roof,
and perhaps without paying as much for installation fees.
They say that my end would have to be either be a Mikrotik Wireless Wire or a
Ubiquiti NanobeamAC so I want to know if peoplesopen/sudomesh has one of those
laying around or if anyone on this list has one.
MB says they "do not allow client equipment for security reasons as well as QOS
reasons for the rest of the customers" but if there's gear available to …
[View More]me then
i'll ask for an exception, and of course give them root and let them lock me
out of it. I'm just trying to avoid making them get on my roof since they said
they're not doing installs right now except for those who are "desperate" which
of course we are (mostly my Teacher housemate who is having trouble streaming
lessons) but I don't want to invoke that.
so... anyone have either be a Mikrotik Wireless Wire or a
Ubiquiti NanobeamAC?
thank you
-jake
(415)533-3699
[View Less]
Hello Folks,
I know this is off topic, but COVID-19 is not discriminating, and or
waiting for us.
I am volunteering with a small group trying to get ventilators (in the
thousands) to our folks in NewYork, but it is being difficult task.
Right now *we need *find out the *European CE Certification Number for each
*of the following two items:
- *Aeomed VG 60*
- *Aeomed VG 70*
I have contacted the EU Trade commission and I was informed that their
database doesn't have that kind of …
[View More]information. But, it should be found on
the devices themselves, as part of their requirements. Please forward this
email to anyone that you may think can help us to gather this information.
Also, while on it, we are looking for a warehouse in NYC were the supplies
can be stored.
Many thanks for your help, and stay safe.
Daniel
Signal/WhatsApp: 413.336.9143
*For more direct emails, please use: danarauz(a)protonmail.com
<danarauz(a)protonmail.com>.*
[View Less]
Hey guys,
Sudomesh party is happening tonight, online at:
https://meet.jit.si/sudomesh2020
It's informal, so let's ask questions, discuss new hardware, and imagine
what we want to be in the future.
In solidarity,
L
Hello!
My sons friend is in need of internet access to be able to attend school.
Is there any way you can help him?
On Sun, Apr 5, 2020 at 12:02 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)…
[View More]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. Re: sudomesh peoplesopen monitor (Jake)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 5 Apr 2020 01:00:02 -0700 (PDT)
> From: Jake <jake(a)spaz.org>
> To: Marc Juul <marc(a)juul.io>
> Cc: Squeesh <squeesh(a)protonmail.com>, mesh(a)lists.sudoroom.org
> Subject: Re: [Mesh] sudomesh peoplesopen monitor
> Message-ID: <alpine.BSF.2.21.999.2004050059020.47622(a)pe710.spaz.org>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> thank you, I see it now.
>
> i guess i just don't understand how the network works, or how the
> diagram works. My node should be connecting to an extender on the roof,
> and
> then to an extender on livelabs roof, and then to The Internet, and then
> to an
> exit node?
>
> On Sun, 5 Apr 2020, Marc Juul wrote:
>
> > I don't know but it's there now. See attachment.
> >
> >
> > On 4/3/20, Jake <jake(a)spaz.org> wrote:
> >> Hi, I just saw this post to the consensus list and went to the
> monitor...
> >>
> >> but i don't see my node on the chart?
> >> peoplesopen.net fast 65.146.129
> >>
> >> i'm connected to it right now and it's working. It doesn't have a
> direct
> >> line
> >> to "the internet" at my house, but rather beams through an extender
> node to
> >> livelabs.
> >>
> >> why isn't it on the chart?
> >>
> >> -jake
> >>
> >> On Fri, 3 Apr 2020, Squeesh wrote:
> >>
> >>> Hi everyone from the delegates meeting and other assorted omninoms! It
> was
> >>> good to talk with you last night. If you guys want to see the nodes
> >>> currently online and how they are connected to one another, go to
> >>> peoplesopen.net/monitor. Here's the jitsi link for our Tuesday
> informal
> >>> [sudomesh hangout, discussion, and question
> >>> time!](https://meet.jit.si/sudomesh2020)
> >>>
> >>> In solidarity,
> >>> L
> >>>
> >>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
> >> _______________________________________________
> >> mesh mailing list
> >> mesh(a)lists.sudoroom.org
> >> https://sudoroom.org/lists/listinfo/mesh
> >>
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> mesh mailing list
> mesh(a)lists.sudoroom.org
> https://sudoroom.org/lists/listinfo/mesh
>
>
> ------------------------------
>
> End of mesh Digest, Vol 87, Issue 3
> ***********************************
>
[View Less]
>We made the decision based on increasing concerns around COVID-19 and
calls from public health officials
>to cancel any public events that could further spread the virus.
Smart and considerate move.
Hi there,
I wanted to make sure those of us on this list are aware that we (Tracy of Media Alliance and a few of us at Sudo Mesh) decided to postpone the Build Your Own Internet event, which was scheduled to take place this Sat March 14.
We made the decision based on increasing concerns around COVID-19 and calls from public health officials to cancel any public events that could further spread the virus. It also did not seem wise, strategically, to hold a panel discussion about the Oakland …
[View More]Internet Choice ordinance when local lawmakers are plenty distracted by this public health crisis. We hope to check back in 2 weeks from now and see about potentially having the event late April if things have blown over by then (fingers crossed).
We hadn't done a great job publicizing this event anyway, so I'm fairly confident that most people didn't even know about it to begin with. However, please let others know that it's not happening if you have told others about the event.
Stay safe out there.
best,
Mai
[View Less]
Apparently David and Niki's house has an antenna partially set up but it
was never turned on. Anybody know what happened or how to get it finished?
Thanks!
Hi,
I'd like to suggest that sudo mesh purchase the following hardware for
research and development purposes:
2 x Mikrotik hAP ac lite (~2 x $50 ~ $100) -
https://www.amazon.com/MikroTik-Dual-concurrent-Access-Point-RB952Ui-5ac2nD…
1 x MikroTik hAP AC RouterBoard (~$125) -
https://www.amazon.com/MikroTik-RouterBoard-Triple-802-11ac-RB962UiGS-5HacT…
Also, one of the APU routers from PC Engines, with the additional
peripherals, all listed below:
Qty Part Description Price Extension Weight …
[View More]HTS Origin
1 - apu4d4 APU.4D4 system board 4GB $ 120.00 $ 120.00 237 8471.5000 TW
1 - case1d4blku Enclosure 4 LAN, black, USB $ 10.00 $ 10.00 256 8473.3000 CN
1 - satacab1 SATA data + power cable $ 1.50 $ 1.50 11 8473.3000 CN
1 - brk1d Wall mount kit for case1d $ 1.50 $ 1.50 54 8473.3000 CN
1 - assy Preassembly $ 6.50 $ 6.50 0 8471.5000 CH
Shipping (TBD) $ 0.00
Total $ 139.50 558 g
Grand total ~ $400
- Matt
[View Less]
Hey meshers,
Come check out this event where I'll be on a panel called "The Future of
the Internet: Protocols vs. Platforms" in SOMA on Thurs Feb 20 6:30pm. It's
free!
I'll be joined by Mike Masnick (Techdirt), Cory Doctorow, Ashley Tyson
(Web3 Foundation). The Lincoln Network, the organization putting it on, is
a tech-libertarian non-profit think tank so there might be some
conservative folks there. Wanted more of you to show up and support and
help me make those other audience members …
[View More]uncomfortable! lulz.
Here's the link to register:
https://www.eventbrite.com/e/the-future-of-the-internet-protocols-vs-platfo…
Hope to see some of you there!
Mai
- - -
*Mai Ishikawa Sutton*
*writer / organizer / artist*
*she/her/they/them pronouns*
[View Less]
Hey Meshers,
In case you don't know: Omni urgently needs help fixing up the building ahead of a visit from the insurance company on Thursday Feb 13. If Omni gets dropped from its insurance policy, it's likely that we might lose the building... D:
SOOoo. There's a big list of tasks that need doing and so I'm rallying a group of us to help knock those tasks out! Come by for any amount of time and help Sudo Mesh show up for Omni.
WHAT: Let's fix up Omni!
WHEN: 1-7pm Sunday Feb 9
WHERE: Omni, …
[View More]obvs
HOW: Wear clothes you can get dirty in, or even paint a building in.
If you can't find us, feel free to ping me on Rocketchat: https://peoplesopen.net/chat/ (https://peoplesopen.net/chat/)
My handle on there is @iamai
Hope you can make it!
Mai
[View Less]
I plan to come :)
WHAT: Let's fix up Omni!
> WHEN: 1-7pm Sunday Feb 9
> WHERE: Omni, obvs
> HOW: Wear clothes you can get dirty in, or even paint a building in.
>
>
(ORCA is Oakland ham radio club)
---------- Forwarded message ----------
From: *Judi KK6ZCU* <kk6zcu(a)manymedia.com>
Date: Tuesday, January 14, 2020
Subject: [ORCA] In case you're interested in the Bay area mesh thing...
To:
This Friday, January 17th, 7 PM at the San Francisco Veterans Administration
Building 7:
Kiley KD8DRX & Greg W2GMD will present the San Francisco Wireless Emergency
Mesh project.
We'll cover the basics of "How we got here?", "Why we're building this?",
"Who …
[View More]will use it?" and most importantly "Why is crimping ethernet jacks so
triggering for Greg?"
This presentation is open to all interested parties, regardless of SF Radio
Club membership.
Bonus, we'll have hardware available for anyone interested in connecting to
the mesh, and we'll be on hand to help you flash & configure your hardware
at
our Flash Party afterwards.
Directions and more information on the SFRC meeting can be found
at: https://www.sfarc.org/map--directions.html [1]
More information on the San Francisco Wireless Emergency Mesh can be found
at: http://www.sfwem.net/ [2]
Thanks, see you Friday!
| LINK: https://www.arednmesh.org/content/friday-friday-friday-
lets-get-meshy
[View Less]
Hey there,
*Just in case* there was someone who was planning to attend the Sudo Mesh meeting tonight (Dec 24) or Dec 31, we are officially cancelling those meetings due to the holidays. Of course people are welcome to show up and still hack on stuff but just know that all the regulars say there will not be there. :P
Hope y'all have a relaxing and warm holidays!
cheers,
Mai
hey folks,
made a troubleshooting section on the walkthrough, please add other cases
of issues and how you resolved them!
Just got this n600 flashed that had had the rest button fall off. Back on
there and working fine now.
https://sudoroom.org/wiki/Mesh/WalkThrough#Troubleshooting
- Matt
Would love to put together some proposals for AMC next year!
---------- Forwarded message ---------
From: Allen Gunn via devsummit list <devsummit(a)lists.aspirationtech.org>
Date: Fri, Dec 13, 2019, 03:59
Subject: [devsummit] AMC Call for Proposals
To: Dev Summit Discussion <devsummit(a)lists.aspirationtech.org>
Hi friends,
Call for Proposals is open for Allied Media Conference 2020.
I can't say enough nice things about what a great event this is, and
2020 will be a unique …
[View More]year, as they took a year off to recharge and
rethink everything about the event.
The proposal info is here:
https://www.alliedmedia.org/amc/propose-session
peace,
gunner
--
Allen Gunn
Executive Director, Aspiration
www.aspirationtech.org
Aspiration: "Better Tools for a Better World"
Read our Manifesto: https://aspirationtech.org/publications/manifesto
Twitter: www.twitter.com/aspirationtech
[View Less]
>From what I understand, Western Digital has dropped their line of My Net
products, and instead is supporting My Cloud devices. Those will be really
fun to hack on later on as they get old and cheap (especially for
distributed networking projects, no?) WD has already stopped offering
support for the My Net products and have definitely stopped selling them.
So eventually we will also run out of n600 and n750 stock. Plus, the price
has gone up to near-MSRP for the n750:
https://camelcamelcamel.…
[View More]com/N750-Dual-Router-Wireless-Accelerate/product/B0…
Following the suggestion from Guifi.net visitors years ago -- to build our
network to provide a good service experience, we should use new hardware
(when we can) to get performance boosts from improvements to radio,
power-management, and standards technologies. It seems like we may want to
find the next router to support, and I'm curious what folks have looked at
lately!
It seems the search may be for affordable, good quality,
dual-band/dual-radio routers that are openwrt-compatible. Plus, devices
that support new technologies like 802.11ac (Wave 2?) and 10/100/1000 MBPS
wan/lan ports (more easily take advantage of fiber services from Sonic.net
/ Cruzio / etc). Interestingly, we may also find affordable options from
brands like MikroTik that seem to have more US distribution than before if
I recall correctly.
Here's my short list from quick research, lmk what you think:
- Netgear R6220
https://www.netgear.com/home/products/networking/wifi-routers/R6220.aspx
- TP-Link Archer C7
https://www.tp-link.com/us/home-networking/wifi-router/archer-c7/
- MikroTik hAP ac lite https://mikrotik.com/product/RB952Ui-5ac2nD
[View Less]
Mesh-folks,
I have flashed the WD N600 router twice, and it fails to connect to the
mesh. As far I was able to tell, the second time it connected, but after 1+
hour the fun ended.
LOGS:
*babeld log:*
"<snip>
Interface eth0.1 has no link-local address.
setsockopt(IPV6_LEAVE_GROUP): Cannot assign requested address
Interface eth0.2 has no link-local address.
setsockopt(IPV6_LEAVE_GROUP): Cannot assign requested address
<snip>"
*messages log:*
"<snip>
Sun Dec 1 23:47:49 …
[View More]2019 daemon.err td-client: Failed to resolve hostname '
exit2.sudomesh.org'.
Sun Dec 1 23:47:49 2019 daemon.err td-client: Failed to resolve hostname '
exit1.sudomesh.org'.
<snip>"
*Question:*Is there a script|command to trigger the IP acquisition? Or is
it a DNS issue on the exit node end?
Mesh-merize me,
Daniel
[View Less]
Hi there folks,
After years of learning a bunch of stuff off of mailing lists I've
started working on using them. I want the messages I send to last and
be referred to later on, so here's a random reply in a mailing list.
For cheap hardware there are many great opportunities with
end-of-life'd enteprise stuff. Brands like Meraki and Aruba require a
license to run, which often means that large lots of hardware suddenly
become useless to the original purchaser and are sold for less than a
penny …
[View More]on the original dollar. When you combine this with the fact that
a lot of ath10k and ath11k hardware has usability issues, the
advantages of sticking with slightly older hardware become obvious.
I have been stockpiling lots of Meraki MR16, MR18 and MR24. Was able
to purchase about 250 MR16 for about $700, and trivial quantities of
the latter for about $6 and $10 apiece for testing. All hardware has
gigabit PoE (active or passive); the MR16 has 2x2 an and 2x2 bgn
(AR9220, AR9223); the MR18 has 2 x 2x2 abgn (AR9582) and one 2x2 bgn
out of the SoC, and the MR24 has 3x3 an and 3x3 bgn -- notably using
mini PCIe slots rather than integrating them into the board, see board
images here:
http://en.techinfodepot.shoutwiki.com/wiki/Cisco_Meraki_MR24
My suspicion is that the MR24's PCIe slots can be used with pretty
much any mini PCIe cards (as long as they don't require the USB-side
of the slot). This means we can stick, for example, Compex WLE900VX in
them -- 3x3 abgn/ac cards with decent power and laughable
affordability ($20/pc in single quantities). These run ath10k and are
known to be OK to run in VHT-IBSS - after all the Archer C7 uses these.
Flashing with OpenWrt is doable for all of these regardless of
firmware revision; riptidewave93 has done most of the work porting
these to OpenWrt. They have serial headers already on them, so for the
MR16 you just pop it open and plug in and power it up (I wrote a
script to automate it here:
https://github.com/btvmeshnet/hardware/tree/master/platforms/Meraki/MR16/fl…)
-- for the others you have to rebuild uBoot and reflash using a flash
clip ... but my point really is, these routers can be obtained in
bulk, have PoE so they can go anywhere, and have ath9k-based hardware
so "just work with mesh no matter how you want to use them".
Here's a lighting talk as done by Yurko of Tomesh:
https://ournetworks.ca/livestream/?m3u8=live-2019-09-22.m3u8&from=QmWyL7hcu…
I have a modification for the MR16 so that they can use external
antennas - it's quite simple, just drill two holes for U.FL-to-RP-SMA
pigtails in the two bottom corners and then screw in two pigtails from
the inside. The internal U.FL connectors are attached to both the 2.4
and 5GHz chains (this is why the internal radios cannot be used on the
same frequency). At that point, you just attach two external dual-band
antennas (or whatever else you want to stick on them).
I am happy to write up much more complete guides for all of these
things (I encourage EVERYONE to link whatever they write up into
techinfodepot, as it is where many people who get into hardware go and
learn). I am happy to flash and box up and ship 10 x MR16 + 5 x
gigabit PoE injectors + 1 x USB-to-TTL cable if you folks can make use
of them. I am happy to send folks TTL cables for free if they need
them (you can also do this work with any Raspberry Pi). Quite frankly,
to put them all to good use I would be happy spending all of my free
time buying, modifying and shipping these out in exchange for my parts
and labor cost (probably $8-$10 per MR16); my goal is to erase all
barriers to reusing this hardware, as it is cheaper than dirt, tougher
than nails, and is PoE-capable out of the box.
I also see many more opportunities out there - like RTL8812AU (see
aircrack-ng's repository for the driver) for
very-high-throughput-point-to-point at low cost. I really would like
to improve community knowledge of hardware so that those who have the
most time and the least funds can gain and share knowledge of these
things, which should (in theory) continue to improve access to
hardware for everyone (because there are more interesting problems to
solve than hardware).
Sorry if this email is exhaustive. I don't see any good single place
to collaborate on this so I'm doing a bit of a thought dump. Would be
very happy if I found a good way to link together communities better
as it took me years to do all this info discovery (did not know
Sudoroom had a mesh mailing list until now).
For hardware information in general I have been hoping to have
consolidation, but since wikidevi.com has come down and is being
migrated to techinfodepot, the new place for hardware info is here:
http://en.techinfodepot.shoutwiki.com/wiki/Main_Page
Let me know if you can use the box of Merakis; happy to send at no cost
if I have a destination.
- Martin Kennedy
[View Less]
Calling all Alameda folks...
Anybody interested in creating a wireless link to San Francisco?
We have somebody with really good line-of-site from Bernal Heights that wants to create a link
to the East Bay.
-SethCarolina
--
Securely sent with Tutanota. Get your own encrypted, ad-free mailbox:
https://tutanota.com