Explanation of the 'missing interfaces' problem that goes beyond one sentence [closed]

asked 2019-10-03 16:00:20 +0000

updated 2019-10-03 16:21:29 +0000

grahamb gravatar image

Hello, I have been using wire shark with all operations normal for some time. In the beginning this issue was frustrating and I over came it. Now its crept back in and I have absolutely no clue what causes it or why it is happening

Some say driver compatibility Some say Admin privileges needed Some say 'maybe' try uninstalling and reinstating that 'could' work

I've checked and gone through all this and still there are interfaces that are missing the only interfaces shown are the loop back adapter and usbpcap

I'm starting to think Wireshark and Windows just don't want to exist together and that I should just use nmap.

I can see these interfaces in one line with nmap in cmd, This isn't a complicated issue so why is it so widespread?

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by lazy_developers
close date 2019-10-04 02:54:49.288210

Comments

The issue, the cause of which is unknown, persists because the few folks complaining about it refuse to work with the Wireshark devs, or take it up with npcap devs, to resolve the issue. As you know the issue isn't complicated maybe you can inform us how to fix it.

Fundamentally it's an npcap issue, Wireshark asks npcap to list all the interfaces and can only use what comes back.

If you wish to help, please run the npcap diagnostic report DiagReport.bat (found in the Program Files\npcap directory) from an elevated command prompt and then post the report results back here. It might be too big for a comment, in which case put it on a public file share and post a link to it back here.

grahamb gravatar imagegrahamb ( 2019-10-03 16:21:09 +0000 )edit

Thanks for that quick response! The file contains sensitive information like the BSSID for all my network adapters but that's the good news the list of interfaces is being detected successfully by npcap.

lazy_developers gravatar imagelazy_developers ( 2019-10-03 17:45:52 +0000 )edit

So you're unable to share it? It is not the list of interfaces detected by npcap, it's the list of interfaces configured by Windows on that machine.

grahamb gravatar imagegrahamb ( 2019-10-03 17:48:18 +0000 )edit

Ah I see my mistake. I assumed incorrectly. The file also showed that the existing paths for wincap and npcap failed. The programs are installed on my system but the paths have changed some reason. At this point, I uninstalled everything and reinstalled (including all the addons) and now everything is working. I ran the batch script again and the report still shows that the path for wincap has failed. Everything else however looks solid. Is there a way to update these path variables? That seems simpler than uninstalling everything.

lazy_developers gravatar imagelazy_developers ( 2019-10-03 18:59:40 +0000 )edit

Presumably you don't have WinPcap installed so that is expected to fail.

I suspect that the npcap devs put that in to check for systems that have left a WinPcap install behind.

As you now appear to have "fixed" your system we are no further to finding out what caused the issue in the first place.

grahamb gravatar imagegrahamb ( 2019-10-03 19:32:47 +0000 )edit