
Windows Server 2003 Service Pack 2, build 3790ĭumpcap 1.8.4 (SVN Rev 46250 from /trunk-1.8) Here's the list of metadata information extracted from MachineB.pcapng by :

, which will display a list of the metadata that was found in the uploaded fileĪs well as convert the capture file to the old libpcap format (without metadata). The easiest way to extract this extra metadata is to upload the capture file to However, what is not shown in this summary view is that MachineB.pcapng additionally containsĬached name resolution information for two machines. Here's the information provided when displaying a Summary in Wireshark on Some of these metadata types can be displayed in Wireshark by clicking “Statistics > Summary”. User comments on individual frames (a.k.a.Cached name resolution entries (mappings from IPv4 or IPv6 addresses to host names).Capture filter used when sniffing packets.Description of interface from where packets are captured.Name of interface from where packets are captured.Software used to create the capture file (application name and version).Operating system of the sniffer machine.Well, the spec allows features such as MAC address of capturing interface as well as interface speed (in bps) to be stored.īut the most commonly used metadata types are: So what types of metadata can a PcapNG file contain?

The remaining 80% is focused on various types of metadata. In fact only about 20% of the PcapNG file specification concerns storage of captured frames, The new PCAP-NG format, however, additionally includes the ability to store meta-data in the capture files. PCAP) is designed to only store captured network frames. In this blog post we explain what type of meta-data that can be found in PcapNG files, and how to extract it.

We revealed the identity of the anonymous capture file uploader by analyzing metadata available in the PCAP-NG file format.
