When is wlan0 not a wifi device?
by business_kid from LinuxQuestions.org on (#55JHF)
I have this weird issue that I have internet via wifi but cannot do any diagnostics on it. This is because my box doesn't know it has wifi.
Slackware64-Current as of 03-2020, wifi is Qualcomm Atheros AR 9485. No recent changes that I'm aware of - I don't update much. I bring up the interface, then the internet with a script that includes a line Code:wpa_supplicant <options> && dhcpcd wlan0 The interface comes up & stays up Code:root@RoseViolet:~# ifconfig -a
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.109 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::52b7:c3ff:fe50:d6b5 prefixlen 64 scopeid 0x20<link>
ether 50:b7:c3:50:d6:b5 txqueuelen 1000 (Ethernet)
RX packets 142858 bytes 183705408 (175.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 60296 bytes 7201970 (6.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0But if I want to do diagnostics (there are issues with bandwidth) I run into a wall. Code:root@RoseViolet:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 no wireless extensions.
root@RoseViolet:~# iwlist wlan0 scan
wlan0 Interface doesn't support scanning. (No lectures on root usage pls. It's one diagnostic terminal for 5 minutes).
My best guess is that the system has lost touch with the firmware, although the chip has it loaded and is doing it's thing. What I've just said sounds insane, and probably is, so feel free to call me out on this.
I really don't have a clue.
Slackware64-Current as of 03-2020, wifi is Qualcomm Atheros AR 9485. No recent changes that I'm aware of - I don't update much. I bring up the interface, then the internet with a script that includes a line Code:wpa_supplicant <options> && dhcpcd wlan0 The interface comes up & stays up Code:root@RoseViolet:~# ifconfig -a
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.109 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::52b7:c3ff:fe50:d6b5 prefixlen 64 scopeid 0x20<link>
ether 50:b7:c3:50:d6:b5 txqueuelen 1000 (Ethernet)
RX packets 142858 bytes 183705408 (175.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 60296 bytes 7201970 (6.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0But if I want to do diagnostics (there are issues with bandwidth) I run into a wall. Code:root@RoseViolet:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 no wireless extensions.
root@RoseViolet:~# iwlist wlan0 scan
wlan0 Interface doesn't support scanning. (No lectures on root usage pls. It's one diagnostic terminal for 5 minutes).
My best guess is that the system has lost touch with the firmware, although the chip has it loaded and is doing it's thing. What I've just said sounds insane, and probably is, so feel free to call me out on this.
I really don't have a clue.