Wireless Network Issues

Category: Network Troubleshooting
Type: Network Tools & Commands
Generated on: 2025-07-11 01:38:53
For: Network Engineering, Administration & Technical Interviews

This cheatsheet provides a comprehensive guide to diagnosing and resolving wireless network issues using various network tools and commands. It covers practical usage, troubleshooting scenarios, and security considerations for network administrators and engineers.

1. Tool Overview

Tool	Description	When to Use
`iwconfig`	Displays and configures wireless network interfaces on Linux. Deprecated in favor of `iw` but still useful for quick status checks.	Checking wireless interface status, ESSID, channel, power, and encryption details.
`iw`	Newer replacement for iwconfig; displays and configures wireless network interfaces on Linux. More feature-rich and supports modern wireless standards.	Checking wireless interface status, scanning for networks, setting channel, power, and encryption details. Preferred for modern Linux systems.
`ifconfig`	(Deprecated) Displays and configures network interfaces (including wireless) on Linux. Mostly replaced by `ip`.	Checking IP address, netmask, MAC address, and interface status. Useful for verifying basic network connectivity.
`ip`	Modern replacement for `ifconfig` on Linux; displays and configures network interfaces (including wireless).	Checking IP address, netmask, MAC address, interface status, routing tables, and neighbor discovery. Preferred for modern Linux systems.
`ping`	Tests network connectivity by sending ICMP echo requests.	Verifying basic network reachability, latency, and packet loss.
`traceroute`	Traces the route packets take to a destination, showing each hop along the way.	Identifying network bottlenecks, routing issues, and where connectivity problems might be occurring.
`tcpdump`	Captures network traffic, allowing you to analyze packets and identify network problems.	Diagnosing protocol-specific issues, identifying malicious traffic, and analyzing network performance.
`Wireshark`	GUI-based packet analyzer, providing a more user-friendly interface for `tcpdump`.	Analyzing network traffic in detail, identifying protocol errors, and troubleshooting application-level problems.
`netsh wlan`	Windows command-line tool for managing wireless networks.	Checking wireless network status, scanning for networks, connecting to networks, and managing wireless profiles.
`Get-NetAdapter` + `Get-NetIPConfiguration`	PowerShell cmdlets for network interface information on Windows.	Scripting and automation of network configuration tasks. Modern alternative to `ipconfig` and `netsh` for many tasks.
`airport`	macOS command-line tool for wireless network diagnostics (primarily for monitoring). Hidden and may require Xcode command-line tools.	Scanning for networks, monitoring signal strength, and debugging wireless connectivity issues.
`networksetup`	macOS command-line tool for managing network interfaces (including wireless).	Configuring network settings, such as IP addresses, DNS servers, and network services.
`airmon-ng`	Part of the Aircrack-ng suite. Used for enabling monitor mode on wireless interfaces.	Capturing raw 802.11 frames for security auditing and packet analysis. Requires specialized hardware and knowledge.
`airodump-ng`	Part of the Aircrack-ng suite. Captures 802.11 frames and displays information about nearby access points and clients.	Identifying nearby wireless networks, monitoring client activity, and detecting rogue access points. Requires specialized hardware and knowledge.
`kismet`	Wireless network detector, sniffer, and intrusion detection system. More comprehensive than `airodump-ng`.	Network discovery, intrusion detection, and security auditing. Requires specialized hardware and knowledge.

2. Basic Syntax

iwconfig (Linux - Deprecated)
Terminal window
```
iwconfig [interface] [parameter] [value]
```

iw (Linux)

iw [dev <interface>] [command] [options]

ifconfig (Linux - Deprecated)

ifconfig [interface] [address] [netmask] [options]

ip (Linux)
Terminal window
```
ip [OPTIONS] OBJECT {COMMAND | help}
```
- OBJECT can be link, addr, route, etc.
ping
Terminal window
```
ping [options] <destination>
```
traceroute
Terminal window
```
traceroute [options] <destination>
```
tcpdump
Terminal window
```
tcpdump [options] [filter]
```
netsh wlan (Windows)
Terminal window
```
netsh wlan [command] [options]
```

airport (macOS)

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport [options] <interface>

networksetup (macOS)
Terminal window
```
networksetup [options] <command>
```

airmon-ng

airmon-ng [start|stop] <interface> [channel]

airodump-ng
Terminal window
```
airodump-ng [options] <interface>
```

3. Practical Examples

Linux (using iw and ip):

Check wireless interface status:

iw dev wlan0 link

Connected to 00:11:22:33:44:55 (on wlan0)
    SSID: MyWiFiNetwork
    freq: 2412 MHz
    signal: -50 dBm
    tx bitrate: 72.2 MBit/s MCS 7

Check IP address:

ip addr show wlan0

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether aa:bb:cc:dd:ee:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic wlan0
       valid_lft 85921sec preferred_lft 85921sec
    inet6 fe80::a8bb:ccff:fedd:eeff/64 scope link
       valid_lft forever preferred_lft forever

Scan for available wireless networks:
Terminal window
```
iw wlan0 scan
```
(Displays a list of available networks with their ESSIDs, signal strengths, and other details.)
Set wireless channel (Advanced - use with caution):
Terminal window
```
iw dev wlan0 set freq 2437
```
(Sets the wireless interface to channel 6 (2437 MHz) - be sure this is legal and doesn’t interfere with other devices)

Windows (using netsh wlan and PowerShell):
- Show available wireless networks:
  Terminal window
```
netsh wlan show networks
```
  (Displays a list of available networks with their ESSIDs and signal strengths.)
- Connect to a wireless network:
  Terminal window
```
netsh wlan connect name="MyWiFiNetwork" ssid="MyWiFiNetwork"
```
- Show wireless interface status (PowerShell):
  Terminal window
```
Get-NetAdapter -Name "Wi-Fi" | Get-NetIPConfiguration
```
  (Displays IP address, DNS servers, and other configuration details for the Wi-Fi adapter.)
macOS (using airport and networksetup):
- Scan for available wireless networks:
  Terminal window
```
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -s
```
  (Displays a list of available networks with their ESSIDs, BSSIDs, RSSI, channel, and security type.)
- Get Wi-Fi interface name:
  Terminal window
```
networksetup -listallhardwareports | grep Wi-Fi
```
  (Find the device name for your Wi-Fi adapter, e.g., Wi-Fi: en0)
- Set DNS servers (replace en0 with your Wi-Fi interface name):
  Terminal window
```
networksetup -setdnsservers "Wi-Fi" 8.8.8.8 8.8.4.4
```
Capturing Network Traffic (Linux/macOS):
- Capture all traffic on interface wlan0 and save to file capture.pcap:
  Terminal window
```
tcpdump -i wlan0 -w capture.pcap
```
- Capture only HTTP traffic on port 80:
  Terminal window
```
tcpdump -i wlan0 port 80 -w capture.pcap
```
- Analyze the capture file using Wireshark:
  Terminal window
```
wireshark capture.pcap
```
Wireless Security Auditing (Linux - Aircrack-ng Suite):
- Enable monitor mode on wlan0:
  Terminal window
```
airmon-ng start wlan0
```
  (This will create a new interface, typically wlan0mon)
- Capture 802.11 frames:
  Terminal window
```
airodump-ng wlan0mon
```
  (This will display a list of nearby access points and clients.)
- Capture 802.11 frames for a specific network (ESSID):
  Terminal window
```
airodump-ng -w capture --bssid <BSSID> --channel <channel> wlan0mon
```
  (Replace <BSSID> and <channel> with the actual values.)

4. Common Options

iwconfig:
- essid <ESSID>: Set the ESSID of the wireless network.
- key <KEY>: Set the WEP key. WEP is insecure and should not be used.
- channel <CHANNEL>: Set the channel.
- mode <MODE>: Set the operating mode (e.g., Managed, Ad-Hoc).
iw:
- dev <interface>: Specify the wireless interface.
- scan: Scan for available networks.
- connect <SSID>: Connect to a network.
- disconnect: Disconnect from the current network.
- freq <frequency>: Set the operating frequency in MHz.
- power <value>: Set the transmit power (mW).
ifconfig:
- up: Enable the interface.
- down: Disable the interface.
- netmask <NETMASK>: Set the subnet mask.
- broadcast <BROADCAST>: Set the broadcast address.
ip:
- addr show <interface>: Show IP address information for the interface.
- link set <interface> up/down: Enable/disable the interface.
- route: Show routing table.
- neighbor: Show ARP table (neighbor discovery).
ping:
- -c <count>: Send only count number of packets.
- -i <interval>: Wait interval seconds between sending each packet.
- -s <size>: Specify the packet size.
- -t (Windows): Ping continuously until stopped (Ctrl+C).
traceroute:
- -m <max_hops>: Set the maximum number of hops.
- -n: Do not resolve IP addresses to hostnames.
tcpdump:
- -i <interface>: Specify the interface to capture traffic on.
- -w <file>: Write the captured traffic to a file.
- -r <file>: Read packets from a file.
- -n: Do not resolve hostnames.
- -nn: Do not resolve hostnames or port numbers.
- -v, -vv, -vvv: Increase verbosity of output.
- port <port>: Filter traffic by port number.
- src <host>: Filter traffic by source host.
- dst <host>: Filter traffic by destination host.
- net <network>: Filter traffic by network.
- tcp, udp, icmp: Filter traffic by protocol.
netsh wlan:
- show profiles: List saved wireless profiles.
- show interfaces: Show wireless interface details.
- connect name=<profile_name>: Connect to a specific profile.
- disconnect: Disconnect from the current network.
- delete profile name=<profile_name>: Delete a saved profile.
airport:
- -s: Scan for available networks.
- -I: Get current wireless information (RSSI, channel, etc.).
networksetup:
- -listallhardwareports: List all network hardware ports.
- -setdnsservers <networkservice> <dns1> <dns2> ...: Set DNS servers for a network service.
- -getdnsservers <networkservice>: Get the DNS servers for a network service.
- -setmanual <networkservice> <ipaddress> <subnetmask> <router>: Set static IP address.
airmon-ng:
- start <interface>: Enable monitor mode on the interface.
- stop <interface>: Disable monitor mode on the interface.
airodump-ng:
- -w <file>: Write captured data to a file.
- --bssid <BSSID>: Filter by BSSID (MAC address of the access point).
- --channel <channel>: Filter by channel.

5. Advanced Usage

Linux (using iw and ip):

Monitor signal strength over time:

while true; do iw dev wlan0 link | grep signal; sleep 1; done

Configure a static IP address (using ip):

ip addr flush dev wlan0  # Remove existing IP address
ip addr add 192.168.1.150/24 dev wlan0
ip link set wlan0 up
ip route add default via 192.168.1.1
echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf

Windows (using netsh wlan and PowerShell):

Export a wireless profile to a file:

netsh wlan export profile name="MyWiFiNetwork" folder=.

Import a wireless profile from a file:

netsh wlan add profile filename="MyWiFiNetwork.xml"

Get the default gateway (PowerShell):

Get-NetRoute -InterfaceAlias "Wi-Fi" -AddressFamily IPv4 | Where-Object {$_.DestinationPrefix -eq "0.0.0.0/0"} | Select-Object -ExpandProperty NextHop

macOS (using airport and networksetup):
- Automate network configuration with scripts.
- Use airport in conjunction with other tools for real-time monitoring and analysis.
Combining tcpdump and Wireshark:
- Capture specific traffic using tcpdump filters, then analyze the captured data in detail using Wireshark’s GUI.

6. Troubleshooting Scenarios

Problem	Possible Causes	Troubleshooting Steps
No wireless connectivity	* Wireless adapter disabled. * Incorrect wireless password. * Wireless network not in range. * Driver issues. * Hardware failure. * AP is down. * DHCP server issues. * Interference.	1. Verify wireless adapter is enabled. 2. Check wireless password and try re-entering it. 3. Move closer to the wireless router/access point. 4. Update wireless adapter drivers. 5. Check for hardware issues (try a different device). 6. Ping the gateway IP address. 7. Restart the wireless router/access point. 8. Check DHCP server configuration. 9. Use a wireless analyzer to check for interference. 10. Check wireless channel. Some devices perform better on certain channels.
Slow wireless speeds	* Weak signal strength. * Interference. * Network congestion. * Outdated firmware on router/access point. * Incorrect wireless channel. * Old wireless standards (e.g., 802.11b/g). * QoS issues. * Router/AP overload.	1. Check signal strength and move closer to the wireless router/access point. 2. Check for interference from other devices (microwaves, Bluetooth devices, etc.). 3. Run a speed test to check network performance. 4. Update firmware on the wireless router/access point. 5. Change the wireless channel to a less congested one. 6. Upgrade to newer wireless standards (802.11ac/ax). 7. Check QoS settings on the router/access point. 8. Restart the router/access point. 9. Check the number of connected devices and consider upgrading the router if it’s overloaded. 10. Use a wireless analyzer to identify sources of interference.
Intermittent wireless connectivity	* Weak signal strength. * Interference. * Driver issues. * Power management settings on the wireless adapter. * Roaming issues (if using multiple access points). * Overlapping channels.	1. Check signal strength and move closer to the wireless router/access point. 2. Check for interference from other devices. 3. Update wireless adapter drivers. 4. Disable power management settings on the wireless adapter. 5. Check roaming settings and ensure seamless transitions between access points. 6. Ensure non-overlapping channels are used on adjacent access points (1, 6, 11 on 2.4GHz). 7. Examine the wireless router/AP logs for clues.
Cannot connect to a specific website	* DNS issues. * Firewall issues. * Website is down. * Routing problems. * Proxy server issues.	1. Ping the website’s IP address to check basic connectivity. 2. Try a different DNS server (e.g., 8.8.8.8). 3. Check firewall settings to ensure the website is not blocked. 4. Check if the website is down using a website monitoring service. 5. Use `traceroute` to identify routing problems. 6. Check proxy server settings. 7. Clear the browser cache and cookies.
Wireless network is not visible	* Wireless network is hidden (SSID broadcast disabled). * Wireless adapter is not scanning on the correct frequency. * Wireless network is too far away. * Wireless adapter is not compatible with the network’s security settings. * Wireless network is configured for 5GHz only.	1. Manually enter the wireless network’s SSID and password. 2. Ensure the wireless adapter is scanning on the correct frequency (2.4GHz or 5GHz). 3. Move closer to the wireless router/access point. 4. Ensure the wireless adapter is compatible with the network’s security settings (WPA2/WPA3). 5. Check if the wireless network is configured for 5GHz only and ensure the adapter supports it. 6. Verify SSID broadcast is enabled on the AP.
Rogue Access Point	* Unauthorized AP on the network. * Security risks. * Performance issues.	1. Scan for wireless networks using tools like `airodump-ng` or `kismet`. 2. Identify unknown APs. 3. Verify MAC address of the AP against known authorized devices. 4. Investigate the physical location of the AP. 5. Block the rogue AP from the network. 6. Improve wireless security measures.

7. Output Interpretation

iwconfig / iw: Pay attention to the ESSID (network name), signal strength (dBm), link quality, channel, and encryption settings. Low signal strength or incorrect encryption settings are common causes of problems.
ifconfig / ip: Verify that the interface has a valid IP address, netmask, and gateway. If the IP address is 169.254.x.x, it indicates a DHCP problem.
ping: High latency or packet loss indicates network congestion or a problem with the connection.
traceroute: Look for hops with high latency or timeouts, as these may indicate network bottlenecks.
tcpdump / Wireshark: Analyze the captured packets to identify protocol errors, retransmissions, or other network issues. Filter by IP address, port number, or protocol to narrow down the search.
netsh wlan: Check the output of show networks to see the signal strength and security type of available networks. Use show interfaces to check the status of the wireless adapter.
airport: RSSI values indicate signal strength (more negative is weaker). Check the channel and security type of available networks.
airmon-ng / airodump-ng: Interpret the output to identify nearby access points, clients, and their associated security settings. Pay attention to the power (PWR) and data (Data) columns.

8. Security Considerations

tcpdump: Be careful when capturing network traffic, as it may contain sensitive information such as passwords or credit card numbers. Use filters to capture only the necessary traffic. Store capture files securely.
airmon-ng / airodump-ng: These tools can be used for malicious purposes, such as unauthorized network access or denial-of-service attacks. Use them responsibly and only on networks that you own or have permission to test. It is illegal to use these tools to attack networks you do not own.
WEP: WEP encryption is highly insecure and should not be used. Use WPA2 or WPA3 instead.
Password Security: Use strong passwords for your wireless networks and change them regularly.
Access Control: Implement access control lists (ACLs) on your wireless router/access point to restrict access to specific devices.
Firmware Updates: Keep your wireless router/access point firmware up to date to patch security vulnerabilities.
Monitor for Rogue Access Points: Regularly scan for unauthorized access points on your network.

9. Platform Differences

Interface Names: Wireless interface names vary between operating systems. On Linux, they are typically wlan0, wlp3s0, etc. On Windows, they are usually named “Wi-Fi”. On macOS, they are typically en0, en1, etc.
Command Syntax: The syntax for network commands differs between operating systems. Use the appropriate commands for your platform.
Tool Availability: Some tools, such as iwconfig and iw, are only available on Linux. Windows uses netsh wlan and PowerShell cmdlets. macOS uses airport and networksetup.
Permissions: Many network commands require root/administrator privileges. Use sudo on Linux or run commands as an administrator on Windows.
PowerShell: On Windows, PowerShell is a powerful scripting environment. Use Get-Help <cmdlet> to learn more about specific cmdlets.
macOS airport: The airport utility is often hidden and may require the installation of Xcode command-line tools.

This cheatsheet provides a starting point for troubleshooting wireless network issues. Remember to consult the documentation for each tool for more detailed information. Always use caution when modifying network settings, and back up your configurations before making changes.