The situation when Kali Linux After installation, it fails to detect wireless networks, a common pitfall for information security novices. Most often, the problem lies not in hardware failure, but in the absence of proprietary drivers or the need to manually activate the interface. Unlike custom distributions, where everything works out of the box, Kali A deeper understanding of the network subsystem is required.
Ignoring this point may result in you being left without internet access while working, unable to download missing packages. Wireless adapter It may be physically functional, but disabled by software or blocked by kernel mechanisms. Understanding the architecture of Linux hardware interactions is the first step to successful configuration.
In some cases, the system detects the device but is unable to switch it to the required operating mode. This is especially relevant for those planning to audit network security. Let's explore why this happens and what tools can help restore connectivity.
RFKill Physical Condition and Blockage Check
The first thing you need to do is make sure that the WiFi module isn't blocked by software or hardware. There's a utility available in Linux rfkill, which controls the state of radio interfaces. It often happens that after a reboot or installation, the system puts wireless modules into a "soft block" state to save power or due to BIOS settings.
Run the command rfkill list in the terminal. You'll see a list of all radio devices and their current status. If you see "Soft blocked: yes," the blocking is software-based and can be removed. If "Hard blocked: yes" appears, the issue is with a physical switch on the laptop or a key combination (e.g., Fn+F2).
β οΈ Attention: Do not attempt to forcibly remove the WiFi module from the M.2 slot or USB port while the system is running, as this may damage the power controller.
To remove the software lock, use the command sudo rfkill unblock wifi or sudo rfkill unblock allIf you want to unblock all radio interfaces at once, you should check the status again. If the indicators are off or change color, the path to the adapter is open.
- π Run the command
ip linkto view the list of network interfaces. - π Check for interfaces
wlan0orwlx...in the conclusion. - π Make sure the interface status is not marked as
DOWN.
Chipset identification and driver search
If there are no blockages, but the network does not appear, most likely the system does not have the necessary driversKali Linux, being based on Debian, does not include proprietary firmware files in the standard image for licensing reasons. You need to accurately determine the chipset model of your adapter.
Use the utility lsusb for USB adapters or lspci For internal cards, you'll find lines like "Realtek Semiconductor Corp. RTL8812AU" or "Atheros Communications Inc. AR9271" in the output. These identifiers (Vendor ID and Product ID) are critical for finding the correct driver.
Users often encounter the adapter being identified as an unknown device. In this case, the following command will help: dmesg | grep -i usb or dmesg | grep -i firmware, which will show the kernel's attempts to load the microcode. Errors in the logs will point to the specific missing file.
| Manufacturer | Popular chipsets | Support in Kali | Difficulty of installation |
|---|---|---|---|
| Realtek | RTL8812AU, RTL8821CU | Requires compilation | Average |
| Atheros | AR9271, AR9380 | Native | Low |
| Ralink | RT3070, RT5370 | Native | Low |
| MediaTek | MT7921, MT7612 | Partial | High |
Installing drivers via the repository
The easiest way to solve the problem is to use the standard Kali repositories. For many popular adapters, especially from Atheros and old RealtekThe packages are already compiled and ready for installation. You will need an internet connection via an Ethernet cable or USB modem (Android/iOS).
Update package lists with the command sudo apt updateThen try searching for the driver by chipset name. For example, for some Realtek cards, the package firmware-realtek, and for Broadcom - firmware-b43-installerInstallation is carried out through apt install.
sudo apt install firmware-realtek firmware-misc-nonfreeAfter installation, you'll need to reboot the system or reconnect the USB device so the kernel picks up the new module. If the standard packages don't help, you'll have to resort to manual compilation from source code, which requires the kernel header files.
Compiling drivers from source code
When ready-made binaries are not available, the driver must be compiled manually. This is a common situation for modern adapters that support the standard. 802.11ac and above. You will need the following build tools: build-essential, linux-headers And git.
The process usually looks like this: cloning a repository from GitHub (for example, from the alliance aircrack-ng or communities morrownr), navigate to the folder, and run the installation script. Be careful: driver versions may conflict with Linux kernel updates.
β οΈ Attention: When compiling third-party drivers, you assume responsibility for system stability. Incorrect code can cause a kernel panic.
If the module does not load after compilation, check the output modprobeSometimes you need to manually add a module to the configuration file or sign it with a key if enabled. Secure Boot in the BIOS. Disabling Secure Boot often solves the problem of loading untrusted modules.
- π οΈ Install packages:
sudo apt install build-essential linux-headers-$(uname -r). - π οΈ Clone the driver repository via
git clone. - π οΈ Run the installation script
install.shormake && sudo make install.
Setting up monitoring mode and network managers
Even if the driver is installed, Kali Linux may not see the network because the interface is in "Managed" mode and is managed by a network manager that hides details. Penetration testing often requires "Monitor" mode. Switching is performed using a utility. airmon-ng.
Team sudo airmon-ng start wlan0 will create a virtual monitoring interface. However, this may conflict with background processes. The system will prompt you to kill processes that interfere with operation (wpa_supplicant, NetworkManager). Only agree to this if you understand the consequences.
βοΈ WiFi Diagnostics in Kali
For a normal internet connection (not for attacks) it is better to use a graphical interface or nmcliNetworkManager sometimes blocks network visibility if the "managed=false" parameter is set in the configuration. Check the file /etc/NetworkManager/NetworkManager.conf.
Problems with VirtualBox and VMware
If you run Kali Linux In a virtual machine, the situation is more complicated. By default, virtualization doesn't forward the host's internal WiFi modules to the guest OS. You'll only see the wired interface. Wireless networks require a USB WiFi adapter.
You need to configure USB filters in the virtual machine settings to "capture" the device and pass it to Kali. After this, the adapter will be disabled in the host system (Windows/macOS) and appear as a new device in the guest system.
Why doesn't internal WiFi work in a virtual machine?
Virtual machines emulate a network card connected to the host. Direct access to the host's hardware radio module is impossible without specialized forwarding drivers, which are unstable. Therefore, using an external USB adapter is the only reliable solution for WiFi auditing in VMs.
Also, make sure that the USB 2.0 or 3.0 (EHCI/xHCI) controller is enabled in the VM settings. Without this, the adapter may be detected as a low-speed device or not detected at all. Install Guest Additions or VMware Tools for correct operation of drivers.
Additional diagnostic methods
If nothing helps, it's worth digging deeper. Use iwconfig to check the wireless interface parameters. The command iwlist scan It can show available networks even when the GUI is silent. This can help you understand whether your hardware is operating at a low level.
It is also worth checking if the connection is blocked Firewall (iptables/nftables). In rare cases, USB power saving issues can disable the adapter. Disabling USB auto-suspension via powertop or kernel parameters can save the situation.
What should I do if the adapter is detected but does not connect?
Try manually entering the IP address through ifconfig or ip addr, check the gateway and DNS. Often, the problem isn't with the driver, but with DHCP settings or an IP address conflict on the local network.
How do I know if my adapter supports packet injection?
Launch sudo airmon-ngThe device table will have a column labeled "Injection." If it's "yes," the adapter is suitable for security testing. If it's "no" or empty, it's only suitable for regular connections.
Can I use my phone as a WiFi adapter for Kali?
Yes, using the "USB Tethering" app on Android. The phone will act as an external network bridge. However, monitoring mode and injection are usually unavailable using this method, as the phone acts as a router.
Why did WiFi disappear after updating the kernel?
When updating the kernel (linux-image) Manually compiled driver modules often crash (DKMS may not work). You need to restart the driver compilation and installation process for the new kernel version.
Where can I find connection error logs?
Main magazine - /var/log/syslog or journalctl -u NetworkManagerSearch for keywords like "firmware", "failed", "association".