My ISP sonic.net has a couple of local Jobs that might interest some of
the folx that mash the mesh:
Utility Pole Fielder Oakland
<https://boards.greenhouse.io/sonic/jobs/724227?gh_jid=724227>
Field Service Technician (Copper and Fiber Cable Technician) Oakland
<https://boards.greenhouse.io/sonic/jobs/1258435?gh_jid=1258435>
https://www.sonic.com/careers
As ISPs go, sonic is not wildly evil, they support net neutrality,
opposed SOPA, are as privacy oriented as is possible for a partner of
ATT to be, and "In December 2018, Sonic announced a partnership with
eero inc., creator of the first whole-home WiFi mesh system, to improve
WiFi connectivity across the entire home."
https://en.wikipedia.org/wiki/Sonic_(ISP)
Seldom-Seen Ed
--
+++++++++++++++++++sig hell+++++++++++++++++++
Edmund Joseph Biow
328 Haddon Road
Oakland, California 94606
(510) 763-0591 (dumb landline, no caller ID, answering machine in attic, generally monitored in morning)
(415) 623-6473 (cell, I monitor the landline more frequently)
EMAIL
biow(a)sonic.net (personal) - biow(a)riseup.net (political) - ejbiow(a)gmail.com (large attachments) - ebiow(a)yasashi.net (bcc) ejbiow(a)yahoo.com (commercial)
IM (Instant Messaging, like text messaging but for computers)
(I recommend pidgin with the 'otr' encryption plugin as an instant message client):
ejbiow(a)gmail.com - ejbiow(a)yahoo.com - EdJBiow (AIM) - biow(a)riseup.net - often "Gnudnik" on irc.freenode.net
Skype username: edmundbiow
To subscribe or unsubscribe to the lists for which I'm an administrator send an email to the following:
Subscribe:
occupyoakland-subscribe(a)lists.riseup.net
oscargrantcommittee-subscribe(a)lists.riseup.net
oaklandprivacyworkinggroup-subscribe(a)lists.riseup.net
oaklandpublicbank-subscribe(a)lists.riseup.net
occupyoaklanddiscuss-subscribe(a)lists.riseup.net
oaklandlivablewagediscussion-subscribe(a)lists.riseup.net (dormant)
occupyoaklandkitchen-subscribe(a)lists.riseup.net (dormant)
Unsubscribe:
occupyoakland-unsubscribe(a)lists.riseup.net
oscargrantcommittee-unsubscribe(a)lists.riseup.net
oaklandprivacyworkinggroup-unsubscribe(a)lists.riseup.net
oaklandpublicbank-unsubscribe(a)lists.riseup.net
occupyoaklanddiscuss-unsubscribe(a)lists.riseup.net
Relatively secure EMAIL:
You can use a PGP key to encrypt and secure our messages. To start using it, you'll need to install an OpenPGP software on your computer. Below you'll find a list of possible solutions for your operating system:
Windoze: Kleopatra (http://gpg4win.de/download.html)
OSX: GPG Keychain (https://gpgtools.org/#gpgsuite)
Linux: GnuPG (https://www.gnupg.org/related_software/frontends.html)
Android: OpenKeychain (https://play.google.com/store/apps/details?id=org.sufficientlysecure.keycha…)
i(diot)OS: iPGMail (https://itunes.apple.com/us/app/ipgmail/id430780873?mt=8)
Once you set up PGP on your computer please import my public key into your local OpenPGP Key-Manager. The valid PGP keys for my biow(a)cubasoldarity.net & biow(a)riseup.net accounts can be downloaded
here: http://ebiow.yasashi.net/pgp/
An "easy" way to set up PGP on your computer is to download the free & open sources Thunderbird email client (available on Linux, Windohs & O$X) & install the EnigMail Add-On.
https://www.mozilla.org/en-US/thunderbird/all.htmlhttps://www.enigmail.net/download/https://www.enigmail.net/documentation/quickstart-ch1.php
Looking forward to exchange snooping-free messages with you & making the NSA spend mondo bucks to discover the secret of my bube's kartofel kugel recipe.
PGP Public Key for biow(a)riseup.net:
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1
mQSuBFH/+cURDADp1FTESAcLH801d1ueRIIresIKhoGx4TjeBFuJgwcGEDazeSJa
9sd9yw7q9vfqQ/yeNxt4fy3GgWuKIEmjHgdmlSA0gC5QYfA6yvhR0ejrwkV1K1F/
kV0H83HWFTi04LA6+9gIiq0YYtWaXOvi5H/PcRUpTyRBGet2KGZKrgNxTVo+Acp/
+bt8uqFjVE8/b1jZdqVDfA/DgUJj2UPdP1gPnvUxv5VKQLRvOEbEnN+0aqvezty2
DQNxEfqWQiOtytXmf3xy76MFeWYWtFxQG3av8IsBu6LiaKxL2/gvWezzl8NjG/eH
ODPscrNOWj5Lb9f/KgrPMCEwDFRUw4/yV+L5OsWgeN6hc1ZRm83OTfbgr0I+35/S
QtBFEbJ8uZh8g6wAioZGjMEaZb+3KZy/Ys39Bye1gxqjuasz5A1Fe9fHAiKB5OZT
XRlXHHklAXMX+4QCG2epuDvWDmi8Fkl5movo2C09rjYAs2NthZiLDVoT2aMEOsuR
y6KzgJFYugQoWe8BAKofM7OAtdHfkjjcMyGdowuig3ZRF/0ORBJU4KXDG00HC/4/
3hJl1hDvNNsukMIkaMbjSFjISro8whM1zR++yLilxk2HqHQ62kQmpi/dy9qdl8X9
X9TZhzqtMQ8FCqoQPbnIeF5U6qLxgKajdggbmu+CQqthbYLoNrCBoQ3mq6Llnn6y
+0+iADDWnIkDCKY4KojwqeAO4KcHazCQXsyNw64vl/ttfp2OCPkM3CwLWywE99lb
QDqYHYiL9o29C/rRlDkiBmatY6OG+R5h9NPURoKCTK4VTr1/DzHIevTseNlX+we2
DQhoP5Mc47wBzZMUxlZTKP5WxSO3aLxIIkHLNI/PLoPoK0RhlV0kao2vyHF67/v+
JETKSnQrDEABW6VX0mH9OCzEm4QIm/RSPP/dOpYV71EqVgtCBGBteR4UAgUBWmrq
MRNW4mReFZVoZmPbgfuo5+h7lnqrc85n+B8WVCZZ3ObCc9AdmOo0YZX08Tbxct3o
Bo6BB6fAkX65ny5Z0L771TI8fZmnwlGY+c4SF5zTV+NI/mgP8xQEGPonQKUUujEM
AIho9waVpg14kas+9wSKC+CqhCsoM3kEHQV9VE+YlNK2UjZQ2P2EOFEXd0FZoB6Z
uJlZhyOxuQrdDcaIG33+nsJIhMvvjOxCU1bnb2mL7UG8u4EPwCG7ByNTJdtv7Fh8
uZWk6AMOWUNDSHSUqlTj+hK8vOy/JYACAPdsU4+wJwywtdtesBmDVP1L5RU++vXm
UKxTylKiNt9zFdUbq3tqJCI7tpZ8KJNVN+f/lbozdD0LLI5D6iTAJeH39+HNDvuM
eRL6d5VCMWQee509nlpiCdwUDrgiVzGKZLZnD24q0YCYUY9qXeUDz6516e5oN1PD
YKKySv2iaSBxkEuiLFm8P3aREX49SajAZSsVKrjHVxIPVU+sJxwOv3knAv9S6hR4
/PjKy97SarxccT94q7EaNfoSeU2vDouOrBQbPXuUXmo6JCYkZ7diRHuS8UohYynD
fGkAEDJIdUl5gk94tSFlyQLf6VvfhGxvfxZ07IEfwg0ngCIA3yOoOMIKolqW3Y8x
brQ2RWQgQmlvdyAoNGssIGJyaW5nIG9uIHRoZSAkNSB3cmVuY2gpIDxiaW93QHJp
c2V1cC5uZXQ+iHoEExEIACIFAlH/+cUCGyMGCwkIBwMCBhUIAgkKCwQWAgMBAh4B
AheAAAoJECFwMETW4AsTkt0BAJ0PVd61nLWwLAnuXHZLiFEkoHsJ67Ia9g+Ko2sd
KdQPAP4lsgljmyiPk+yTRphXKuckoOjxjsFmmaqge1fHNf0S2LkEDQRR//nFEBAA
jo3VP8u7CksqPneuFn6IrmO61jinCEo6dZW4a9loUDuX2gJI7wj918OEck2dBJn2
ubv3+G8scZhfU9HpDajbh161IW2hldvukk4il9TzKbOIV8g+CG7bTo1I3k8cFVmX
JjMI52uKqSkaoEodtU5lQvhYYyMXMLJ/QbaStA3kgTubWvS/N3/iQ3gRZVHkzRyj
fNe2OM2+fY2AFpuVZEn0eu+DfqILzPWTFCSVSXFZLcBe6crPYJaLW2gFf9eL6aDg
gBoP2AMeurg3WwjkCvAOSK6xD/TcCLZiWWjnWL/i3d+7A3l9yw7eCvNYkbEbuy9M
9aMUwHBg+dRvKpyTGA4O9FF5jXKWBaUiDZxR8+hkDaYLhyxafQiXRF9NmSes/v8o
Q9q4tYUDpvQbZpj7vjkCS6MOVq7oN3MPx9eGyHYpxXI3yP7gupYwfAydmVLCrvUt
WK97v/KcystOnNEpiLavEuqEhEIv6U8RaNLxPPI2CmlLCyyadZfv4NHfU2WYo8H3
rd1CZyvC/iBM5ZBqbLL8WmOVxMjFkwCY78FBRKQ5LGGp5V8UvgvEWJcmlhKGK9FM
tY6XkgWuujYgWqmMtgf09BntYaJ1oruaOCyazufrhyx/296GHNU3dvFRgq37ePq+
FiFQV83U0PR0uqYtNaFFlDViuCqtNQxx33nl8m3cQJMAAwUP/0XDRpBJ6uMAUpkq
oKIgJjbWNUbbUh+RuL3LWY30foxF8Q1A5xJJ+2P0WLcr0j+hsVJLjA7zn38o6Zbn
qT/0S6mKIEcXlsulrcDtbSLQ8MUJO+sky2XZlk1knL0xcrw9OgaebpzHU4mWviyj
8HqHHzhjD1ZHA42CkDyI8DyXwXJvez2yFcxtKrjVMrGuxRjEwZtJqaOuWt9pp9Tp
l6VXzdOTPDC8FdHl50HVGJoVX1HJJtbRlDHskBX6eU683+1i4BCdoyNUNzHzkVYB
+FT3hrwiPtG8ac5BXSdFHb+opNCYrp4qMbWBe4BrMGm+QipTU9/0FhxfR94qgEC1
nL/pgeItXwe4iC3mqc7tEBhy6KWdeY7QXYDnKb4dDW/ipTHP1+TBBfXtH+4cGdXd
PUEJ/6Aqe60qFau1Vh4yTqoCG0B6tKHxwThOZQ/SxQRKl/fmHN7EFJaG6IcRBrRD
2RbUNkCmp+MOvVWYuQiq6WfiORjUI3DcMRcbjkRr2wX2ihjFi+dJodbIfqjr0q1X
DHVXnT7BDZXWvhDyyCsd1nwxoJW8KBQbm5BTYQ5ROz++nYDtt/4Is8eK5SY7G3rY
dE8x3ypbnfX/LrYM9dPkAL4ulUnmO6dqwbvAZc3pQBiurTxjpqdvqx9CpbjVDSmf
XJcG/zgfqdYGdkFwM8JSXG2DOmB5iGEEGBEIAAkFAlH/+cUCGwwACgkQIXAwRNbg
CxPSXwD/QDF0ILGa8LD+YF7eGC7JZasuRu2100EwLeQlCx5X920A/3mk0gr4Lo7e
cKuaMJnvySeLUouC8+LF7a8ePxmbfHvw
=gUK/
-----END PGP PUBLIC KEY BLOCK-----
Is god willing to prevent evil but not able? Then he is not omnipotent. Is he able but not willing? Then he is malevolent. Is he both able and willing? Then whence cometh evil? Is he neither able nor willing? Then why call him god? - Epicurus (341-270 BCE)
_-^--^=-_
_.-^^ -~_
_-- --_
< >)
| That's all, folks! |
\._ _./
```--. . , ; .--'''
| | |
.-=|| | |=-.
`-=#$%&%$#=-'
| ; :|
_____.,-#%&$(a)%#&#~,._____
Hi all,
A colleague on the Ashby Village Tech Team where I am volunteering
heard about my connection with sudomesh, and tells me that he has:
"seven new-in-box SonicWall TZ-205 routers left over from my days as a
road warrior for ATT," and that he would like to donate them if they
can be used for the Mesh.
Please advise!
thanks
Hilary
---
Hilary Naylor, Ph.D.
www.a2zed.us
Oakland CA
Hi! This is Ál, from Guifi.net mesh community network. I was visiting
your hackerspace in 2014 and I was collaborating with this speech:
https://sudoroom.org/pipermail/mesh/2014-September/001244.html
I hope all of you are well!
My friend and colleague Konejo (in CC) is traveling around North America
and I said him to not forget to visit your fantastic hackerspace and
projects.
He's a great programmer in several languages, ask him about his great
contributions to free software frontends!
Are you there everyday or what is the best day to go to visit you?
Take care and I hope to see you again some day, in any case you're
invited to come and visit Barcelona!
---------- Forwarded message ----------
Date: Mon, 22 Jun 2020 03:50:37 +0000
From: Noisebridge <noreply(a)discuss.noisebridge.info>
[Aaron Swartz Day Hackathon Radio Edition][2]
Hello all, I wanted to let people know that there is a special Aaron Swartz Day Hackathon is going on right now. We are building small LoRa radio modules and OP25 GNUradio systems to turen into emergency radio mesh network for people to use around the bay during emergencies, power outages, cell disruptions, and events where the cell networks might be overloaded.
you can find info on how to help here.
https://www.aaronswartzday.org/virtual-hackathon/https://www.aaronswartzday.org/virtual-hackathon-faq/
another project we are improving is the Swartz Manning VR Museum that Lisa, Me, LXPK, Bernice, and a few others started in 2017.
that project can be found here
[2]: https://discuss.noisebridge.info/t/aaron-swartz-day-hackathon-radio-edition…
Hello all,
I hope everyone is well. I wanted to remind all collectives that if yall
have an event, even if it is virtual, we want to encourage sharing it via
the Omni's calendar. You can send the event info to
commons(a)lists.omnicommons.org.
En Solidaridad,
Roberto
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
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
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
> ************************************
>
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.
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
>>>>
>>>
>>
