mesh April 2020

mesh@sudoroom.org

10 participants
13 discussions

by Benny Lichtner

The oakland internet choice initiative is picking up speed! > The Oakland Internet Choice Coalition (OICC) is organizing to provide a legal path requiring landlords of large multi-tenant buildings to allow *any *qualified Internet service provider to serve their tenants. Oakland City Council President Rebecca Kaplan is looking for community support in the next couple of months. If you live in Oakland, read more about it and send her an email: https://takeaction.salsalabs.org/oicc0 I think passing this ordinance is going to be a really important step to support independent ISPs in their fight against the big monopolies. --Benny Tweet from Monkey Brains: https://twitter.com/monkeybrainsnet/status/1192505705728598016 And from EFF: https://act.eff.org/action/bring-choice-to-oakland-f765c0b9-89ea-4dac-ac4d-…

2 years, 6 months

Omni Newsletter - call for updates, thoughts, art, words

by Roberto Martinez

Hello fellow omninoms, how is everyone doing? We hope all of you are well and taking care of yourselves and your community during this covid-19 pandemic. What an intense couple of weeks we have lived, right? Full of uncertainties, but also full of hope. A lot has happened in the past several weeks, it feels like we are the center of a fast moving current, acting and reacting to the rapidly evolving threat we and our communities face. After all, covid-19 has done an excellent job at amplifying the ills of the capitalist system making its deadly presence ever more cruel within our most vulnerable communities. But at the Omni, we are lucky to be part of a community of caring, committed and skillful folks who are doing the groundwork to support and build efforts to aid those in need. There is a lot that has happened, direct actions, mutual aid efforts, mask making, food distribution, and more! In the spirit of community building and mutual-care, the communications working group is dusting off the printing press and bringing back Omni’s newsletter to share with each other all of the work we are doing, the feelings we are feeling, and maybe a collective vision for a better future. We are hoping to have the newsletter out by the end of the month, which is in about two weeks. Like newsletters of the past we want to feature the work of each collective. So we are asking each collective to submit 1-4 paragraphs providing an update of the work ya’ll are doing collectively or maybe feature the work of an individual member. Below are some suggestions of questions or topics you can touch on: - Updates from your collective - How is your collective responding to the covid-19 pandemic. - Reflections about the covid-19 pandemic. - What kind of world do yall imagine post covid-19? - Share anything that your collective needs help with, or needs. - Anything you want to share….poetry, paintings, photographs, recipes, anything. Additionally, we will be featuring upcoming events, meetings, or ongoing efforts from collectives, so please send those our way as well. *Please send your content to the communications working group email at comms(a)lists.omnicommons.org <comms(a)lists.omnicommons.org>, by Tuesday April 28th. * Like all the other working groups at the Omni, the communications working group needs more participation. If you are interested in joining please sign up to the communication working group email list at https://omnicommons.org/lists/listinfo/comms. Thank you. With love and solidarity, The Communications Working Group

3 years, 11 months

Sudo Mesh is an Omni Member Collective + meeting tonight!

by mai＠peoplesopen.net

Hey Meshers, (apologies for the cross post!) At the Omni Delegates meeting on Thursday 4/23, the Delegates voted to approved Sudo Mesh's application to become a member collective! Woohoo!! The terms of contribution are as the Stewards decided on Loomio: a flat $200/month payment to Omni, plus 5% of any grants we receive up to $5000 for a single grant. This is an exciting new chapter for Sudo Mesh. It feels really good to be able to support Omni more officially, not just financially, but to be present and help the Commons have a stronger core of stewarding organizations. If you're interested in joining the next delegates meeting, it will take place on Thursday May 7 from 7-9pm. It's every first and third Thursday. Also! We are meeting tonight 7:30-9pm on Jitsi. Lots to chat about! Here's the meeting room link: https://meet.jit.si/sudomesh2020 (https://meet.jit.si/sudomesh2020) Hope to see you at the meeting tonight. Thanks, Mai

3 years, 12 months

Re: [Mesh] mesh Digest, Vol 87, Issue 13

by outtolunch＠tutanota.com

Hey this sounds cool. Sorry just to clear things up. Are you saying that there are 2 point-to-point links(1-5ghz and 1-2.4ghz) between the InternetArchive Richmond tower and the location here: https://goo.gl/maps/FornbaGQogUQYhgf6 at Nicholl Knob and we could potentially create a point-to-point between Nicholl Knob area and 1037 Murray or between Nicholl Knob and PLACE? InternetArchive<->NichollKnob<->PLACE or IA<->NK<->1037Murray I attached two .KMLS showing links between NK<->1037Murray and NK<->PLACE There are less buildings between PLACE and NK! -- Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: https://tutanota.com Apr 15, 2020, 12:00 by mesh-request(a)lists.sudoroom.org: > 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. link to Internet Archive in Richmond available (Jake) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Apr 2020 18:06:07 -0700 (PDT) > From: Jake <jake(a)spaz.org> > To: mesh(a)lists.sudoroom.org > Cc: "$-pEEf-$" <peef(a)mindfart.com> > Subject: [Mesh] link to Internet Archive in Richmond available > Message-ID: <alpine.BSF.2.21.999.2004141622410.47622(a)pe710.spaz.org> > Content-Type: text/plain; format=flowed; charset=US-ASCII > > Peef says that there are two links to the Richmond Internet Archive tower that > are still available for us to connect to. > > there is a still an unused 5ghz link to Richmond that could be utilized easily. > > Richmond Tower, probably 60' AGL: https://goo.gl/maps/FornbaGQogUQYhgf6 > > He also has a 24ghz AirFiber, but that would probably need a tower climb to > align it on the Richmond side, whereas the 5ghz is much wider: > https://goo.gl/maps/H9JzbvVLZd9orvsa9 > > That link can be seen almost anywhere in the east bay, it's super high, but > would definitely need alignment if not right in line with 1037 Murray street. > > I'm in contact with the people at P.L.A.C.E. and the property owners are cool > friends too, so we could put a tower there and beam out from there to wherever > we needed to, and it would stay there forever. That's at 1121 64th St, Oakland > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > mesh mailing list > mesh(a)lists.sudoroom.org > https://sudoroom.org/lists/listinfo/mesh > > > ------------------------------ > > End of mesh Digest, Vol 87, Issue 13 > ************************************ >

4 years

sudomesh peoplesopen monitor

by Jake

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.

4 years

Re: [Mesh] 65.146.129 doesn't seem to be working

by Jake

OK it stopped working again. 19: l2tp0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1446 qdisc htb state UNKNOWN group default qlen 1000 link/ether 82:8d:3e:43:28:9e brd ff:ff:ff:ff:ff:ff inet 100.65.146.129/32 scope global l2tp0 valid_lft forever preferred_lft forever inet6 fe80::808d:3eff:fe43:289e/64 scope link valid_lft forever preferred_lft forever root@sudomesh-node:~# ping -I l2tp0 100.65.165.1 PING 100.65.165.1 (100.65.165.1): 56 data bytes 64 bytes from 100.65.165.1: seq=0 ttl=63 time=42.820 ms 64 bytes from 100.65.165.1: seq=1 ttl=63 time=44.847 ms 64 bytes from 100.65.165.1: seq=2 ttl=63 time=36.171 ms ^C --- 100.65.165.1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 36.171/41.279/44.847 ms root@sudomesh-node:~# ping -I l2tp0 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ** hangs ** and i should say that i could ping 8.8.8.8 if i didn't specify the -I l2tp0 and that internet wasn't flowing when i was on the PON wifi > OK well I rebooted it and now it works, but i would like to know what i could > have checked to figure out what was wrong before. > > On Sun, 12 Apr 2020, Jake wrote: > >> 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? 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 >>>> >>> >>

4 years

link to Internet Archive in Richmond available

by Jake

Peef says that there are two links to the Richmond Internet Archive tower that are still available for us to connect to. there is a still an unused 5ghz link to Richmond that could be utilized easily. Richmond Tower, probably 60' AGL: https://goo.gl/maps/FornbaGQogUQYhgf6 He also has a 24ghz AirFiber, but that would probably need a tower climb to align it on the Richmond side, whereas the 5ghz is much wider: https://goo.gl/maps/H9JzbvVLZd9orvsa9 That link can be seen almost anywhere in the east bay, it's super high, but would definitely need alignment if not right in line with 1037 Murray street. I'm in contact with the people at P.L.A.C.E. and the property owners are cool friends too, so we could put a tower there and beam out from there to wherever we needed to, and it would stay there forever. That's at 1121 64th St, Oakland

4 years

Re: [Mesh] mesh Digest, Vol 87, Issue 11

by outtolunch＠tutanota.com

Mesh routing table: $ip route show table public Tuneldigger: $tail -f /var/log/messages | grep td-client $/etc/init.d/tunneldigger restart Or $/etc/init.d/meshrouting restart -- Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: https://tutanota.com Apr 14, 2020, 12:00 by mesh-request(a)lists.sudoroom.org: > 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. Re: 65.146.129 doesn't seem to be working (Jake) > 2. Re: 65.146.129 doesn't seem to be working (Jake) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Apr 2020 19:34:01 -0700 (PDT) > From: Jake <jake(a)spaz.org> > To: Benny Lichtner <bennlich(a)gmail.com>, mesh(a)lists.sudoroom.org > Subject: Re: [Mesh] 65.146.129 doesn't seem to be working > Message-ID: <alpine.BSF.2.21.999.2004131924000.47622(a)pe710.spaz.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > OK well I rebooted it and now it works, but i would like to know what i could > have checked to figure out what was wrong before. > > On Sun, 12 Apr 2020, Jake wrote: > >> 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? 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 >>>> > > > ------------------------------ > > Message: 2 > Date: Tue, 14 Apr 2020 00:12:18 -0700 (PDT) > From: Jake <jake(a)spaz.org> > To: mesh(a)lists.sudoroom.org > Subject: Re: [Mesh] 65.146.129 doesn't seem to be working > Message-ID: <alpine.BSF.2.21.999.2004140009510.47622(a)pe710.spaz.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > OK it stopped working again. > > 19: l2tp0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1446 qdisc htb state UNKNOWN > group default qlen 1000 > link/ether 82:8d:3e:43:28:9e brd ff:ff:ff:ff:ff:ff > inet 100.65.146.129/32 scope global l2tp0 > valid_lft forever preferred_lft forever > inet6 fe80::808d:3eff:fe43:289e/64 scope link > valid_lft forever preferred_lft forever > root@sudomesh-node:~# ping -I l2tp0 100.65.165.1 > PING 100.65.165.1 (100.65.165.1): 56 data bytes > 64 bytes from 100.65.165.1: seq=0 ttl=63 time=42.820 ms > 64 bytes from 100.65.165.1: seq=1 ttl=63 time=44.847 ms > 64 bytes from 100.65.165.1: seq=2 ttl=63 time=36.171 ms > ^C > --- 100.65.165.1 ping statistics --- > 3 packets transmitted, 3 packets received, 0% packet loss > round-trip min/avg/max = 36.171/41.279/44.847 ms > root@sudomesh-node:~# ping -I l2tp0 8.8.8.8 > PING 8.8.8.8 (8.8.8.8): 56 data bytes > ** hangs ** > > and i should say that i could ping 8.8.8.8 if i didn't specify the -I l2tp0 and > that internet wasn't flowing when i was on the PON wifi > >> OK well I rebooted it and now it works, but i would like to know what i could >> have checked to figure out what was wrong before. >> >> On Sun, 12 Apr 2020, Jake wrote: >> >>> 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? 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 >>>>> > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > mesh mailing list > mesh(a)lists.sudoroom.org > https://sudoroom.org/lists/listinfo/mesh > > > ------------------------------ > > End of mesh Digest, Vol 87, Issue 11 > ************************************ > t

4 years

65.146.129 doesn't seem to be working

by Jake

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

4 years

either be a Mikrotik Wireless Wire or a Ubiquiti NanobeamAC

by Jake

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

4 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

mesh April 2020