Ask Your Question
0

Not able to capture bridge connection. The capture session could not be initiated on interface

asked 2020-12-27 06:40:50 +0000

turtle166 gravatar image

updated 2020-12-27 06:42:03 +0000

Hi,

I'm trying to capture incoming and outgoing IP addresses from a PS4 (for a game glitch) however wireshark doesn't seem to be able to capture any of the traffic. I get the following error when I try to capture the bridge connection:

error I have ran it as administrator btw

I have the following interfaces:

interfaces

The only one of them that has traffic and I can monitor is the loopback one but that seems to only be for the current PC and not have any PS4 traffic.

Here is the bridge connection I have setup:

bridge

Any way to see outgoing and incoming IP addresses for the PS4? Thank you!!

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-12-27 19:23:58 +0000

Guy Harris gravatar image

"Failed to set hardware filter to promiscuous mode" sounds as if it means that the device doesn't support promiscuous mode.

Try capturing using the Capture > Options menu item and unchecking the promiscuous mode check box for the interface before starting the capture.

edit flag offensive delete link more

Comments

"Failed to set hardware filter to promiscuous mode" sounds as if it means that the device doesn't support promiscuous mode.

It could mean that, but, in this case, it probably means that 1) the Windows 11 driver 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.)

Guy Harris gravatar imageGuy Harris ( 2023-04-21 06:08:27 +0000 )edit

And the next 4.0.x release of Wireshark won't report the bit about sufficient permissions, because that should only be reported for a true permissions problem, which this isn't.

Guy Harris gravatar imageGuy Harris ( 2023-04-21 06:10:20 +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: 2020-12-27 06:40:50 +0000

Seen: 5,586 times

Last updated: Dec 27 '20