Wireshark

Why does Wireshark say no interfaces found

Wireshark is a very famous, open-source network capturing and analyzing tool. While using Wireshark, we may face many common issues. One of the common issues is “No Interfaces are listed in Wireshark”. Let’s understand the issue and find a solution in Linux OS.If you do not know Wireshark basic, then check Wireshark Basic first, then come back here.

No Interfaces are listed in Wireshark:

Let’s see this issue and try to solve it.

Step1:

First of all, we need to see how many interfaces are there in our Linux PC.

We can use the command “ifconfig” to see a list of up interfaces in our Linux pc. So open terminal (Short cut Alt+Ctrl+t) and run command “ifconfig

Outputs:

It should list down all up interfaces. Here is the screenshot for the “ifconfig” output

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_1.png

Here we can see three interfaces, including loopback interface “lo”.

If we want to see all interfaces in our system, including down interfaces, then use the command “ifconfig -a

Step2:

Now launch Wireshark from the command line.

“wireshark”

Screenshot:

Output:

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_2.png

Now we do not see the interfaces that we have seen from the previous output of the “ifconfig” command. On the right side, we can see “All interfaces shown” is selected.

Then what is the issue? Why Wireshark not able to detect required interfaces?

Let’s see.

Step3:

Close Wireshark and come back to the terminal. Here we can see the user is a normal user [Example: “rian”], but we need to launch Wireshark in superuser mode; otherwise, Wireshark is allowed to access the system interface list. Let’s try it out.

su” and enter the root password.

Output:

Now we can see the prompt as “[email protected]”. This means we are in root. Let’s try to launch Wireshark again from the terminal.

“wireshark”

Output:

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_3.png

All interfaces are listed down here on the Wireshark home page. Required interfaces are marked with a blue circle. These are the same interfaces that we have seen in the “ifconfig” command output.

In Linux, running Wireshark in sudo or superuser mode solves the problem.

We have seen in superuse mode. Let’s try if doing “sudo” works or not.

Command sequences:

1. Close Wireshark and enter “exit” to come out from the root.

2. Type the command “sudo wireshark” and enter the password for user “rian”. No need of a root password.

Here is the screenshot for the above steps 1 and 2.

Here is the home screen of Wireshark

All interfaces are listed down here.

Capturing Test:

Note: “enp1s0” is an Ethernet interface, and “wlp2s0” is a Wi-Fi interface.

As we see, interfaces are listed down, so let’s try to capture in one interface to see if it’s working or not.

See the below screenshot and double-click on the first interface.

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_4.png

As soon as we double click on the “enp1s0” interface, it starts capturing. Here is the screenshot for live capturing on interface “enp1s0”

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_5.png

We can try on capturing other interfaces also to see if it’s working.

Now double click on “wlp2s0” to start capturing. Here is the screenshot for live capturing.

E:\fiverr\Work\Linuxhint_mail74838\Article_Task\c_c++_wireshark_15\bam\pic\inter_6.png

Conclusion

In this article, we have learned how to solve the problem when Wireshark cannot detect or list down all interfaces from the Linux system. And there are two ways we can resolve this; either launch Wireshark in superuser mode or using sudo.

About the author

Bamdeb Ghosh

Bamdeb Ghosh

Bamdeb Ghosh is having hands-on experience in Wireless networking domain.He's an expert in Wireshark capture analysis on Wireless or Wired Networking along with knowledge of Android, Bluetooth, Linux commands and python. Follow his site: wifisharks.com