


Winshark works on ETW sessions, this is why you can select an ETW session in place of Network interface at the start of capture. It implements a backend for libpcap to capture ETW events. Winshark takes place in the first and last parts. libpcap ( wpcap.dll) which is in charge of interfacing between dumpcap.exe and the Operating System.dumpcap.exe which is in charge of capturing packets.Wireshark.exe which is in charge of parsing and dissecting protocols.Wireshark is split in three parts (yes, him too): The real underlying consumer is libpcap, ( wpcap.dll for Windows) which is used by dumpcap.exe which is the process in charge of packet capture. Well-known consumers are:Īnd now Winshark!!! Winshark is a simple ETW consumer. ConsumerĪ consumer is a simple program that will read logs from a session. You can see here some interesting session use by the event logger to capture logs from Application and System sessions and from Sysmon. Select DLT_USER under Protocols and Edit the encapsulations table:ĮventLog-Microsoft-Windows-Sysmon-Operational Trace Running To do that you have to open Preferences tab under the Edit panel. We issued a pull request to have a dedicated DLT value it is still pending. This is because you have not yet a true value from libpcap for our new Data Link. Capture NamedPipe through NpEtw file system filter driverĬurrently, you have to ask Wireshark to interpret the DLT_USER 147 as ETW.

