First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

Trouble with running Wireshark (Promiscuous mode)

  • retag add tags

Hi here i am again with a question. When i try to run WireShark on my Computer (windows 11). It wont work there will come a notification that sounds like this.

The capture session could not be initiated on capture device "\Device\NPF_{62432944-E257-41B7-A71A-D374A85E95DA}". (failed to set hardware filter to promiscuous mode: A device attached to the system is not functioning. (31))

please turn of promiscuous mode on your device.

Can someone please explain to me how i put this promiscuous mode off, and why this is happening? I used WireShark just fine on my dads computer, so i realy wonder why i got these issues.

Joep de Goeij's avatar
1
Joep de Goeij
asked 2023-11-03 17:08:21 +0000
Jaap's avatar
13.7k
Jaap
updated 2023-11-05 11:16:59 +0000
edit flag offensive 0 remove flag close merge delete

Comments

Please provide "Wireshark: Help -> About Wireshark -> Copy to Clipboard" information.

cmaynard's avatar cmaynard (2023-11-03 19:03:09 +0000) edit
add a comment see more comments

1 Answer

0

If you search for this you probably will run into suggestions to update npcap to 1.73 or above.

Jaap's avatar
13.7k
Jaap
answered 2023-11-03 20:51:30 +0000
edit flag offensive 0 remove flag delete link

Comments

1.74 contains the real fix (1.73 contains a change from somebody named "Guy Harris" that fixed a problem that said somebody thought might be the problem, and may have been a potential problem, but the main problem was somewhere else).

But 1.74 breaks time stamping; that's fixed in 1.75.

So I'd say "1.75 or above" now, and, given what's in the Npcap change log, I'd recommend 1.78 (not 1.76 or 1.77; those had memory-leak issues, at least one of which showed up in Wireshark's main screen with the interface traffic sparklines).

Guy Harris's avatar Guy Harris (2023-11-03 23:40:42 +0000) edit

:)

npcap is a bit of a moving target. Keep an eye on the release notes if problems are seen.

Jaap's avatar Jaap (2023-11-04 21:48:05 +0000) edit

And because of these npcap issues, the version installed by Wireshark tends to lag behind a bit until we find another npcap version that works well.

grahamb's avatar grahamb (2023-11-05 14:25:34 +0000) edit

Hi all

I want to thank you all for the great feedback!

Joep de Goeij's avatar Joep de Goeij (2023-11-06 19:32:58 +0000) edit
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer