THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

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

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!!

turtle166's avatar
1
turtle166
asked 2020-12-27 06:40:50 +0000, updated 2020-12-27 06:42:03 +0000
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

"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.

Guy Harris's avatar
19.9k
Guy Harris
answered 2020-12-27 19:23:58 +0000
edit flag offensive 0 remove flag delete link

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's avatar Guy 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's avatar Guy Harris (2023-04-21 06:10:20 +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