14 Apr
2020
14 Apr
'20
5:57 p.m.
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>om>, 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:
t
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
************************************