https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101

--- Comment #4 from Guy Harris <g...@alum.mit.edu> ---
(In reply to LorenAmelang from comment #3)
> Still shows Bluetooth, also shows Local Area Connection 3, 12, 13, 14 with
> no addresses, and 6 with only (local) IPv6 addresses. Only the Wi-Fi ever
> shows data. Pretty much like WinPcap did. 
> 
> 
> As for what to do with this bug, maybe a popup when you first see an
> interface with no addresses, asking something like "do you want to hide
> these useless interfaces?" But no big deal really. 

Or how about having Npcap not report interfaces if it can't capture on them
(either by adding support for capturing on them, if it's possible for Npcap to
capture on them, or not listing them, if it's not possible for it to capture on
them)?

(WinPcap is no longer being maintained, so any fixing would have to be done to
Npcap.)

The only definition of "useless" that should be applied in the Wireshark or
Npcap code is "they can't be captured on"; otherwise, it's a user's personal
preference, which should be handled by un-checking the interfaces the user
doesn't find useful in the "Manage Interfaces" in Capture > Options.

Now, Npcap might be able to *sort* the interfaces better, so the more useful
ones show up at the top.

> And maybe "PacketGetStats error 995" should just be a dialog confirming no
> packets were seen, instead of an ominous error we are asked to report?

That's also an Npcap issue - either it should be fixed so that it gets capture
statistics or so that it doesn't list the device.

And you're asked to report it so that we can *get* it fixed.  It doesn't
necessarily mean "no packets were seen"; it could mean, for example, "The I/O
operation has been aborted because of either a thread exit or an application
request.", which would be a bug.

> Also, I already had an almost current npcap installed by nmap. Maybe
> Wireshark installs could offer to adopt it if it is already installed?

That might be a good idea; I don't know whether the Npcap people (who are also
the Nmap people...) should have the installer handle that?

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to