Moin,
für’s Setup sei auf die Grafik verwiesen. »Node X« eine AVM FRITZ!Box 4040 (19.07-SNAPSHOT / Gluon v2021.1.x), »Node A« ein GL.iNet GL-MT1300 (22.03-SNAPSHOT / Gluon v2022.1.x).
Aus $Gründen möchte ich mit VHT-20, VHT-40, VHT-80 rumspielen, und daher wollte ich auf Frequenzen jenseits UNII-1 zurückgreifen — sprich auf DFS-pflichtige Känäle. Allein, weder auf Kanal 104 (UNII-2 Extended) noch auf Kanal 52 (UNII-2) kommt ein Link zustande:
root@33332-MT7615E-v2022-cd9d:~# iwinfo client1 info
client1 ESSID: "bielefeld.freifunk.net"
Access Point: BE:79:5B:EB:6D:4C
Mode: Master Channel: 100 (5.500 GHz) HT Mode: HT40
Center Channel 1: 102 2: unknown
Tx-Power: 23 dBm Link Quality: unknown/70
Signal: unknown Noise: -87 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11ac/n
Hardware: 14C3:7615 7615:14C3 [MediaTek MT7615E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
root@33332-MT7615E-v2022-cd9d:~# iwinfo mesh1 info
mesh1 ESSID: "17:47:de:ca:fb:ad"
Access Point: BE:79:5B:EB:6D:4D
Mode: Mesh Point Channel: unknown (unknown) HT Mode: NOHT
Center Channel 1: unknown 2: unknown
Tx-Power: 23 dBm Link Quality: unknown/70
Signal: unknown Noise: -87 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11ac/n
Hardware: 14C3:7615 7615:14C3 [MediaTek MT7615E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
root@33332-4040-v2021-c3a7:~# iwinfo client1 info
client1 ESSID: "FF_OFFLINE_33332-40...021-c3a7"
Access Point: 6E:AA:42:F2:B8:64
Mode: Master Channel: 100 (5.500 GHz)
Tx-Power: 26 dBm Link Quality: unknown/70
Signal: unknown Noise: -103 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11nac
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
root@33332-4040-v2021-c3a7:~# iwinfo mesh1 info
mesh1 ESSID: "17:47:de:ca:fb:ad"
Access Point: 6E:AA:42:F2:B8:65
Mode: Mesh Point Channel: unknown (unknown)
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: -103 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11nac
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
Hmm?
EDIT: augenscheinlich eine Regression aus OpenWrt 21.02.3. Auch als OpenWrt-Issue existent, unresolved seit 28.02.2023. Lovin’ it … (Gäbe es doch nur einen Gluon- unter den OpenWrt-Entwicklern. Oh, wait …)
So I’ve now updated both the R7800 and the AVM3000 to the latest 22.03 snapshot and things have started to deteriorate even more. With the AVM on 22.03, the mesh doesn’t even work with
option country 'US'
anymore. At least not reliably. Every once in a while when poking various parameters, everything would start to work miraculously, until the next boot. Maybe I should have a look at the mainline ath10k firmware again?Anyway, on the R7800,
iw dev if-mesh mesh_param dump
has stopped working, it just lists the help text instead. Getting and setting individual parameters (e.g.iw dev if-mesh get mesh_param mesh_ttl
) works fine however.
Meh!