Wireshark can't find the interface when capturing packets

        Wireshark is a very important packet capture tool in learning computer networks. The packet capture tool can specify the interface of the network card, and accurately display the operation process and data format of the network protocol according to a specific network protocol. It is our understanding of computer networks. A must for the deep principles of the protocol.

        But recently, when I used Wireshark to capture http protocol packets, I found that no available network card was captured when I opened it, as shown below:

blob.png

        After viewing a series of information, I found out the solution:

1. When you start Wireshark for the first time, please start it as an administrator . (Keep in mind) If you start as a normal user, even if you start the npf service on the command line, the service name will be invalid;

blob.png

So make sure to start Wireshark as an administrator first;

blob.png

2. When Wireshark is turned on at this time, the available network card interface may still not be displayed (not absolute). In fact, the network card information captured by Wireshark is related to the npf service of Windows. It is not captured correctly because the npf service is not enabled, so you only need to open the command line as an administrator , and then enable the npf service.

tips: The command to start the service is

    net start npf

blob.png

3. At this time, check the situation of Wireshark again, and it shows that the network card is correctly captured.

blob.png



Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324896416&siteId=291194637