Kali Linux WiFi Adapter Not Detected: Driver Fixes

Kali Linux WiFi adapter not detected: start here

You plug in a USB adapter, run iwconfig or ip a, and there is no wlan1. This is one of the most common Kali problems, and it nearly always comes down to one of four things: the adapter is not reaching Kali, the driver is missing, the firmware is missing, or the chipset cannot do what you want.

This guide is for adapters you own, used on networks you are authorised to test. Work through the steps in order, because each one narrows the problem. If you are still setting up the connection itself, see Kali Linux wpa_supplicant CLI config.

Step 1: does Kali see the hardware at all?

lsusb
dmesg | tail -30

Run both with the adapter plugged in. If the adapter does not appear in lsusb, the problem is physical or virtual, not a driver. Try another USB port, avoid unpowered hubs, and swap the cable.

If you run Kali in a virtual machine, this is where most people get stuck. The VM does not see USB devices by default. In VirtualBox or VMware, attach the adapter to the guest through the USB menu, and make sure the USB controller type is set to 2.0 or 3.0 as needed. Rebooting the VM with the adapter already attached often helps.

Step 2: is it listed but has no interface?

If the adapter shows in lsusb but not in iw dev, the driver did not bind. Look at the dmesg output for lines mentioning firmware or the chipset name. Note the USB ID, for example 0bda:8812, and search for it to find the chipset.

iw dev
ip link
rfkill list

Also check rfkill list. If the adapter shows as blocked, unblock it:

sudo rfkill unblock all

Step 3: update the system and kernel

A newer kernel often includes drivers that older ones lacked. Before building anything by hand, update fully and reboot:

sudo apt update && sudo apt full-upgrade -y
sudo reboot

Check the kernel with uname -r. Many adapters that needed extra drivers years ago now work out of the box on a current Kali release. Do not assume this for every chipset, though. Verify with iw dev after the reboot.

Step 4: install missing firmware or a driver

Some chipsets need firmware files that ship in separate packages:

sudo apt install firmware-realtek firmware-atheros firmware-misc-nonfree

For Realtek chips that still lack a driver, Kali packages some of the out-of-tree drivers as DKMS packages. Search first rather than cloning random repositories:

apt search realtek-rtl88
sudo apt install linux-headers-$(uname -r) dkms

Then install the package that matches your chipset. DKMS needs the kernel headers for the running kernel, so if the build fails, a headers mismatch is the usual cause. Reboot after installing and check iw dev again.

Step 5: test monitor mode and injection

Detection is only half of it. To confirm the adapter can do what a pentest needs:

sudo airmon-ng check kill
sudo airmon-ng start wlan1
sudo aireplay-ng --test wlan1

airmon-ng check kill stops NetworkManager and similar services that interfere. You will lose normal WiFi until you restart them with sudo systemctl start NetworkManager. A successful injection test reports that injection is working. You can also check iw list for “monitor” under supported interface modes. For how the tools fit together, see Aircrack-ng WiFi security testing on Kali.

Step 6: check the hardware revision

Vendors sometimes change the chipset under the same model name. A v2 or v3 of a popular adapter may use a completely different chip, with no monitor mode support. Compare the USB ID in lsusb with the one the original model used. If it differs, no driver will add features the chip lacks, and you will need a different adapter.

Quick checklist

1. Does lsusb show it? If not, fix the port or the VM passthrough.
2. Does iw dev show an interface? If not, check dmesg and rfkill.
3. Is Kali fully updated and rebooted?
4. Is the firmware package installed?
5. Does the chipset have a driver, in-kernel or DKMS?
6. Does iw list show monitor mode?

Work through the list and the cause is usually found by step three or four.