And there are two ways we can resolve this either launch Wireshark in superuser mode or using sudo. In this article, we have learned how to solve the problem when Wireshark cannot detect or list down all interfaces from the Linux system. Here is the screenshot for live capturing. Now double click on “wlp2s0” to start capturing. We can try on capturing other interfaces also to see if it’s working. Here is the screenshot for live capturing on interface “enp1s0” See the below screenshot and double-click on the first interface.Īs soon as we double click on the “enp1s0” interface, it starts capturing. Note: “enp1s0” is an Ethernet interface, and “wlp2s0” is a Wi-Fi interface.Īs we see, interfaces are listed down, so let’s try to capture in one interface to see if it’s working or not.

Help information available from Wireshark. To see what they are, simply enter the command wireshark -h and the help information shown in Help information available from Wireshark (or something similar) should be printed. Wireshark supports a large number of command line parameters. Here is the screenshot for the above steps 1 and 2.Īll interfaces are listed down here. In this section we will look at starting it from the command line. Type the command “sudo wireshark” and enter the password for user “rian”. Close Wireshark and enter “ exit” to come out from the root.Ģ. In Linux, running Wireshark in sudo or superuser mode solves the problem. These are the same interfaces that we have seen in the “ ifconfig” command output. Required interfaces are marked with a blue circle. All interfaces are listed down here on the Wireshark home page.

Launch wireshark commandline