Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why doesn't wireshark detect my interface?

I just installed Wireshark, but when I click capture > interfaces, the dialog box appears, but it does not contain my network interface.

When click on capture > interfaces it appears as in the screenshot below. What can cause this?

no interfaces listed

like image 957
Ananda Subasinghe Avatar asked Nov 24 '11 10:11

Ananda Subasinghe


People also ask

How do I get an interface in Wireshark?

You can double-click on an interface in the welcome screen. You can select an interface in the welcome screen, then select Capture → Start or click the first toolbar button. You can get more detailed information about available interfaces using Section 4.5, “The “Capture Options” Dialog Box” (Capture → Options… ​).

Why is my Wireshark not capturing anything?

Installing Wireshark A problem you'll likely run into is that Wireshark may not display any packets after starting a capture using your existing 802.11 client card, especially if running in Windows. The issue is that many of the 802.11 cards don't support promiscuous mode.

How do I find my network interface?

From your computer, click Start, then Control Panel. Select Network and Internet Connections icon. Select the Network Connections icon. Under LAN or High-Speed Internet category, look for the name of the Ethernet card (Tip: words like Ethernet adapter, Ethernetlink, or LAN adapter may be contained in the card name).


1 Answers

This is usually caused by incorrectly setting up permissions related to running Wireshark correctly. While you can avoid this issue by running Wireshark with elevated privileges (e.g. with sudo), it should generally be avoided (see here, specifically here). This sometimes results from an incomplete or partially successful installation of Wireshark. Since you are running Ubuntu, this can be resolved by following the instructions given in this answer on the Wireshark Q&A site. In summary, after installing Wireshark, execute the following commands:

sudo dpkg-reconfigure wireshark-common  sudo usermod -a -G wireshark $USER 

Then log out and log back in (or reboot), and Wireshark should work correctly without needing additional privileges. Finally, if the problem is still not resolved, it may be that dumpcap was not correctly configured, or there is something else preventing it from operating correctly. In this case, you can set the setuid bit for dumpcap so that it always runs as root.

sudo chmod 4711 `which dumpcap` 

One some distros you might get the following error when you execute the command above:

chmod: missing operand after ‘4711’

Try 'chmod --help' for more information.

In this case try running

sudo chmod 4711 `sudo which dumpcap` 
like image 145
multipleinterfaces Avatar answered Sep 19 '22 19:09

multipleinterfaces