Ne strahlt Offline aus.
Ack, hier Zuhause auch, dito in der 4ma — da hab’ ich’s wohl hingerichtet das l2tp-Netz … Sorry for that.
config broker 'mesh_vpn'
option uuid 'f8d111bd5e24'
option group 'gluon-mesh-vpn'
option broker_selection 'usage'
option bind_interface 'br-wan'
option interface 'mesh-vpn'
option enabled '1'
list address 'gut.l2tp-gut01.4830.org:10001'
list address 'gut.l2tp-gut02.4830.org:10001'
list address 'gut.l2tp-ham01.4830.org:10001'
list address 'gut.l2tp-ham02.4830.org:10001'
list address 'gut.l2tp-fra01.4830.org:10001'
list address 'gut.l2tp-ams01.4830.org:10001'
Soweit, so schick …
root@33332-Schalueckstr-Garten1:~# logread -f
Mon May 6 13:59:16 2019 daemon.err td-client: No suitable brokers found. Retrying in 5 seconds.
Mon May 6 13:59:21 2019 daemon.notice netifd: wan (27729): udhcpc: sending renew to 0.0.0.0
Mon May 6 13:59:21 2019 daemon.notice netifd: wan (27729): udhcpc: lease of 192.168.5.202 obtained, lease time 30
Mon May 6 13:59:21 2019 daemon.err td-client: Resetting status of brokers and starting from scratch.
Mon May 6 13:59:21 2019 daemon.info td-client: Performing broker selection...
Mon May 6 13:59:32 2019 daemon.err td-client: No suitable brokers found. Retrying in 5 seconds.
Mon May 6 13:59:36 2019 daemon.notice netifd: wan (27729): udhcpc: sending renew to 0.0.0.0
Mon May 6 13:59:36 2019 daemon.notice netifd: wan (27729): udhcpc: lease of 192.168.5.202 obtained, lease time 30
Mon May 6 13:59:37 2019 daemon.err td-client: Resetting status of brokers and starting from scratch.
Mon May 6 13:59:38 2019 daemon.info td-client: Performing broker selection...
*Kopfkratz*
root@33332-Schalueckstr-Garten1:~# nslookup gut.l2tp-gut01.4830.org
;; connection timed out; no servers could be reached
root@33332-Schalueckstr-Garten1:~# cat /tmp/resolv.conf.auto
# Interface wan
# Interface wan6
Hmm? Keinen DNS-Server per DHCP bekommen?! Dürfte aber lokales Problem sein, renovierungsbedingt ist das Netz hier grade komisch …
root@33332-Schalueckstr-Garten1:~# echo "nameserver 1.1.1.1" >> /tmp/resolv.conf.auto
root@33332-Schalueckstr-Garten1:~# cat /tmp/resolv.conf.auto
# Interface wan
# Interface wan6
nameserver 1.1.1.1
root@33332-Schalueckstr-Garten1:~# nslookup gut.l2tp-gut01.4830.org
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: gut.l2tp-gut01.4830.org
gut.l2tp-gut01.4830.org canonical name = l2tp-gut01.4830.org
Name: l2tp-gut01.4830.org
Address 1: 192.251.226.126
gut.l2tp-gut01.4830.org canonical name = l2tp-gut01.4830.org
Address 2: 2a06:e881:1700:1:400:c0ff:fefb:e27e
root@33332-Schalueckstr-Garten1:~# logread -f
Mon May 6 14:04:12 2019 daemon.err td-client: Resetting status of brokers and starting from scratch.
Mon May 6 14:04:12 2019 daemon.info td-client: Performing broker selection...
Mon May 6 14:04:21 2019 daemon.notice netifd: wan (27729): udhcpc: sending renew to 0.0.0.0
Mon May 6 14:04:21 2019 daemon.notice netifd: wan (27729): udhcpc: lease of 192.168.5.202 obtained, lease time 30
Mon May 6 14:04:23 2019 daemon.err td-client: No suitable brokers found. Retrying in 5 seconds.
Hrmpft.
root@33332-Schalueckstr-Garten1:~# for i in gut01 gut02 ham01 ham02 fra01 ams01 ; do echo $i ; echo ; nslookup gut.l2tp-$i.4830.or
g 1.1.1.1 ; echo ; done
gut01
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-gut01.4830.org
gut.l2tp-gut01.4830.org canonical name = l2tp-gut01.4830.org
Name: l2tp-gut01.4830.org
Address 1: 192.251.226.126
gut.l2tp-gut01.4830.org canonical name = l2tp-gut01.4830.org
Address 2: 2a06:e881:1700:1:400:c0ff:fefb:e27e
gut02
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-gut02.4830.org
gut.l2tp-gut02.4830.org canonical name = l2tp-gut02.4830.org
Name: l2tp-gut02.4830.org
Address 1: 192.251.226.125
gut.l2tp-gut02.4830.org canonical name = l2tp-gut02.4830.org
Address 2: 2a06:e881:1700:1:400:c0ff:fefb:e27d
ham01
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-ham01.4830.org
Address 1: 127.6.6.6
*** Can't find gut.l2tp-ham01.4830.org: No answer
ham02
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-ham02.4830.org
Address 1: 127.6.6.6
*** Can't find gut.l2tp-ham02.4830.org: No answer
fra01
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-fra01.4830.org
Address 1: 127.6.6.6
*** Can't find gut.l2tp-fra01.4830.org: No answer
ams01
Server: 1.1.1.1
Address: 1.1.1.1#53
Name: gut.l2tp-ams01.4830.org
Address 1: 127.6.6.6
*** Can't find gut.l2tp-ams01.4830.org: No answer
Hmmm …
wusel@ysabell:~$ ssh root@l2tp-gut01.4830.org netstat -anup \| grep pyth
wusel@ysabell:~$ ssh root@l2tp-gut02.4830.org netstat -anup \| grep pyth
udp 0 0 192.251.226.125:10000 0.0.0.0:* 4173/python
wusel@ysabell:~$ ssh root@l2tp-ham01.4830.org netstat -anup \| grep pyth
udp 13056 0 193.26.120.125:10000 0.0.0.0:* 680/python
udp 33792 0 193.26.120.125:10001 0.0.0.0:* 692/python
udp 0 0 193.26.120.125:10002 0.0.0.0:* 628/python
udp 0 0 193.26.120.125:10004 0.0.0.0:* 685/python
udp 0 0 193.26.120.125:10005 0.0.0.0:* 632/python
udp 0 0 193.26.120.125:10006 0.0.0.0:* 689/python
udp 0 0 193.26.120.125:20102 91.36.179.65:41555 ESTABLISHED 680/python
wusel@ysabell:~$ ssh root@l2tp-ber01.4830.org netstat -anup \| grep pyth
udp 52224 0 193.26.120.99:10001 0.0.0.0:* 646/python
udp 0 0 193.26.120.99:10002 0.0.0.0:* 623/python
udp 0 0 193.26.120.99:10003 0.0.0.0:* 661/python
udp 0 0 193.26.120.99:10004 0.0.0.0:* 613/python
udp 0 0 193.26.120.99:10005 0.0.0.0:* 610/python
udp 0 0 193.26.120.99:10006 0.0.0.0:* 659/python
Dann tmp-fixen wir das doch mal eben schnell im DNS …
wusel@ysabell:~$ for i in gut gto gt8 wrz fsl ; do host $i.l2tp-ham01.4830.org dns-gut.4830.org. | grep alias ; done
wrz.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
fsl.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
wusel@ysabell:~$ for i in gut gto gt8 wrz fsl ; do grep $i.l2tp-ham01.4830.org /data/wusel/site-ffgt-v2018.1/domains-l2tp/* ; done
/data/wusel/site-ffgt-v2018.1/domains-l2tp/gut.conf: 'gut.l2tp-ham01.4830.org:10001',
/data/wusel/site-ffgt-v2018.1/domains-l2tp/gto.conf: 'gto.l2tp-ham01.4830.org:10002',
/data/wusel/site-ffgt-v2018.1/domains-l2tp/gt8.conf: 'gt8.l2tp-ham01.4830.org:10003',
/data/wusel/site-ffgt-v2018.1/domains-l2tp/wrz.conf: 'wrz.l2tp-ham01.4830.org:10005',
/data/wusel/site-ffgt-v2018.1/domains-l2tp/fsl.conf: 'fsl.l2tp-ham01.4830.org:10006',
DNS geändert, reloaded:
wusel@ysabell:~$ for i in gut gto gt8 wrz fsl ; do host $i.l2tp-ham01.4830.org dns-gut.4830.org. | grep alias ; done
gut.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
gto.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
gt8.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
wrz.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
fsl.l2tp-ham01.4830.org is an alias for l2tp-ham01.4830.org.
Scheint zu tun:
wusel@ysabell:~$ ssh root@l2tp-ham01.4830.org netstat -anup \| grep pyth
udp 13056 0 193.26.120.125:10000 0.0.0.0:* 680/python
udp 3840 0 193.26.120.125:10001 0.0.0.0:* 692/python
udp 6912 0 193.26.120.125:10002 0.0.0.0:* 628/python
udp 0 0 193.26.120.125:10004 0.0.0.0:* 685/python
udp 0 0 193.26.120.125:10005 0.0.0.0:* 632/python
udp 0 0 193.26.120.125:10006 0.0.0.0:* 689/python
udp 46592 0 193.26.120.125:20101 84.179.119.12:33671 ESTABLISHED 692/python
udp 3840 0 193.26.120.125:20102 91.36.179.65:41555 ESTABLISHED 680/python
udp 39168 0 193.26.120.125:20104 88.76.249.207:41145 ESTABLISHED 628/python
udp 42752 0 193.26.120.125:20105 178.201.41.190:50389 ESTABLISHED 692/python
udp 16896 0 193.26.120.125:20106 87.142.43.35:45579 ESTABLISHED 692/python
udp 23808 0 193.26.120.125:20107 91.36.179.65:45601 ESTABLISHED 692/python
udp 37632 0 193.26.120.125:20108 88.153.161.209:63557 ESTABLISHED 692/python
udp 37632 0 193.26.120.125:20109 88.153.161.209:58532 ESTABLISHED 692/python
root@33332-Schalueckstr-Garten1:~# batctl gwl
[B.A.T.M.A.N. adv openwrt-2018.1-5, MainIF/MAC: primary0/b6:49:05:e3:ce:33 (bat0/f8:d1:11:bd:5e:24 BATMAN_IV)]
Router ( TQ) Next Hop [outgoingIf] Bandwidth
* 02:ca:ff:ee:01:02 ( 93) 02:ca:ff:ee:01:02 [ mesh-vpn]: 1024.0/1024.0 MBit
02:ca:ff:ee:01:04 ( 80) 02:ca:ff:ee:01:02 [ mesh-vpn]: 1024.0/1024.0 MBithopglass.4830.org/tng/ hat nun die 7 Teilnetze zusammengefaßt (Stadt GT, Nordkreis GT, Südkreis GT, Stadt Rheda-Wiedenbrück, Müritz-Region, Feldberger Seenlandschaft sowie “sonstwo”) …
Ipv4 scheint aktuell im L2Tp Netz ein Problem z haben.
Sowohl über die Knoten die über das Gütersloher Netz gehen, als auch über das Wiedenbrücker Netz.
Das war mir schon klar. Ging mir nur darum, es zusagen, so das es nicht in vergessenheit Gerät, falls es aus welchen Gründen auch immer wie beim letzten mal nur ein kleines Teil des Testnetzes betrifft.
(Ich habe den Rest auch gelesen, allerdings nicht direkt mit bekommen, da meine beiden Orte wo ich täglich bin aktuell komplett über L2TP laufen.)
1 „Gefällt mir“
Zweitjob als Hellseher in Erwägung gezogen? 
Zumindest bei mir lag’s an Exit via Berlin (der IP nach bei Dir auch), da stimmte das interne Routing nicht und somit kamen die Antwortpakete nicht wieder in Berlin an. v4 tut bei mir nun, v6 hat noch 'n Problem.
Hrmpft. Eben ging’s doch wieder nicht 
Ich ziehe manchmal solche Fehler an 
Aktuell gibt es keine v4 Adresse, egal ob im Wiedenbrücker oder Gütersloher L2TP Netz.
v6 funktioniert inklusive Routing.
Hmm. Gestern abend tat’s von der VM hinter einer L2TP-Gluon-VM. Vom Handy aber nicht
Should be fixed — der isc-dhcpd lief auf l2tp-ham01 schlicht nicht (mehr)
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc mq state UP group default qlen 1000
link/ether 00:24:d7:26:94:e4 brd ff:ff:ff:ff:ff:ff
inet 10.234.137.155/20 brd 10.234.143.255 scope global dynamic wlp2s0
valid_lft 3600sec preferred_lft 3600sec
inet6 2001:bf7:1310:128:224:d7ff:fe26:94e4/64 scope global noprefixroute dynamic
valid_lft 86391sec preferred_lft 14391sec
inet6 fe80::224:d7ff:fe26:94e4/64 scope link
valid_lft forever preferred_lft forever
1 „Gefällt mir“
http://hopglass.4830.org/tng/ hat nun eine Karte aus den 7 verschiedenen Meshes.
00 - Freifunk by 4830.org (JWD)
01 - Freifunk KreisGT (Stadt GT)
02 - Freifunk KreisGT (Süd)
03 - Freifunk KreisGT (Nord)
04 - Freifunk KreisGT (Rheda-Wiedenbrück)
05 - Freifunk Müritz
06 - Freifunk Feldberger Seenplatte
Die Netzprobleme mit Berlin sollten nun auch ausgeräumt sein; die fehlerhaft in Gütersloh eingebrachte Route zur Berliner NAT-IP konnte gefunden und gelöscht werden. Happy Testing!
Statt ...
root@de6:~# traceroute 192.251.226.216
traceroute to 192.251.226.216 (192.251.226.216), 30 hops max, 60 byte packets
1 130.255.76.1 (130.255.76.1) 0.668 ms 0.717 ms 0.691 ms
2 ve300.edge1-dus1.mesh.eu (194.146.118.2) 0.722 ms 0.699 ms 0.673 ms
3 ae4.cr2.gut1.plusserver.com (213.203.192.158) 3.115 ms 3.093 ms 2.926 ms
4 62.138.113.177 (62.138.113.177) 2.870 ms 2.846 ms 2.906 ms
5 de0.as206946.net (193.26.120.92) 12.264 ms 12.197 ms 12.100 ms
6 bgp-gut01.4830.org (193.26.120.82) 12.703 ms 12.570 ms 12.469 ms
7 bgp-gut02.4830.org (193.26.120.83) 17.241 ms 17.224 ms 17.198 ms
8 de0.as206946.net (193.26.120.92) 12.668 ms 12.710 ms 12.669 ms
9 bgp-gut01.4830.org (193.26.120.82) 13.379 ms 13.329 ms 13.874 ms
10 bgp-gut02.4830.org (193.26.120.83) 18.263 ms 18.233 ms 18.121 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * bgp-gut02.4830.org (193.26.120.83) 18.974 ms 18.880 ms
17 de0.as206946.net (193.26.120.92) 14.717 ms 14.715 ms 14.693 ms
18 bgp-gut01.4830.org (193.26.120.82) 15.357 ms 15.337 ms 15.302 ms
… nun …
root@de6:~# traceroute 192.251.226.216
traceroute to 192.251.226.216 (192.251.226.216), 30 hops max, 60 byte packets
1 130.255.76.1 (130.255.76.1) 0.571 ms 0.585 ms 0.562 ms
2 ve300.edge1-dus1.mesh.eu (194.146.118.2) 0.694 ms 0.670 ms 0.646 ms
3 ae4.cr2.gut1.plusserver.com (213.203.192.158) 2.898 ms 2.937 ms 2.980 ms
4 62.138.113.177 (62.138.113.177) 3.191 ms 3.168 ms 3.272 ms
5 de0.as206946.net (193.26.120.92) 11.611 ms 11.604 ms 11.537 ms
6 bgp-gut01.4830.org (193.26.120.82) 12.192 ms 12.223 ms 12.286 ms
7 bgp-ber01.4830.org (193.26.120.86) 16.708 ms 16.724 ms 16.688 ms
8 gw-camp.uu.org (192.251.226.216) 16.812 ms 19.432 ms 19.339 ms
(Ja, DNS muß noch angepaßt werden.)
In der Tat, die NAT-Regel fehlte wieder — WTF?!
root@l2tp-ham01 ~ # traceroute -s 10.234.144.2 v6.de
traceroute to v6.de (195.30.8.34), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
…
root@l2tp-ham01 ~ # iptables -L -n -t nat
…
SNAT all -- 0.0.0.0/0 0.0.0.0/0 to:192.251.226.214
…
root@l2tp-ham01 ~ # iptables -A POSTROUTING -t nat -s 10.0.0.0/8 -o ens3 -j SNAT --to-source 192.251.226.214
root@l2tp-ham01 ~ # traceroute -s 10.234.144.2 v6.de
traceroute to v6.de (195.30.8.34), 30 hops max, 60 byte packets
1 bgp-ham02.4830.org (193.26.120.85) 0.285 ms 0.254 ms 0.233 ms
2 decix-ham.ham.de.tnib.net (80.81.203.3) 8.212 ms 8.215 ms 8.200 ms
3 ae5-0.cr0.muc.de.tnib.net (81.92.175.13) 13.355 ms 13.301 ms 13.300 ms
4 m33-ten0-0-0-2.space.net (81.92.174.134) 15.627 ms 15.855 ms 15.912 ms
5 m32-te0-0-1-3.space.net (185.54.120.68) 15.492 ms 15.398 ms 15.555 ms
6 cisco-m-ii-te1-2-v25.space.net (185.54.120.58) 15.228 ms 15.136 ms 14.995 ms
7 v4only.v6.de (195.30.8.34) 15.562 ms 15.847 ms 15.807 ms
Das muß ich mal genauer beobachten …
1 „Gefällt mir“
Gnampf, das tut auch nimmer. Checking …
Gibt es eine möglichkeit per Konsole das Mesh/Domäne im Nachgang zu ändern, ohne einen kompletten Reset durchzu führen? (Nur Interesse halber um zwischendurch mal verschiedene sachen schneller zu testen)
Sure:
wusel@ysabell:~$ ssh root@192.168.5.186
sh: /usr/bin/xauth: not found
BusyBox v1.28.4 () built-in shell (ash)
_/_/_/_/ _/ _/_/ _/
_/ _/ _/_/ _/_/ _/ _/ _/ _/_/_/ _/ _/
_/_/_/ _/_/ _/_/_/_/ _/ _/_/_/_/ _/ _/ _/ _/ _/_/
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/ _/ _/_/_/ _/ _/ _/_/_/ _/ _/ _/ _/
Freifunk-Firmware für den Kreis Gütersloh sowie die Müritz-Region
und die Feldberger Seenlandschaft
Info/Kontakt: https://freifunk-kreisgt.de | https://mueritz.freifunk.net
https://freifunk-feldberg.de
Tools:
- autoupdater -f (Firmware-Update erzwingen)
- batctl gwl (Informationen zu batman-adv-Gateways anzeigen)
- batctl o | wc -l (Anzahl 'orginators' (Knoten) im Netz anzeigen)
- batctl tg | wc -l (Anzahl aller Geräte im Netz anzeigen)
OS: 18.06-SNAPSHOT, r7712+20-8de93ce FW: 1.1.5~4
HW: TP-Link TL-WA860RE v1
root@33332-S107-RPT-OG-8be4:~# uci get gluon.core.domain
gut
root@33332-S107-RPT-OG-8be4:~# uci set gluon.core.domain=zzz
root@33332-S107-RPT-OG-8be4:~# uci get gluon.core.domain
zzz
root@33332-S107-RPT-OG-8be4:~# uci commit
root@33332-S107-RPT-OG-8be4:~# gluon-reconfigure
Configuring: 001-aaaearly-save-wan-mac.sh
Configuring: 001-ffgt-gluon-hacks.sh
Configuring: 001-upgrade
Configuring: 004-migrate-ffgt-locode
Information: setting FFGT locode 'gut' as domain code for site.conf.
[*** NARF! Satz mit X ;-) *** ]
[…]
Configuring: 998-commit
Configuring: 999-ffgt-preserve-mods
Configuring: 999-localize-banner
Configuring: 999-version
One or more upgrade scripts failed. Please review the above error messages.
root@33332-S107-RPT-OG-8be4:~# uci get gluon.core.domain
gut
Hmm. Soweit die Theorie
Aber das sollte tun:
root@33332-S107-RPT-OG-8be4:~# uci get gluon-node-info.@location[0].siteselect
gut
root@33332-S107-RPT-OG-8be4:~# uci set gluon-node-info.@location[0].siteselect=zzz
root@33332-S107-RPT-OG-8be4:~# gluon-reconfigure
Configuring: 001-aaaearly-save-wan-mac.sh
Configuring: 001-ffgt-gluon-hacks.sh
Configuring: 001-upgrade
Configuring: 004-migrate-ffgt-locode
Information: setting FFGT locode 'zzz' as domain code for site.conf.
Configuring: 005-site-domain
Configuring: 010-primary-mac
Configuring: 020-interfaces
Configuring: 030-system
Configuring: 100-core-reset-sysctl
Configuring: 100-lock-password
Configuring: 110-network
Configuring: 120-ntp-servers
Configuring: 140-firewall-rules
Configuring: 150-poe-passthrough
Configuring: 200-wireless
Configuring: 210-interface-wan
Configuring: 220-interface-lan
Configuring: 300-gluon-client-bridge-network
Configuring: 300-setup-mode
Configuring: 310-gluon-client-bridge-local-node
Configuring: 310-gluon-mesh-batman-adv-mesh
Configuring: 310-setup-mode-migrate
Configuring: 320-gluon-client-bridge-wireless
Configuring: 320-gluon-mesh-batman-adv-client-bridge
Configuring: 320-setup-ifname
Configuring: 330-gluon-mesh-batman-adv-mac-addresses
Configuring: 400-alfred-firewall
Configuring: 400-mesh-vpn-tunneldigger
Configuring: 400-neighbour-info-firewall
Configuring: 400-respondd-firewall
Configuring: 499-migrate-vpn
/usr/bin/lua: ./499-migrate-vpn:3: module 'gluon.site_config' not found:
[Fehlermeldung entfernt; muß ich mir angucken.]
Configuring: 500-autoupdater
Configuring: 500-enable-alfred
Configuring: 500-mesh-vpn
Configuring: 500-node-info-system
Configuring: 500-opkg
Configuring: 500-radvd-remove-user
Configuring: 500-ssid-changer
Configuring: 500-status-page
Configuring: 510-autoupdater-wifi-fallback
Configuring: 510-node-info-role
Configuring: 520-node-info-whitespace-fix
Configuring: 800-migrate-batadv
Configuring: 820-dns-config
Configuring: 950-ffda-domain-director
Configuring: 991-hostname-conformization
Configuring: 998-commit
Configuring: 999-ffgt-preserve-mods
Configuring: 999-localize-banner
Configuring: 999-version
One or more upgrade scripts failed. Please review the above error messages.
root@33332-S107-RPT-OG-8be4:~# cat /etc/config/tunneldigger
config broker 'mesh_vpn'
option uuid 'c46e1f3a8be4'
option group 'gluon-mesh-vpn'
option broker_selection 'usage'
option bind_interface 'br-wan'
option interface 'mesh-vpn'
option enabled '1'
list address 'zzz.l2tp-gut01.4830.org:10000'
list address 'zzz.l2tp-gut02.4830.org:10000'
list address 'zzz.l2tp-ham01.4830.org:10000'
list address 'zzz.l2tp-ham02.4830.org:10000'
list address 'zzz.l2tp-fra01.4830.org:10000'
list address 'zzz.l2tp-ams01.4830.org:10000'
root@33332-S107-RPT-OG-8be4:~# reboot
root@33332-S107-RPT-OG-8be4:~# Connection to 192.168.5.186 closed by remote host.
Connection to 192.168.5.186 closed.
Kaum macht man’s richtig …
wusel@ysabell:~$ ssh root@192.168.5.186 ip addr show br-client \; iwinfo
sh: /usr/bin/xauth: not found
8: br-client: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether c4:6e:1f:3a:8b:e4 brd ff:ff:ff:ff:ff:ff
inet6 2001:bf7:1310:666:c66e:1fff:fe3a:8be4/64 scope global dynamic
valid_lft 86394sec preferred_lft 14394sec
inet6 fd10:ca1::c66e:1fff:fe3a:8be4/64 scope global dynamic
valid_lft 86291sec preferred_lft 14291sec
inet6 fe80::c66e:1fff:fe3a:8be4/64 scope link
valid_lft forever preferred_lft forever
client0 ESSID: "l2tp.freifunk.4830.org"
Access Point: C6:5C:AF:7A:9C:78
Mode: Master Channel: 1 (2.412 GHz)
Tx-Power: 18 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
mesh0 ESSID: "21:de:ca:fb:ad:ff"
Access Point: C6:5C:AF:7A:9C:79
Mode: Mesh Point Channel: 1 (2.412 GHz)
Tx-Power: 18 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
wlan0-1 ESSID: "UU FFGT"
Access Point: C6:5C:AF:7A:9C:7B
Mode: Master Channel: 1 (2.412 GHz)
Tx-Power: 18 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
Also ja, geht