Net.show does not shows the LAN network

The command net show does not exist in Kali Linux or standard networking tools. If you are trying to view LAN networks, you likely meant iwlist scan, nmcli device wifi list, or airodump-ng. This article explains how to correctly scan for wireless networks and troubleshoot why your interface might appear down or missing.

Identifying the Correct Command

The confusion often stems from a misunderstanding of available utilities. There is no built-in system command named net.show in Debian-based distributions like Kali Linux. When users report that this command fails to show the LAN, they are usually attempting one of three specific tasks: listing active connections, scanning for nearby Wi-Fi access points, or checking network interface status. To diagnose the actual state of your network, you should first identify your network interfaces. Use the following command to list all network devices:

ip link show

This output will display interfaces such as eth0 (wired), wlan0 (wireless), or virtual interfaces like veth pairs if you are running Docker containers. If your wireless interface is not listed here, the driver may not be loaded, or the hardware is disabled via a physical switch. If you are looking for currently established connections rather than a raw scan of the airwaves, use:

nmcli connection show --active

Or for a more traditional Unix approach:

ifconfig -a

Understanding which tool matches your intent is the first step in resolving the issue. Using the wrong syntax for the intended tool will always result in an error or empty output.

Scanning for Wireless Networks

If your goal is to see available Wi-Fi networks on your local area network, you need a tool capable of putting your wireless card into monitor mode or using managed mode scanning. The method depends heavily on whether you are performing legitimate administrative tasks or security assessments. For standard desktop usage, NetworkManager provides the most reliable interface. Run:

nmcli device wifi list

This command queries the NetworkManager daemon for visible access points. It requires that your wireless interface is up and associated with the hardware driver properly. If this returns nothing, check the interface status with nmcli device status. You may find the device is set to "unmanaged" or "disconnected." For penetration testing contexts, where you need to capture packets or see hidden SSIDs, aircrack-ng suite tools are common. However, these require root privileges and specific interface states.

sudo airodump-ng wlan0

Note that airodump-ng will only show networks if the interface wlan0 is in monitor mode. If it is in managed mode, the command may hang or return no data. To switch modes, you typically need to kill existing processes using the interface and then bring it down before setting the mode. This process is complex and prone to breaking connectivity if done incorrectly on a primary system.

Alternative Scanning Tools

Another popular utility is iwlist, part of the wireless-tools package. While older, it remains functional for basic scans.

sudo iwlist wlan0 scan

Like airodump-ng, this requires elevated privileges. If you receive "Interface doesn't support scanning," it confirms the interface is either not a wireless card, the driver is missing, or the card is physically disabled.

Troubleshooting Interface Issues

When network tools fail to show expected results, the problem is rarely the software itself but rather the state of the hardware or the configuration management system. Below are the most common causes and their solutions. 1. Interface is Down Check if the interface flag includes UP. If it shows DOWN, bring it up:

sudo ip link set wlan0 up

2. Driver Missing or Incorrect Run lspci -k | grep -A 3 -i network to see if the kernel driver is bound to your wireless card. If it says "Kernel modules: iwlwifi" but no driver is loaded, you may need to load the module manually with modprobe iwlwifi. 3. NetworkManager Conflict Sometimes, manual configuration conflicts with NetworkManager. Ensure that your interface is not being ignored by the manager. Check the /etc/NetworkManager/NetworkManager.conf file to ensure managed=true is set for your wireless interface. For deeper insights into connectivity issues within virtual environments, you might find our guide on Can't Connect to VM Remotely: Troubleshooting Guide helpful, as VM network bridging often mimics these local interface issues.

Verifying Configuration

Once you have identified the correct command and ensured your interface is up, verify your configuration. Use iwconfig to check encryption settings and ESSID (network name).

iwconfig wlan0

If you are still unable to see networks, consider using a packet capture tool like Wireshark to see if beacon frames are arriving at the interface. Filtering by protocol can help isolate whether the issue is with the scanning tool or the underlying radio reception. For detailed instructions on analyzing traffic, see Kali Linux: Filter by Protocol in Wireshark's PCAPs. Remember that modern Kali Linux installations rely heavily on systemd-networkd or NetworkManager. Avoid mixing manual ifup/ifdown scripts with these managers unless necessary, as they can conflict and leave interfaces in a broken state. Always restart the network service after making configuration changes:

sudo systemctl restart NetworkManager

Frequently Asked Questions

Why does my wireless interface show as 'unmanaged'?

This usually means NetworkManager has excluded the interface from management, often due to a static configuration in /etc/network/interfaces. Remove any manual entries for the interface in that file and restart NetworkManager to regain control.

Can I use netstat to find Wi-Fi networks?

No, netstat displays active network connections and routing tables, not available wireless access points. It cannot scan the radio spectrum for SSIDs; you must use nmcli or iwlist for that purpose.

What should I do if airodump-ng shows no networks?

Ensure your interface is in monitor mode using airmon-ng start wlan0. Also, verify that no other processes are using the interface by running airmon-ng check kill before starting the monitor mode.

Does VirtualBox prevent Wi-Fi scanning?

Virtual machines generally cannot access physical Wi-Fi cards directly for scanning unless specifically passthrough-configured, which is rare and unstable. Host-only or NAT networking in VMs will not reflect the host's local Wi-Fi environment.

How do I fix 'Interface doesn't support scanning'?

This error indicates the driver does not support the requested operation or the interface is not a wireless device. Verify you are targeting the correct interface (e.g., wlan0 vs eth0) and that the correct wireless drivers are installed via apt install firmware-linux-nonfree.