[freifunk-public] Neue Experimental-FW 1.12.0~exp20250112
Sebastian Fontaine
fontaines at gmx.de
Di Jan 14 17:39:50 CET 2025
Hallo Keno, hallo Jan,
das sind ja tolle Neuigkeiten, so fängt das Jahr gut an.
Habe gleich mal einen Konten hergenommen und mit dieser Version
bespielt. Dabei fällt mir folgendes auf:
root at ffsaar-Kastanie2-Wohnung:~# echo 30 >
/sys/class/net/bat0/mesh/hop_penalty
-ash: can't create /sys/class/net/bat0/mesh/hop_penalty: nonexistent
directory
scp auf die Knoten geht auch nicht mehr:
ash: /usr/libexec/sftp-server: not found
scp: Connection closed
Ist das bei der neuen Version normal, bzw. gibt es jetzt einen anderen Weg?
Bin dann mal auf die Suche gegangen was andere Knoten so machen.
Weil ich schonmal den Eindruck hatte, dass öfter mal nicht das erste
Gateway gewählt wird.
Beispielsweise ffsaar-Voelzke-Perl
https://mgmt.saar.freifunk.net/hopglass/#!v:m;n:e8de27fd0d22
Gewähltes Gateway gw1.saar.freifunk.net -> ... -> gw3.saar.freifunk.net
Wieso geht der von einem Gateway über mindestens zwei weitere?
anders Beispiel: ffsaar-HammelsbergVe
https://mgmt.saar.freifunk.net/hopglass/#!v:m;n:c4e984f9c0b9
Gewähltes Gateway ffsaar-HammelsbergVb -> ffsaar-HammelsbergVa ->
gw3.saar.freifunk.net
Dabei hängen alle Zwischenrouter selbst mit ihrem WAN im Internet und
bauen eine eigene Verbindung auf.
Ein paar mehr Details zu den beiden Knoten im Anhang.
Grüße
Sebastian
Am 13.01.25 um 23:51 schrieb Hassler, Keno via freifunk-public:
> Hallo an alle,
>
> nach längerer Zeit gibt es wieder neue Experimental-Firmware (1.12.0~exp20250112). Dies ist die erste Firmware auf Basis von Gluon 2022.x, das leider viele beliebte Router, insbesondere von TP-Link, nicht mehr unterstützt (siehe unten).
> Um weiterhin auf dem bestehenden Pfad Notfall-Updates für die alte Version 1.11.x anbieten zu können, enthält diese Firmware auch einen neuen Pfad für Firmware-Updates (https://mgmt.saar.freifunk.net/firmware/experimental-gen2), auf dem künftig weitere Updates für 1.12+ ankommen werden. Falls eure Knoten auf den Experimental-Kanal eingestellt sind, sollten sie die neue Version automatisch installieren.
> Im Folgenden der Changelog:
>
> * Neues OpenWrt 22.03 mit Linux-Kernel 5.10 und wireless-backports 5.15
> * Neue CLI-Befehle:
> - `gluon-info` zeigt Informationen zum Knoten an.
> - `gluon-enter-setup-mode` startet den Knoten im Setup-Modus neu.
> * Wireguard-Unterstützung (noch ungenutzt, wird zukünftig vermutlich L2TP als VPN-Protokoll ersetzen)
>
> * Hinzugekommene Hardware-Unterstützung:
> - Arcadyan: o2 Box 6431
> - Aruba Networks: AP-303H, AP-365, InstantOn AP11D, InstantOn AP17
> - AVM: FRITZ!Box 7520
> - Cudy: WR2100, X6 (v1, v2)
> - D-Link: DAP-2660 A1, DAP-X1860 (A1), DGS-1210-10P
> - Enterasys: WS-AP3705i
> - Extreme Networks: WS-AP3825i
> - FriendlyElec: NanoPi R2S, NanoPi R4S (4GB LPDDR4)
> - GL.iNet: microuter-N300, GL-AP1300, GL-MT1300
> - LibreRouter: LibreRouter (v1)
> - Linksys: E8450
> - Mercusys: MR70X (v1)
> - Mikrotik: RB951Ui-2nD, SXTsq-5-AC, hAP ac2
> - Netgear: R6020, R6260, WAC104, WAX202
> - RAVPower: RP-WD009
> - Siemens: WS-AP3610
> - Sophos: RED 15w rev. 1
> - Teltonika: RUT230 (v1)
> - TP-Link: Archer A7 v5, CPE510 v2, CPE510 v3, CPE710 v1, EAP225-Outdoor v1, WBS210 v2, Archer C20 v4, Archer C20 v5, RE200 v2, RE200 (v3), RE305 v1, RE500, RE650 v1, TL-WDR4900 (v1)
> - Ubiquiti: UniFi 6 Lite, UniFi 6 LR
> - Xiaomi: AX3200, Mi Router 3G, Mi Router 3G (v2), Mi Router 4C, Mi Router 4A (100M Edition), Mi Router 4A (Gigabit Edition)
> - Zyxel: NWA50AX
>
> * Ausgelaufene Hardware-Unterstützung:
> - D-Link: DIR-615 (C1, D1, D2, D3, D4, H1)
> - Linksys: WRT160NL
> - TP-Link:
> * TL-MR13U (v1)
> * TL-MR3020 (v1)
> * TL-MR3040 (v1, v2)
> * TL-MR3220 (v1, v2)
> * TL-MR3420 (v1, v2)
> * TL-WA701N/ND (v1, v2)
> * TL-WA730RE (v1)
> * TL-WA750RE (v1)
> * TL-WA801N/ND (v1, v2, v3)
> * TL-WA830RE (v1, v2)
> * TL-WA850RE (v1)
> * TL-WA860RE (v1)
> * TL-WA901N/ND (v1, v2, v3, v4, v5)
> * TL-WA7210N (v2)
> * TL-WA7510N (v1)
> * TL-WR703N (v1)
> * TL-WR710N (v1, v2)
> * TL-WR740N (v1, v3, v4, v5)
> * TL-WR741N/ND (v1, v2, v4, v5)
> * TL-WR743N/ND (v1, v2)
> * TL-WR840N (v2)
> * TL-WR841N/ND (v3, v5, v7, v8, v9, v10, v11, v12)
> * TL-WR841N/ND (v1, v2)
> * TL-WR843N/ND (v1)
> * TL-WR940N (v1, v2, v3, v4, v5, v6)
> * TL-WR941ND (v2, v3, v4, v5, v6)
> * TL-WR1043N/ND (v1)
> * TL-WDR4900 (v2)
> - Ubiquiti: AirGateway, AirGateway Pro, AirRouter, Bullet, LS-SR71, Nanostation XM, Nanostation Loco XM, Picostation
> - Unknown: A5-V11
> - VoCore: VoCore (8M, 16M)
>
> * Wahrscheinlich ebenfalls ausgelaufen:
> * 8Devices: Carambola 2
> * Allnet: ALL0315
> * Buffalo: WZR-HP-G300NH2, WZR-HP-G450H
> * GL.iNet: 6408A v1
> * Netgear: WNDRMAC, WNDRMAC v2
> * TP-Link: WR2543
> * Ubiquiti: Rocket
> * WD: MyNet N600, MyNet N750
> * ZyXEL: NB6616, NB6716
>
> Wir haben übrigens bereits weitere Updates in Vorbereitung, um zum aktuellen Stand von Gluon aufzuschließen. Die allermeisten Geräte, die dieses Update unterstützen, werden auch die nächsten Updates installieren können.
>
> Viele Grüße
> Keno
>
-------------- nächster Teil --------------
root at ffsaar-Voelzke-Perl:~# /bin/nodeinfo-local.sh
runtime: Tue Jan 14 17:38:08 CET 2025
### hostname : ffsaar-Voelzke-Perl
### IP : inet6 addr: 2a03:2260:3009:2400:eade:27ff:fefd:d22/64 Scope:Global
default via 192.168.101.2 dev br-wan src 192.168.101.30
10.24.240.0/20 dev local-node scope link src 10.24.240.255
192.168.101.0/24 dev br-wan scope link src 192.168.101.30
### from ssh : 2a03:2260:3009:2200:4885:b659:a78c:fc78 50746 2a03:2260:3009:2200:eade:27ff:fefd:d22 22
### uptime : 17:38:09 up 12:34, load average: 0.00, 0.00, 0.00
### firmware : 1.11.1
### hardware : TP-Link TL-WR1043N/ND v2
### Radio-Networks acitve:client0 ESSID: "saar.freifunk.net"
Access Point: 22:01:5E:6B:31:58
Mode: Master Channel: 1 (2.412 GHz)
Tx-Power: 14 dBm Link Quality: 65/70
Signal: -45 dBm Noise: -95 dBm
Bit Rate: 65.0 MBit/s
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: "24.66:66:73:61:61:72/mzg"
Access Point: 22:01:5E:6B:31:59
Mode: Mesh Point Channel: 1 (2.412 GHz)
Tx-Power: 14 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
### connected to this node : 1
### number of total clients : 69
### Mesh: MoL: MoW: Fastd:
### BatIFs:
primary0: active
mesh0: active
mesh-vpn: active
batctl gw : client (selection class: 20)
### BatGateways
[B.A.T.M.A.N. adv openwrt-2019.2-14, MainIF/MAC: primary0/22:01:5e:6b:31:5b (bat0/e8:de:27:fd:0d:22 BATMAN_IV)]
Router ( TQ) Next Hop [outgoingIf] Bandwidth
ca:fe:ba:be:02:02 (224) ca:fe:ba:be:02:01 [ mesh-vpn]: 500.0/500.0 MBit
ca:fe:ba:be:02:04 (225) ca:fe:ba:be:02:01 [ mesh-vpn]: 1000.0/1000.0 MBit
* ca:fe:ba:be:02:03 (225) ca:fe:ba:be:02:01 [ mesh-vpn]: 1000.0/1000.0 MBit
### Location: Geo?:'1' lon:'6.388394237' lat:'49.474712504' Contact:'mail at sfinp.de'
Mesh neighbours:
### WAN network status:
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 45269,
"l3_device": "br-wan",
"proto": "dhcp",
"device": "br-wan",
"updated": [
"addresses",
"routes",
"data"
],
"metric": 0,
"dns_metric": 0,
"delegation": true,
"ipv4-address": [
{
"address": "192.168.101.30",
"mask": 24
}
],
"ipv6-address": [
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
{
"target": "0.0.0.0",
"mask": 0,
"nexthop": "192.168.101.2",
"source": "192.168.101.30/32"
}
],
"dns-server": [
],
"dns-search": [
],
"neighbors": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
"192.168.101.2"
],
"dns-search": [
"fritz.box"
],
"neighbors": [
]
},
"data": {
"leasetime": 864000,
"ntpserver": "192.168.101.2"
}
}
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 45265,
"l3_device": "br-wan",
"proto": "dhcpv6",
"device": "br-wan",
"ip6table": 1,
"metric": 0,
"dns_metric": 0,
"delegation": true,
"ipv4-address": [
],
"ipv6-address": [
{
"address": "2a00:6020:5019:a800:eade:27ff:fefd:d23",
"mask": 64,
"preferred": 2580,
"valid": 6775
},
{
"address": "fdd0:16c0:7ece:0:eade:27ff:fefd:d23",
"mask": 64,
"preferred": 3175,
"valid": 6775
}
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
{
"target": "2a00:6020:5019:a800::",
"mask": 64,
"nexthop": "::",
"metric": 256,
"valid": 6775,
"source": "::/0"
},
{
"target": "fdd0:16c0:7ece::",
"mask": 64,
"nexthop": "::",
"metric": 256,
"valid": 6775,
"source": "::/0"
},
{
"target": "fdd0:16c0:7ece::",
"mask": 64,
"nexthop": "fe80::52e6:36ff:fec5:b039",
"metric": 512,
"valid": 1375,
"source": "::/0"
},
{
"target": "2a00:6020:5019:a800::",
"mask": 56,
"nexthop": "fe80::52e6:36ff:fec5:b039",
"metric": 512,
"valid": 1375,
"source": "::/0"
},
{
"target": "::",
"mask": 0,
"nexthop": "fe80::52e6:36ff:fec5:b039",
"metric": 512,
"valid": 1375,
"source": "::/0"
}
],
"dns-server": [
],
"dns-search": [
],
"neighbors": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
"fdd0:16c0:7ece:0:52e6:36ff:fec5:b039",
"2a00:6020:5019:a800:52e6:36ff:fec5:b039"
],
"dns-search": [
],
"neighbors": [
]
},
"data": {
"passthru": "00170020fdd016c07ece000052e636fffec5b0392a0060205019a80052e636fffec5b03900380028000100102a0060205019a80052e636fffec5b03900010010fdd016c07ece000052e636fffec5b039005600102a0060205019a80052e636fffec5b039"
}
}
### WAN DNS:
nameserver fdd0:16c0:7ece:0:52e6:36ff:fec5:b039
nameserver 2a00:6020:5019:a800:52e6:36ff:fec5:b039
nameserver 192.168.101.2
### nslookup-test: /usr/bin/gluon-wan /usr/bin/nslookup www.heise.de
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: www.heise.de
Address 1: 193.99.144.85
Address 2: 2a02:2e0:3fe:1001:7777:772e:2:85
error-code: 0
### ping-test: /usr/bin/gluon-wan /bin/ping -c 4 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=52 time=9.708 ms
64 bytes from 1.1.1.1: seq=1 ttl=52 time=8.538 ms
64 bytes from 1.1.1.1: seq=2 ttl=52 time=8.803 ms
64 bytes from 1.1.1.1: seq=3 ttl=52 time=8.430 ms
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 8.430/8.869/9.708 ms
error-code: 0
root at ffsaar-Voelzke-Perl:~#
-------------- nächster Teil --------------
root at ffsaar-Kastanie2-Wohnung:~# /bin/nodeinfo-local.sh
runtime: Tue Jan 14 17:36:21 CET 2025
### hostname : ffsaar-Kastanie2-Wohnung
### IP : inet6 addr: 2a03:2260:3009:2400:9683:c4ff:fe03:103/64 Scope:Global
default via 192.168.178.1 dev br-wan src 192.168.178.55
10.24.240.0/20 dev local-node scope link src 10.24.240.255
192.168.178.0/24 dev br-wan scope link src 192.168.178.55
### from ssh : 2a03:2260:3009:2200:4885:b659:a78c:fc78 50748 2a03:2260:3009:2200:9683:c4ff:fe03:103 22
### uptime : 17:36:21 up 8 min, load average: 0.24, 0.30, 0.24
### firmware : 1.12.0~exp20250112
### hardware : GL.iNet GL-AR750
### Radio-Networks acitve:client0 ESSID: "saar.freifunk.net"
Access Point: DA:B1:9E:6F:88:C8
Mode: Master Channel: 36 (5.180 GHz) HT Mode: HT20
Center Channel 1: 36 2: unknown
Tx-Power: 20 dBm Link Quality: 67/70
Signal: -43 dBm Noise: -103 dBm
Bit Rate: 6.0 MBit/s
Encryption: none
Type: nl80211 HW Mode(s): 802.11ac/n
Hardware: 168C:0050 0000:0000 [Qualcomm Atheros QCA9887]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
client1 ESSID: "saar.freifunk.net"
Access Point: DA:B1:9E:6F:88:CC
Mode: Master Channel: 1 (2.412 GHz) HT Mode: HT20
Center Channel 1: 1 2: unknown
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -92 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11b/g/n
Hardware: 168C:0033 168C:9530 [Qualcomm Atheros QCA9530]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
mesh0 ESSID: "50.66:66:73:61:61:72/mzg"
Access Point: DA:B1:9E:6F:88:C9
Mode: Mesh Point Channel: 36 (5.180 GHz) HT Mode: HT20
Center Channel 1: 36 2: unknown
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -103 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11ac/n
Hardware: 168C:0050 0000:0000 [Qualcomm Atheros QCA9887]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
mesh1 ESSID: "24.66:66:73:61:61:72/mzg"
Access Point: DA:B1:9E:6F:88:CD
Mode: Mesh Point Channel: 1 (2.412 GHz) HT Mode: HT20
Center Channel 1: 1 2: unknown
Tx-Power: 20 dBm Link Quality: 28/70
Signal: -82 dBm Noise: -92 dBm
Bit Rate: 61.4 MBit/s
Encryption: none
Type: nl80211 HW Mode(s): 802.11b/g/n
Hardware: 168C:0033 168C:9530 [Qualcomm Atheros QCA9530]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
wan0 ESSID: "fontaines"
Access Point: DA:B1:9E:6F:88:CB
Mode: Master Channel: 36 (5.180 GHz) HT Mode: HT20
Center Channel 1: 36 2: unknown
Tx-Power: 20 dBm Link Quality: 53/70
Signal: -57 dBm Noise: -103 dBm
Bit Rate: 6.0 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/n
Hardware: 168C:0050 0000:0000 [Qualcomm Atheros QCA9887]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
wan1 ESSID: "fontaines"
Access Point: DA:B1:9E:6F:88:CF
Mode: Master Channel: 1 (2.412 GHz) HT Mode: HT20
Center Channel 1: 1 2: unknown
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -92 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11b/g/n
Hardware: 168C:0033 168C:9530 [Qualcomm Atheros QCA9530]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
### connected to this node : 1
### number of total clients : 68
### Mesh: MoL: MoW: Fastd:
### BatIFs:
primary0: active
mesh1: active
mesh0: active
mesh-vpn: active
batctl gw : client (selection class: 20)
### BatGateways
[B.A.T.M.A.N. adv 2022.0-openwrt-7, MainIF/MAC: primary0/da:b1:9e:6f:88:cb (bat0/94:83:c4:03:01:03 BATMAN_IV)]
Router ( TQ) Next Hop [outgoingIf] Bandwidth
ca:fe:ba:be:02:03 (217) ca:fe:ba:be:02:02 [ mesh-vpn]: 1000.0/1000.0 MBit
ca:fe:ba:be:02:04 (217) ca:fe:ba:be:02:02 [ mesh-vpn]: 1000.0/1000.0 MBit
* ca:fe:ba:be:02:02 (247) ca:fe:ba:be:02:02 [ mesh-vpn]: 500.0/500.0 MBit
### Location: Geo?:'1' lon:'6.388539076' lat:'49.469612643' Contact:'mail at sfinp.de'
Mesh neighbours:
Station e6:0a:ad:57:3d:19 (on mesh1)
Station 12:70:6a:eb:ff:31 (on mesh1)
### WAN network status:
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 492,
"l3_device": "br-wan",
"proto": "dhcp",
"device": "br-wan",
"metric": 0,
"dns_metric": 0,
"delegation": true,
"ipv4-address": [
{
"address": "192.168.178.55",
"mask": 24
}
],
"ipv6-address": [
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
{
"target": "0.0.0.0",
"mask": 0,
"nexthop": "192.168.178.1",
"source": "192.168.178.55/32"
}
],
"dns-server": [
],
"dns-search": [
],
"neighbors": [
],
"inactive": {
"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
"192.168.178.1"
],
"dns-search": [
"localdomain"
],
"neighbors": [
]
},
"data": {
"dhcpserver": "192.168.178.1",
"hostname": "ffsaar-Kastanie2-Wohnung",
"leasetime": 86400
}
}
{
"up": false,
"pending": true,
"available": true,
"autostart": true,
"dynamic": false,
"proto": "dhcpv6",
"device": "br-wan",
"data": {
}
}
### WAN DNS:
nameserver 192.168.178.1
### nslookup-test: /usr/bin/gluon-wan /usr/bin/nslookup www.heise.de
Server: 127.0.0.1
Address: 127.0.0.1:53
Non-authoritative answer:
Name: www.heise.de
Address: 193.99.144.85
Non-authoritative answer:
Name: www.heise.de
Address: 2a02:2e0:3fe:1001:7777:772e:2:85
error-code: 0
### ping-test: /usr/bin/gluon-wan /bin/ping -c 4 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=52 time=10.916 ms
64 bytes from 1.1.1.1: seq=1 ttl=52 time=10.443 ms
64 bytes from 1.1.1.1: seq=2 ttl=52 time=12.239 ms
64 bytes from 1.1.1.1: seq=3 ttl=52 time=9.917 ms
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 9.917/10.878/12.239 ms
error-code: 0
root at ffsaar-Kastanie2-Wohnung:~#
Mehr Informationen über die Mailingliste freifunk-public