Here are some links that appear to be related to trying to resolve this exact issue. If the cameras are plugged directly into the computer you are running Wireshark on make sure TCP Chiminey is off. If the cameras are connected to a switch you can configure a mirrored port (mirror the port the camera is plugged into to a port you plug a machine doing the wireshark capture into). If the cameras are connected to a hub you can plug a laptop into the hub and capture in promiscuous mode. This is a screenshot from my network interface settings (the marked driver 'Teledyne DALSA Sapera GigE Vision Filter Driver' is the relevant one). Screenshot of Adapter Configuration (in German, sorry): Capture Driver: WinPCap v4.1.3 (packet.dll version 4.).Question: Is there any way to prioritize WinPCap, so that it handles the packets before the filter driver? I would like to avoid the need for capturing using additional hardware and prefer a software-only solution to this. The software which comes with the cameras needs the filter driver to work (there is no plain UDP-Socket fallback) and I would like to analyze it's traffic.
The protocol is simple UDP, but for performance reasons (high packet throughput causing CPU load) the manufacturer uses a filter driver that prevents those packets from showing up while capturing with WinPCap/Wireshark. I've got some GigabitEthernet Vision cameras, which use Ethernet to communicate.
0 kommentar(er)
