Managing wireless network interfaces from the command line is a fundamental skill for Linux system administrators and advanced users. The utility iw serves as the modern, versatile tool for this purpose, replacing older, fragmented commands and providing direct interaction with the Linux wireless extensions and nl80211 driver API. This guide explores the capabilities of iw , demonstrating how to perform essential tasks such as scanning, connecting, and monitoring wireless networks with precision and efficiency.
Understanding the iw Utility and Its Role
At its core, iw is a configuration utility for wireless LAN devices, built to work with the kernel's nl80211 subsystem. It provides a low-level interface to query and set various parameters of a wireless device, offering more detailed control than tools like iwconfig , which is now largely deprecated. The tool is typically included in the iw package and relies on the kernel's mac80211 driver to function, making it the standard for modern wireless management in Linux distributions. Its power comes from its ability to communicate directly with the hardware drivers, bypassing older abstraction layers for more accurate and flexible control.
Basic Syntax and Core Commands
The general structure of an iw command follows the pattern iw [dev interface ] command [options] . The dev argument is optional if the interface can be automatically determined, but it is good practice to specify it for clarity. Core commands are organized by their function, such as managing links, scanning for networks, or setting interface parameters. To see a list of all available commands for your specific version of the tool, running iw without arguments is the best starting point for discovery and verification.
Link Management and Interface Information
Before attempting to connect to a network, it is essential to understand the current state of your wireless interface. The link command displays detailed information about your current connection to an access point, including the MAC address of the router, the current signal strength, the negotiated bitrate, and various retry and timeout counters. This information is invaluable for troubleshooting connectivity issues, verifying that you are connected to the correct network, and monitoring the stability of the link in real time.
Scanning for Available Networks
To discover available wireless networks in your vicinity, the scan command is used. Executing iw dev wlan0 scan (replacing wlan0 with your interface name) triggers a active scan, where the interface sends probe requests and listens for beacons and probe responses from nearby access points. The output is a raw list of detected networks, showing their SSIDs, MAC addresses, signal levels, supported frequencies, and security protocols. For a more human-readable format, the results are typically piped to iwlist or parsed by higher-level tools like nmcli or wpa_supplicant , but iw provides the foundational data.
Connecting to Wireless Networks
While iw can manage the radio state and provide scan data, establishing an encrypted connection usually requires interaction with a supplicant like wpa_supplicant . The typical workflow involves first using iw to set the correct regulatory domain with iw reg set to ensure valid channel usage, then configuring wpa_supplicant with the SSID and password. The interface is then brought up, and the supplicant is attached to it. For ad-hoc or mesh networks, iw provides specific commands to set the appropriate type, allowing for direct peer-to-peer connections or participation in a mesh protocol without an access point.
