New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3643 - iwinfo returns bad data #8680
Comments
Goerge255: Also, the contents of the:
root@OpenWrt:/etc/config# cat wireless
...and all of these radios operate in the |
Goerge255: Also, note that
root@OpenWrt:~# airmon-ng
|
jow-: Please attach the output of |
wulfy23: seeing oddities also on master @ 2021-02-27ish ( running build date... no idea when introduced likely a week or two previous to this ) attach strace crashes flyspray rpi4 note: the phantom 'wlan0' ...
[root@dca632 /usbstick 50°]# iwinfo
wlan0 ESSID: unknown
Access Point: DC:A6:32:56:31:78
Mode: Client Channel: 36 (5.180 GHz)
Center Channel 1: 36 2: unknown
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: -95 dBm
Bit Rate: unknown
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11bgnac
Hardware: 02D0:A9A6 0000:0000 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: no PHY name: phy1
[root@dca632 /usbstick 51°]# cat /etc/config/wireless
|
jow-: I need the strace, as well as the |
Goerge255:
root@OpenWrt:~# strace iwconfig
root@OpenWrt:~# iwinfo
|
Goerge255:
root@OpenWrt:~# ubus call network.wireless status
I can see that the device "path" for the |
Goerge255: So this apparently is a bug. Is anyone going to help correct it? |
Goerge255:
OpenWrt 19.07.7 r11306-c4a6851c72 / LuCI openwrt-19.07 branch git-21.054.03371-3b137b5
Device: Netgear R6120
Bad data returned by
iwinfo
for a wireless adapter connected via USB.root@OpenWrt:~# iwinfo
wlan0 ESSID: "myssid0"
Access Point: BA:AD:F0:0D:BA:AD
Mode: Client Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 51/70
Signal: -59 dBm Noise: unknown
Bit Rate: 52.0 MBit/s
Encryption: WPA2 PSK (TKIP, CCMP)
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 14C3:7628 14C3:0004 [MediaTek MT76x8]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
wlan1 ESSID: "myssid1"
Access Point: BA:AD:F0:0D:BA:DD
Mode: Client Channel: 44 (5.220 GHz)
Tx-Power: 20 dBm Link Quality: 43/70
Signal: -67 dBm Noise: unknown
Bit Rate: 54.0 MBit/s
Encryption: WPA2 PSK (TKIP, CCMP)
Type: nl80211 HW Mode(s): 802.11nac
Hardware: 14C3:7662 14C3:7662 [MediaTek MT76x2E]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
wlan2 ESSID: "myssid2"
Access Point: BA:AA:AD:F0:00:0D
Mode: Client Channel: 9 (2.452 GHz)
Tx-Power: 20 dBm Link Quality: 56/70
Signal: -54 dBm Noise: unknown
Bit Rate: 150.0 MBit/s
Encryption: WPA2 PSK (TKIP, CCMP)
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 14C3:7628 14C3:0004 [MediaTek MT76x8]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy2
Notice that the same
Hardware
line is returned forwlan0
andwlan2
despite different MAC addresses and differentPHY names
.The wlan2 hardware is the ALFA AWUS036NHA and `lsusb' identifies it as:
root@OpenWrt:~# lsusb -v | grep ID
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It is worth mentioning that the
wlan2
interface is fully functional.The text was updated successfully, but these errors were encountered: