<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi Ralf,<br>
<br>
habe gerade manuell ein update von folgenden Knoten gemacht:<br>
ffsaar-RuFV-klHalle, ffsaar-RuFV-Einsteller1,
ffsaar-RuFV-Einsteller2, ffsaar-RuFV-Einsteller3<br>
<br>
alt:<br>
OpenWrt 19.07-SNAPSHOT, r11328+12-81266d9001<br>
gluon-ffsaar 1.10.1 / gluon v2020.2.3<br>
<br>
neu: <br>
OpenWrt 19.07-SNAPSHOT, r11354+25-ffd4452f8b<br>
gluon-ffsaar 1.11.0 / gluon v2021.1.1<br>
<br>
Im Resultat, sind sie von der Karte "verschwunden"<br>
<img src="cid:part1.MZryxxo1.bOTvz04Z@gmx.de" alt=""><br>
<br>
Die entsprechende Konfig ist aber unverändert, sprich, sie sind auch
per ssh erreichbar:<br>
root@ffsaar-RuFV-klHalle:~# cat /etc/config/gluon-node-info <br>
<br>
config location<br>
option share_location '1'<br>
option latitude '49.530890825'<br>
option longitude '6.414288282'<br>
<br>
config owner<br>
option contact '<a class="moz-txt-link-abbreviated" href="mailto:mail@sfinp.de">mail@sfinp.de</a>'<br>
<br>
config system<br>
<br>
root@ffsaar-RuFV-klHalle:~#<br>
<br>
Versuchshalber habe ich dann noch ein update an folgendem Knoten
angestoßen:<br>
ffsaar-RuFV-grHalle<br>
<br>
Und folgerichtig "verschwindet" der auch von der Karte:<br>
<img src="cid:part2.4horIKvt.J05mMYFv@gmx.de" alt=""><br>
<br>
Wie erklärt sich das denn?<br>
<br>
Grüße<br>
Sebastian<br>
<br>
<div class="moz-cite-prefix">Am 30.12.21 um 21:36 schrieb Fam.
Fontaine:<br>
</div>
<blockquote type="cite"
cite="mid:945485ed-a68d-ff0c-531e-c1c4e3aa042c@gmx.de">Hi,
<br>
<br>
habe da ein Phänomen, das ist nicht verstehe. Im besten Fall fehlt
mir ein kleiner Hinweis.
<br>
Ich habe hier einen Knoten, der seit über einem Jahr läuft und
jetzt nicht mehr auf der Karte auftaucht.
<br>
Allerdings kann ich mich per SSH verbinden und eigentlich sieht
für mich alles gut aus.
<br>
Er hat die jüngste Firmware, aber irgendwas stimmt trotzdem nicht,
sonst wäre er ja im Hopglas sichtbar.
<br>
<br>
Hier ein wenig output, logs, etc.
<br>
<br>
SFmba:Freifunk fontaines$ ssh -l root ffsaar-Papierstbchen-Perl
<br>
<br>
<br>
BusyBox v1.30.1 () built-in shell (ash)
<br>
<br>
_____ _____
<br>
_/ ____\/ ____\___________ _____ _______
<br>
\ __\\ __\/ ___/\__ \ \__ \\_ ___\
<br>
| | | | \___ \ / __ \_/ __ \| |
<br>
|__| |__| /_____/ (_____/(_____//__|
<br>
-----------------------------------------------------
<br>
OpenWrt 19.07-SNAPSHOT, r11354+25-ffd4452f8b
<br>
gluon-ffsaar 1.11.0 / gluon v2021.1.1
<br>
-----------------------------------------------------
<br>
Gluon commandline administration reference:
<br>
<a class="moz-txt-link-freetext" href="https://github.com/freifunk-gluon/gluon/wiki/Commandline-administration">https://github.com/freifunk-gluon/gluon/wiki/Commandline-administration</a>
<br>
-----------------------------------------------------
<br>
root@ffsaar-Papierstbchen-Perl:~# uptime
<br>
21:12:11 up 26 days, 11:26, load average: 0.00, 0.00, 0.00
<br>
root@ffsaar-Papierstbchen-Perl:~# crontab -l
<br>
*/6 * * * * /bin/awake-test.sh >/dev/null 2>&1
<br>
root@ffsaar-Papierstbchen-Perl:~# cat /etc/config/gluon-node-info
<br>
<br>
config location
<br>
option share_location '1'
<br>
option latitude '49.473453'
<br>
option longitude '6.386101'
<br>
<br>
config owner
<br>
option contact '<a class="moz-txt-link-abbreviated" href="mailto:mail@sfinp.de">mail@sfinp.de</a>'
<br>
<br>
config system
<br>
<br>
root@ffsaar-Papierstbchen-Perl:~# uci set
gluon-node-info.@location[0]='location
<br>
'; uci set gluon-node-info.@location[0].share_location='1';uci set
gluon-node-in
<br>
fo.@location[0].latitude='49.473464603';uci set
gluon-node-info.@location[0].lon
<br>
gitude='6.386103630';uci commit gluon-node-info
<br>
root@ffsaar-Papierstbchen-Perl:~#
<br>
<br>
root@ffsaar-Papierstbchen-Perl:~# /bin/nodeinfo_lokal.sh
<br>
runtime: Thu Dec 30 21:33:00 CET 2021
<br>
### hostname : ffsaar-Papierstbchen-Perl
<br>
### IP : inet6 addr:
2a03:2260:3009:2200:b2be:76ff:fe80:8358/64 Scope:Global
<br>
default via 192.168.2.1 dev br-wan src 192.168.2.100
<br>
10.24.240.0/20 dev local-node scope link src 10.24.240.255
<br>
192.168.2.0/24 dev br-wan scope link src 192.168.2.100
<br>
### from ssh : 2003:da:704:1a00:195a:b831:cf14:7b34 53000
2a03:2260:3009:2200:b2be:76ff:fe80:8358 22
<br>
### uptime : 21:33:00 up 18 min, load average: 0.03, 0.08, 0.08
<br>
### firmware : 1.11.0
<br>
### hardware : TP-Link TL-WR940N v6
<br>
### Radio-Networks acitve:wlan0 ESSID: unknown
<br>
Access Point: B0:BE:76:80:83:58
<br>
Mode: Client Channel: unknown (unknown)
<br>
Tx-Power: 20 dBm Link Quality: unknown/70
<br>
Signal: unknown Noise: unknown
<br>
Bit Rate: unknown
<br>
Encryption: unknown
<br>
Type: nl80211 HW Mode(s): 802.11bgn
<br>
Hardware: unknown [Generic MAC80211]
<br>
TX power offset: unknown
<br>
Frequency offset: unknown
<br>
Supports VAPs: yes PHY name: phy0
<br>
<br>
### connected to this node : 0
<br>
### number of total clients : 75
<br>
### Mesh: MoL: MoW: Fastd:
<br>
### BatIFs:
<br>
primary0: active
<br>
mesh-vpn: active
<br>
batctl gw : client (selection class: 20)
<br>
### BatGateways
<br>
[B.A.T.M.A.N. adv openwrt-2019.2-12, MainIF/MAC:
primary0/4a:c4:ec:81:5b:e3 (bat0/b0:be:76:80:83:58 BATMAN_IV)]
<br>
Router ( TQ) Next Hop [outgoingIf]
Bandwidth
<br>
ca:fe:ba:be:02:03 (225) ca:fe:ba:be:02:02 [ mesh-vpn]:
400.0/400.0 MBit
<br>
ca:fe:ba:be:02:01 (225) ca:fe:ba:be:02:02 [ mesh-vpn]:
400.0/400.0 MBit
<br>
* ca:fe:ba:be:02:02 (255) ca:fe:ba:be:02:02 [ mesh-vpn]:
200.0/200.0 MBit
<br>
ca:fe:ba:be:02:04 (225) ca:fe:ba:be:02:02 [ mesh-vpn]:
1000.0/1000.0 MBit
<br>
### Location: Geo?:'1' lon:'6.386103630' lat:'49.473464603'
Contact:'<a class="moz-txt-link-abbreviated" href="mailto:mail@sfinp.de">mail@sfinp.de</a>'
<br>
Mesh neighbours:
<br>
### WAN network status:
<br>
{
<br>
"up": true,
<br>
"pending": false,
<br>
"available": true,
<br>
"autostart": true,
<br>
"dynamic": false,
<br>
"uptime": 1075,
<br>
"l3_device": "br-wan",
<br>
"proto": "dhcp",
<br>
"device": "br-wan",
<br>
"updated": [
<br>
"addresses",
<br>
"routes",
<br>
"data"
<br>
],
<br>
"metric": 0,
<br>
"dns_metric": 0,
<br>
"delegation": true,
<br>
"ipv4-address": [
<br>
{
<br>
"address": "192.168.2.100",
<br>
"mask": 24
<br>
}
<br>
],
<br>
"ipv6-address": [
<br>
<br>
],
<br>
"ipv6-prefix": [
<br>
<br>
],
<br>
"ipv6-prefix-assignment": [
<br>
<br>
],
<br>
"route": [
<br>
{
<br>
"target": "0.0.0.0",
<br>
"mask": 0,
<br>
"nexthop": "192.168.2.1",
<br>
"source": "192.168.2.100/32"
<br>
}
<br>
],
<br>
"dns-server": [
<br>
<br>
],
<br>
"dns-search": [
<br>
<br>
],
<br>
"neighbors": [
<br>
<br>
],
<br>
"inactive": {
<br>
"ipv4-address": [
<br>
<br>
],
<br>
"ipv6-address": [
<br>
<br>
],
<br>
"route": [
<br>
<br>
],
<br>
"dns-server": [
<br>
"192.168.2.1",
<br>
"192.168.2.1"
<br>
],
<br>
"dns-search": [
<br>
"Speedport_W723_V_Typ_A_1_01_022"
<br>
],
<br>
"neighbors": [
<br>
<br>
]
<br>
},
<br>
"data": {
<br>
"leasetime": 1814400
<br>
}
<br>
}
<br>
{
<br>
"up": true,
<br>
"pending": false,
<br>
"available": true,
<br>
"autostart": true,
<br>
"dynamic": false,
<br>
"uptime": 1072,
<br>
"l3_device": "br-wan",
<br>
"proto": "dhcpv6",
<br>
"device": "br-wan",
<br>
"ip6table": 1,
<br>
"metric": 0,
<br>
"dns_metric": 0,
<br>
"delegation": true,
<br>
"ipv4-address": [
<br>
<br>
],
<br>
"ipv6-address": [
<br>
{
<br>
"address": "2003:da:717:9f01:b2be:76ff:fe80:8359",
<br>
"mask": 64,
<br>
"preferred": 1770,
<br>
"valid": 14370
<br>
}
<br>
],
<br>
"ipv6-prefix": [
<br>
<br>
],
<br>
"ipv6-prefix-assignment": [
<br>
<br>
],
<br>
"route": [
<br>
{
<br>
"target": "2003:da:717:9f01::",
<br>
"mask": 64,
<br>
"nexthop": "::",
<br>
"metric": 256,
<br>
"valid": 14370,
<br>
"source": "::/0"
<br>
},
<br>
{
<br>
"target": "::",
<br>
"mask": 0,
<br>
"nexthop": "fe80::1",
<br>
"metric": 384,
<br>
"valid": 150,
<br>
"source": "::/0"
<br>
}
<br>
],
<br>
"dns-server": [
<br>
<br>
],
<br>
"dns-search": [
<br>
<br>
],
<br>
"neighbors": [
<br>
<br>
],
<br>
"inactive": {
<br>
"ipv4-address": [
<br>
<br>
],
<br>
"ipv6-address": [
<br>
<br>
],
<br>
"route": [
<br>
<br>
],
<br>
"dns-server": [
<br>
"fe80::1"
<br>
],
<br>
"dns-search": [
<br>
<br>
],
<br>
"neighbors": [
<br>
<br>
]
<br>
},
<br>
"data": {
<br>
"passthru": "00170010fe800000000000000000000000000001"
<br>
}
<br>
}
<br>
### WAN DNS:
<br>
nameserver fe80::1%br-wan
<br>
nameserver 192.168.2.1
<br>
nameserver 192.168.2.1
<br>
### nslookup-test: /usr/bin/gluon-wan /usr/bin/nslookup
<a class="moz-txt-link-abbreviated" href="http://www.heise.de">www.heise.de</a>
<br>
Server: 127.0.0.1
<br>
Address: 127.0.0.1#53
<br>
<br>
Name: <a class="moz-txt-link-abbreviated" href="http://www.heise.de">www.heise.de</a>
<br>
Address 1: 193.99.144.85
<br>
Address 2: 2a02:2e0:3fe:1001:7777:772e:2:85
<br>
error-code: 0
<br>
### ping-test: /usr/bin/gluon-wan /bin/ping -c 4 1.1.1.1
<br>
PING 1.1.1.1 (1.1.1.1): 56 data bytes
<br>
64 bytes from 1.1.1.1: seq=0 ttl=55 time=31.558 ms
<br>
64 bytes from 1.1.1.1: seq=2 ttl=55 time=32.297 ms
<br>
64 bytes from 1.1.1.1: seq=3 ttl=55 time=31.796 ms
<br>
<br>
--- 1.1.1.1 ping statistics ---
<br>
4 packets transmitted, 3 packets received, 25% packet loss
<br>
round-trip min/avg/max = 31.558/31.883/32.297 ms
<br>
error-code: 0
<br>
root@ffsaar-Papierstbchen-Perl:~# reboot
<br>
...
<br>
root@ffsaar-Papierstbchen-Perl:~# uptime
<br>
21:34:55 up 20 min, load average: 0.10, 0.12, 0.09
<br>
root@ffsaar-Papierstbchen-Perl:~#
<br>
<br>
</blockquote>
<br>
</body>
</html>