Thomas
(Thomas Hollenbeck)
8. Oktober 2016 um 16:47
1
Hallo,
mir ist gerade aufgefallen das mitlerweile die Privaten Wlans auf der Statusseite nicht mehr angezeit werden. Das geschieht aber aktuell scheinbar nur bei 2,4GHz Netzen.
Siehe hier:
(without private WLAN, if enabled)
client0 ESSID: »KreisGT.freifunk.net «
Access Point: A6:2D:B1:F4:3A:87
Mode: Master Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: 23/70
Signal: -87 dBm Noise: -103 dBm
Bit Rate: 6.0 MBit/s
Encryption: none
Type: nl80211 HW Mode(s): 802.11nac
Hardware: 168C:003C 0000:0000 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
client1 ESSID: »KreisGT.freifunk.net «
Access Point: A6:2D:B2:F4:3A:87
Mode: Master Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 42/70
Signal: -68 dBm Noise: -95 dBm
Bit Rate: 34.3 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: phy1
mesh1 ESSID: »00:42:de:ca:fb:ad«
Access Point: 00:42:DE:CA:FB:AD
Mode: Ad-Hoc Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 51/70
Signal: -59 dBm Noise: -95 dBm
Bit Rate: 180.0 MBit/s
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: phy1
wlan0 ESSID: »Erle«
Access Point: A4:2B:B0:F4:3A:85
Mode: Master Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -103 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11nac
Hardware: 168C:003C 0000:0000 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
wusel
(Kai 'wusel' Siering)
8. Oktober 2016 um 17:20
2
Oops. Gucke nachher mal; danke für’s finden & reporten
wusel
(Kai 'wusel' Siering)
8. Oktober 2016 um 20:43
3
Hmm.
Die Codezeile lautet:
io.write(util.exec(“for i in iwinfo | awk '/^[[:space:]]/ {next;} /ESSID/ {print $1;}' | grep -v wlan.-
; do iwinfo $i info ; echo ; done”))
Das tut bei mir auch, vgl. http://[2a03:2260:117:1000:26a4:3cff:feb1:11d9]/cgi-bin/status
WiFi status
(without private WLAN, if enabled)
client0 ESSID: "KreisGT.freifunk.net"
Access Point: 26:A6:3D:B1:11:D9
Mode: Master Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11an
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
mesh0 ESSID: "00:42:de:ca:fb:ad"
Access Point: 00:42:DE:CA:FB:AD
Mode: Ad-Hoc Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11an
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
mesh1 ESSID: "00:42:de:ca:fb:ad"
Access Point: 00:42:DE:CA:FB:AD
Mode: Ad-Hoc Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 42/70
Signal: -68 dBm Noise: -95 dBm
Bit Rate: 153.2 MBit/s
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 168C:0033 0777:E507 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
Auf dem Knoten:
root@33332-Schalueckstr-107-11d9:~# iwinfo
client0 ESSID: "KreisGT.freifunk.net"
Access Point: 26:A6:3D:B1:11:D9
Mode: Master Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11an
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
mesh0 ESSID: "00:42:de:ca:fb:ad"
Access Point: 00:42:DE:CA:FB:AD
Mode: Ad-Hoc Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11an
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
mesh1 ESSID: "00:42:de:ca:fb:ad"
Access Point: 00:42:DE:CA:FB:AD
Mode: Ad-Hoc Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 41/70
Signal: -69 dBm Noise: -95 dBm
Bit Rate: 110.5 MBit/s
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 168C:0033 0777:E507 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
wlan0-1 ESSID: "UU FFGT"
Access Point: 24:A4:3C:B1:11:D9
Mode: Master Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11an
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
wlan1-1 ESSID: "UU FFGT"
Access Point: 24:A4:3C:B2:11:D9
Mode: Master Channel: 9 (2.452 GHz)
Tx-Power: 20 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: 168C:0033 0777:E507 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
Sprich: eigentlich sollte das private WLAN wlan%d-%d sein, nicht, wie bei Dir, wlan0; und wlan.- als Pattern wird – erfolgreich – ausgefiltert. Hmm, 802.11nac — Archer C5/C7? Kannste mir mal die /etc/config/wireless
(WPA-PW wipen nicht vergessen) & /etc/config/network
schicken ?