28 releases

0.14.0 May 13, 2022
0.13.3 Mar 24, 2022
0.13.0 Sep 13, 2021
0.11.1 Apr 23, 2021
0.4.0 Mar 19, 2019

#735 in Parser implementations

Download history 1332/week @ 2022-11-28 1272/week @ 2022-12-05 1463/week @ 2022-12-12 1043/week @ 2022-12-19 564/week @ 2022-12-26 1083/week @ 2023-01-02 1487/week @ 2023-01-09 1387/week @ 2023-01-16 1448/week @ 2023-01-23 1443/week @ 2023-01-30 1515/week @ 2023-02-06 1040/week @ 2023-02-13 1452/week @ 2023-02-20 1379/week @ 2023-02-27 3133/week @ 2023-03-06 4993/week @ 2023-03-13

11,011 downloads per month
Used in 9 crates (8 directly)



License: MIT Apache License 2.0 Crates.io Version docs.rs Github CI Minimum rustc version

PCAP and PCAPNG parsers

This crate contains several parsers for PCAP and PCAPNG files.

Compared to other similar projects, it is designed to offer a complete support of the many possible formats (legacy pcap, pcapng, little or big-endian, etc.) and features (pcapng files with multiple sections, interfaces, and endianness) while using only safe code and without copying data (zero-copy).

The code is available on Github and is part of the Rusticata project.

The pcap format(s)

The PCAP format (files usually ending with .pcap extension) is rather trivial. The PCAPNG format (usually .pcapng extension) is much more complex: it can be composed of multiple sections, each with multiple interfaces, having different capture lengths, time precision and even endianness!

These formats are more containers than data formats: packets contain data, formatted according to its interface linktype. There are many possible linktypes, defined in the linktypes registry. Support for parsing some of them is provided using the data feature (disabled by default).

This crate provides an abstraction over these different formats.

Parsing a file

pcap-parser provides several ways of parsing pcap data. Choosing the right one is mostly driven by resources: if the input file is small, the parse_pcap and parse_pcapng functions can be used directly.

Fine-grained functions are also available, to parse specifically some block types for example. They are listed in the pcap and pcapng modules.

If the input is larger and cannot fit into memory, then streaming parsers are available. They work by iterating on blocks, and so do not require to map the entire input. They cannot seek to a specific block, however.

Note: due to PCAPNG limitations, it is not possible to directly seek in a file to get a packet and handle it: the caller has to iterate though the file and store (at least) the interface descriptions for the current section, in order of appearance.

Example: streaming parsers

The following code shows how to parse a file in the pcap-ng format, using a PcapNGReader streaming parser. This reader provides a convenient abstraction over the file format, and takes care of the endianness.

use pcap_parser::*;
use pcap_parser::traits::PcapReaderIterator;
use std::fs::File;

let file = File::open(path).unwrap();
let mut num_blocks = 0;
let mut reader = PcapNGReader::new(65536, file).expect("PcapNGReader");
loop {
    match reader.next() {
        Ok((offset, _block)) => {
            println!("got new block");
            num_blocks += 1;
        Err(PcapError::Eof) => break,
        Err(PcapError::Incomplete) => {
        Err(e) => panic!("error while reading: {:?}", e),
println!("num_blocks: {}", num_blocks);

See PcapNGReader for a complete example, including handling of linktype and accessing packet data.

See also the pcapng module for more details about the new capture file format.

For legacy pcap files, use similar code with the LegacyPcapReader streaming parser.

See pcap-analyzer, in particular the libpcap-tools and pcap-info modules for more examples.

Example: generic streaming parsing

To create a pcap reader for input in either PCAP or PCAPNG format, use the create_reader function.


Support for serialization (i.e. generating binary data) is available by enabling the serialize feature. Most structures gain the to_vec() method (provided by the ToVec trait).

Note: support is still experimental, though working. API may change in the future.




Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


~18K SLoC