Working with wireless networks in the operating system Kali Linux Often encounters the primary obstacle—the lack of drivers for the Wi-Fi adapter immediately after installation. Unlike consumer distributions such as Ubuntu or Mint, this pentesting tool does not include proprietary modules by default for reasons of licensing purity and minimalism. The user must independently identify the device's chipset and download the appropriate software.
The difficulty often stems from a lack of internet access, as the driver is needed specifically for connecting to the network. A solution is to use a USB modem, an Ethernet cable, or pre-download the archives on another device. It's important to understand that installing drivers — this is a fundamental stage, without which neither network diagnostics nor security audits are possible.
In this article, we'll cover manual compilation methods, using a package manager, and working with repositories in detail. You'll learn how to identify the chip vendor, resolve dependency errors, and test the interface in monitoring mode. Proper hardware configuration ensures the stable operation of tools such as Aircrack-ng And Wireshark.
Identifying the Wi-Fi adapter and checking its status
The first step before any manipulation is to accurately determine the model of your network interface. Often, the label on the device's case contains a marketing name that doesn't reveal anything about the internal chipset. For example, an adapter may be sold under the TP-Link brand, but have a chip inside. Realtek or MediaTekIt is the chip manufacturer that determines the choice of driver.
To get technical information, connect the device to a USB port and run the command lsusb in the terminal. This will list all connected USB devices with their Vendor ID and Product ID. These hexadecimal codes are the key to finding the required driver in the repositories or on the manufacturer's website.
It is also useful to check whether the Linux kernel sees the device itself, even without a driver. The command dmesg | tail will show the latest system log messages, which often indicate an attempt to load a module or an error about its absence. If the device is detected as a network interface but is not working, check its presence via ip link or iwconfig.
The collected information will allow you to accurately classify the hardware. Without understanding the exact chip installed, driver installation will be a trial-and-error process, which is rarely successful. Write down or copy the device ID, as you'll need it to search compatibility databases.
Preparing the environment and installing dependencies
Before compiling or installing packages, you need to make sure your system has the tools to build software modules. The Linux kernel requires header files (headers), which correspond to the version of the currently running kernel. Missing these files is the most common cause of driver installation errors.
First, update your package lists to ensure the system is aware of the latest versions of available software. This is critical, as Kali's repositories are frequently updated. Next, install a basic set of compilation tools, including the GCC compiler, make utilities, and dkms scripts, which automatically rebuild modules when the kernel is updated.
sudo apt update
sudo apt install -y linux-headers-$(uname -r) build-essential git dkms
After installing the packages, it's recommended to reboot the system to ensure the new kernel headers are correctly integrated. If you're using a virtual machine, make sure the Guest Additions are also up to date, although USB port forwarding must be configured correctly for a physical Wi-Fi adapter to work.
☑️ Preparing to install drivers
It's important to note that package versions may change. If standard commands don't find packages, check the source list in the file /etc/apt/sources.listThe relevance of repositories directly affects the ability to automatically resolve dependencies.
Automatic installation via package manager
Many popular chipsets such as Atheros (AR9271 series) or some models Ralink, have open-source drivers already included in the Kali repositories. In these cases, manual compilation is not required, and the entire process boils down to installing a single package. This is the most secure and stable method.
To find the right package, you can search for keywords related to the chip manufacturer. The package name often contains the word firmware or prefix firmware-The system will automatically detect the required firmware and install it in the correct directory.
- 📡 For Atheros devices, the package is often used
firmware-atheros. - 📡 For Realtek chips it may be required
firmware-realtek. - 📡 Universal packages are sometimes simply called
linux-firmware.
After installing the package, you must reconnect the device or restart the computer. You can check functionality by running the command iwconfigIf a new interface appears in the list (for example, wlan0), which means the driver has been successfully activated and is ready to work.
⚠️ Note: Automatic installation does not work for all adapters. If the interface does not appear after installing the package, there is no ready-made solution for your specific model in the repositories, and manual compilation will be required.
Manually compiling drivers from source code
When ready-made packages are unavailable, manual assembly is the only option. This process requires downloading the driver source code, usually from GitHub or the manufacturer's official website. This most often applies to chip-based adapters. Realtek (eg RTL8812AU, RTL8821CU), which are popular among security professionals.
The compilation process is standard for most drivers. First, clone the code repository, then navigate to the created directory. Inside, you'll often find a file called install.sh or instructions README, but the classic method involves using the make and make install commands.
git clone https://github.com/repository_address/driver.gitCD driver
sudo make
sudo make install
sudo modprobe module_name
The key here is the team modprobe, which forces the newly compiled module to be loaded into the kernel. If the module fails to load, check the output of the command. dmesg for module signature errors (Signing key), which is often found in Secure Boot.
Problem with Secure Boot
If you have Secure Boot enabled in your BIOS, signed kernel modules may be blocked. In this case, either disable Secure Boot or sign the module with your own MOK key, which requires additional steps in the MOK Management menu during boot.
A successful compilation guarantees that the driver is adapted specifically to your kernel version. However, if you perform a kernel upgrade, you may need to repeat the process unless you used the DKMS mechanism for automatic recompilation.
Compatibility table of popular chipsets
To simplify your search, below is a table of the most common chipsets and their corresponding actions. This reference information will help you navigate the sea of available drivers.
| Chipset | Monitor Mode support | Injection Support | Recommended method |
|---|---|---|---|
| Atheros AR9271 | Yes (natively) | Yes | firmware-atheros package |
| Realtek RTL8812AU | Yes | Yes | Compiling from GitHub (aircrack-ng) |
| MediaTek MT7921 | Partially | No | Linux kernel 5.16+ |
| Ralink RT3070 | Yes | Yes | firmware-ralink package |
Availability of support modes Monitor Mode And Packet Injection This is critical for pentesting. Regular office adapters can often only connect to access points, but cannot intercept other people's traffic or inject packets.
When choosing hardware for Kali Linux, always check the latest compatibility lists. Manufacturers can change the internal components of adapters while keeping the same model number, which can result in the installation of an incompatible driver.
Diagnostics and problem solving
Even after a successful installation, connection or stability issues may still occur. A common cause is a conflict with network managers. In Kali Linux, this may work by default. NetworkManager, which attempts to automatically manage the interface, interfering with the work of specialized tools.
For diagnostics, use the utility airmon-ng checkIt will show processes that may be interfering with the Wi-Fi adapter and offer to terminate them. It's also worth checking whether the adapter is blocked programmatically. rfkill listIf the status is "blocked: yes", unblock it with the command rfkill unblock wifi.
- 🔍 Check kernel logs:
dmesg | grep firmwarewill show microcode loading errors. - 🔍 Make sure the interface is up:
sudo ip link set wlan0 up. - 🔍 Check permissions: running tools requires root or sudo privileges.
If the adapter constantly disconnects, this may indicate a power shortage, especially for high-power models with external antennas. Using a USB hub with an external power supply often resolves the issue.
⚠️ Note: Command interfaces and package names may change with the release of new versions of the distribution. If a command doesn't work, please refer to the official documentation or man pages.
Frequently Asked Questions (FAQ)
Why is my Wi-Fi adapter not visible in Kali Linux?
Most likely, the driver is missing or the device is not compatible. Check the output. lsusbIf the device isn't even there, the problem may be with the physical port or the adapter itself. If the device is visible but there's no wlan0 interface, you need a driver.
Can I use my laptop's built-in Wi-Fi for auditing?
Integrated cards often use Intel or Broadcom chips, which have limited support for injection mode. For full functionality, it's better to use an external USB adapter with an Atheros or Realtek chip.
Do I need to reinstall the driver after updating the kernel?
If you used DKMS during installation, the driver will be rebuilt automatically. If you compile manually without DKMS, you will have to repeat the installation procedure after each major system update.
Where can I download the driver if I don't have internet access on Kali?
Use another computer to download the driver archive (for example, from GitHub). Transfer the file to Kali via a USB drive. You can also try using your Android smartphone as a USB modem for temporary network access.