Ask Your Question
0

Wireshark 4.0, Npcap 1.71, Windows 11 22H2 - getting an issue with promiscuous mode

asked 2022-10-06 14:33:30 +0000

JHSPerc gravatar image

updated 2024-01-16 00:45:58 +0000

Guy Harris gravatar image

Wireshark 4.0 and NPCAP 1.71 are not working for me - getting a disable promiscuous mode message. Tried disabling and packet capture still not functioning.

Wireshark 3.6.8 and NPCAP 1.60 work just fine with no errors.

Any thoughts?

edit retag flag offensive close merge delete

Comments

using latest windows 11, Wireshark stopped working this Jan 2024!. Tried rolling back, and also 1.78,1.75,1.74 doesn't help. using Win 11 Home, 10.0.22621 Build 22621 tried a brand new laptop, which happens to have the same win 11 build. no software whatsoever apart from this wireshark install, and same, it does not see USB serial (Silicon Labs CP210x) - which does show up in device manager, and i can use the port for serial transfer (even upto 1MBAUD) so the port and driver works fine. Just wireshark cannot see it.

FL-Rob gravatar imageFL-Rob ( 2024-01-15 20:10:05 +0000 )edit

As I noted in a reply to your comment on Npcap issue #628, this has nothing to do with the "failed to set hardware filter to promiscuous mode" issue. Please ask a new question, so we can respond to that.

Guy Harris gravatar imageGuy Harris ( 2024-01-16 00:44:55 +0000 )edit

i'm not able to raise a case, maybe because you dinged me for raising a valid issue that needs solving. maybe not exactly the fail above, but very similar (Win 11 2H23 update stops USB Serial devices). ether way,. it didn't need the -1 rating.

FL-Rob gravatar imageFL-Rob ( 2024-01-17 19:40:17 +0000 )edit

i'm not able to raise a case

Yes, you are - you filed this question, which was the right way to ask about this.

Guy Harris gravatar imageGuy Harris ( 2024-01-17 23:44:27 +0000 )edit

2 Answers

Sort by ยป oldest newest most voted
0

answered 2023-04-21 06:06:55 +0000

Guy Harris gravatar image

This is probably due to 1) the Windows 11 driver for your adapter using the Windows NetAdapterCx framework, 2) the NetAdapterCx framework not strictly following the Network Driver Interface Specification (NDIS) rules, and 3) the Npcap driver expecting all adapter drivers to strictly follow that specification and reporting an error if they don't.

This should be fixed in Npcap 1.74, which was released today (2023-04-20). (The Npcap driver no longer reports an error for that particular violation of the specification; the 1.60 driver also didn't check for that particular violation.)

edit flag offensive delete link more

Comments

Thank you - will test and confirm!

JHSPerc gravatar imageJHSPerc ( 2023-04-26 13:16:12 +0000 )edit
0

answered 2022-10-06 15:44:28 +0000

Chuckc gravatar image

There is a current Wireshark issue open (18414: Version 4.0: failed to to set hardware filter to promiscuous mode) that points to a npcap issue: 628: failed to set hardware filter to promiscuous mode with Windows 11 related to Windows drivers with Windows 11.

edit flag offensive delete link more

Comments

Thank you Chuck

JHSPerc gravatar imageJHSPerc ( 2022-10-06 17:58:59 +0000 )edit

And that Npcap issue appears to be fixed in Npcap 1.74, as per my comment.

Guy Harris gravatar imageGuy Harris ( 2023-04-22 02:50:48 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2022-10-06 14:33:30 +0000

Seen: 4,514 times

Last updated: Jan 16