How to find the name of a Linux WiFi adapter: all methods

Enter ip link show or in short ip aIn the output, you will see a list of all network devices. Wireless adapters usually have names starting with the prefix wl, followed by letters and numbers, such as wlp2s0 or wlan0Wired card names often start with en, and virtual or local ones - with lo.

⚠️ Attention: If the command output ip link You don't see an interface with the prefix wl, this may mean that the driver for your WiFi adapter is not installed or the device is hardware locked.

Pay special attention to the interface state. If the state is indicated next to the name NO-CARRIER or DOWN, this means that the adapter is physically present in the system, but is not connected to the network or is turned off. To enable the interface, use the command ip link set dev [name] up, where instead [Name] You need to substitute the identifier of your adapter.

Advantages of the utility ip Its advantage lies in its speed and minimal resource consumption. It is available by default in almost all modern distributions, including Ubuntu, Debian, Fedora, and Arch Linux. Using this command is the de facto standard for system administrators.

Analyzing network connections with nmcli

If your system uses NetworkManager (which is standard for most desktop environments like GNOME, KDE, Cinnamon), then a command line utility will be an excellent diagnostic tool nmcliIt allows you to not only see the device's name but also understand its current role and connection status to specific networks.

To view a list of all devices and their types, enter the command nmcli device. In the column TYPE look for the meaning wifi. The corresponding name in the column DEVICE and will be the name of your wireless adapter. This method is especially useful because it immediately filters out virtual interfaces and tunnels, showing only the physical hardware.

Moreover, nmcli allows you to see if the device is connected to any network. If the status is connected, then the adapter is active and working correctly. If the status disconnected, the device is ready to work, but not connected. Status unmanaged indicates that NetworkManager ignores this interface and it must be managed manually or through other tools.

Usage nmcli Provides the advantage of clear, human-readable output. You immediately see not only the technical name of the interface, but also its logical state within the system's network policy. This helps you quickly diagnose connection issues when the driver is loaded but the network is down.

Checking hardware using lspci and lsusb

When standard network utilities don't produce the expected results, you need to go down a level and check whether the system itself sees the physical device. To do this, use the following commands: lspci for internal cards (PCI/PCIe) and lsusb For external USB adapters. These tools query the bus directly, bypassing the operating system's network stack.

For internal cards, run the command lspci | grep -i network or lspci | grep -i wirelessThe output will show the chipset model, for example, Intel Corporation Wireless 8265 or Realtek Semiconductor Co., Ltd.. Although the interface name is not always displayed here (for example, wlp3s0), you confirm the hardware availability. Knowing the chipset model makes it much easier to find the appropriate driver.

If you are using a USB WiFi adapter, the command lsusb will become your best friend. It will list all connected USB devices. Find the line containing the words Wireless, 802.11 or the adapter's brand name. This will confirm that the USB port is working properly and the device is being detected at a low level.

It is important to note that the absence of the device in lspci or lsusb If physically present, this could indicate a power issue, a faulty port, or a BIOS/UEFI setting where the port may be disabled. In such cases, software-based network configuration methods will be useless until the hardware or firmware issue is resolved.

Using the iw utility for wireless devices

A specialized tool for working with wireless networks in Linux is the package iw. Unlike the universal one ip, utility iw tailored specifically to IEEE 802.11 standards. Team iw dev displays a list of all wireless interfaces that are currently available to the system and have loaded drivers.

Executing a command iw dev will show the data structure where the first element will be the interface name (for example, wlp1s0). Next come parameters like index, type (usually managed) and MAC address. If your WiFi card is not shown here, but is visible in ip link, it may not have the firmware loaded on it or it may be locked.

⚠️ Attention: Utility iw Shows only wireless interfaces. If you're looking for an Ethernet network interface, this command won't return anything. It also doesn't work with virtual interfaces created for bridges or tunnels.

Additionally, iw allows you to get extended information about the adapter's capabilities by running iw listThe output often begins with the interface name and supported frequencies. This is useful for checking whether your adapter supports the 5 GHz band or only 2.4 GHz, which directly impacts connection speed.

Finding interface names through system logs and files

In Linux, all hardware and kernel event information is recorded in logs. If graphical utilities are silent and commands don't produce results, it's worth checking the kernel log. dmesg outputs a kernel message buffer that records the hardware detection process during system boot.

Use keyword filtering: dmesg | grep -i wifi or dmesg | grep -i firmwareIn the logs, you will find lines where the driver reports that the interface is registered. For example, the line wlp2s0: renamed from wlan0 will indicate that the interface is being renamed by udev. This is a common situation when predictable interface names are enabled.

You can also access the file system /sys. Directory /sys/class/net/ contains symbolic links to all network interfaces. A simple listing of the contents of this folder is done with the command ls /sys/class/net/ will give you a list of all names. This is the "ultimate truth," since this is the representation the kernel itself sees.

Log analysis is especially important when debugging driver issues. If dmesg If there are errors related to firmware or device registration, you'll understand why the interface doesn't appear in the default list. Often, the solution lies in installing a package. linux-firmware or a specific proprietary driver.

Table of names and commands for different distributions

While the basic principles of networking in Linux are the same, different distributions may use different default tools or have specific settings. Below is a summary table to help you navigate the various options depending on your system.

Understanding the differences helps you find the right configuration files faster. For example, in Ubuntu, static IP settings are often stored in netplan YAML files, whereas in older Debian systems, this might be a file /etc/network/interfacesThe adapter name in these files should match what you learned earlier.

Frequently Asked Questions (FAQ)