I have a project to add support for two new block types to Wireshark. This doesn't seem to be documented anywhere and so I'm hoping that my notes here may help someone in the future.

This is work in progress and so the notes here are not complete. Also, I'm using this as a notepad and I may make mistakes which I'll correct later. If you notice mistakes, please feel free to update this page.

PCAP-NG Block Basics

A PCAP-NG file contains blocks of data. Each block contains:

Block Types are grouped as follows:

I have requested two Standard Block Types for my project - see Appendix C below. A recent code change (25583) prevents us from using anything other than Local Use Block during development.

Within the groups of Block Types, there is a further sub-grouping:


The objective of the project is to add Wireshark support for the display, filtering, etc. of text log data (machine data). The data is presented to Wireshark in a PCAP-NG file that contains two new block types:

The initial data being used is Apache HTTPD Common format log records, but I'm designing the solution so that any format of log data can be supported. I've started with the Apache HTTPD log data as it is a fairly simple format; space separated variables in fixed columns.

Test PCAP-NG Generation

Of course, the above raises the question, "What creates the PCAP-NG file with the new blocks?". At this time I'm using the Babel function that comes with TribeLab Workbench. The project that should follow this one will be to write a Wiretap reader for log files.

Babel produces the PCAP-NG file like this:

    log_file -----------------------------------> TRBs
    apache-common.xml -----+--------------------> TSDB

An XML file describes the format of the log file. The XML is used to generate the TSDB, and some elements of it are used to help parse the log records to form TRBs.

NB: Although I'm using Babel to generate the file, anyone can use any tool to generate a suitable file. There is nothing proprietary about the TSDB or TRB formats.

Other points

I'm trying to add this support completely through the plugin framework, and avoid having to make any changes to core Wireshark code. There is an API to add support for new block types via plugins, but I think this may the first project to use this functionality; there could be bugs and it may not be complete.

Even though the code I am writing has nothing to do with network packets, Wireshark still refers to the list of events in the top pane as the Packet List, and various structures that we need to use refer to all events as packets, most notably the wtap_pkthdr structure.

TSDB Handling

The TSDB defines the type and meaning of fields. Wireshark should not generate a "Packet List" entry for this block. Later; this type of block is referred to as an internal block. If you want to add support for a new internal block to your dissector, think of the TSDB as a template.

The TSDB defines each field through TLVs (type-length-value). The types map to native Wireshark field types with two important exceptions.

Field Type Encoding

The encoded integer values for the field types are not the same as the integer values used within Wireshark. This is because the Wireshark types are generated via an enumerated list. A change to the list could change the enumerated values. If we used these values within the TSDB, we would have compatibility problems. Wireshark field tyoe values start at 0. The TSDB field type values start at 1001.

The Wireshark field types values can be found in epan/ftypes/ftype.h. The mapping of TSDB values to Wireshark field values is in the array babeltowsft.

Special Cases

We need to deal with two special cases. A log record could contain many date-time values. We need to indicate which value should be used in the Wireshark packet list. This is done through the EVENT_DATETIME field type.

A log often mixes IPv4 and IPv6 addresses in the same column; both Apache HTTPD and Microsoft IIS do this. To accommodate this we have a TS_FT_IPvx field type.

Internal Block

This type of block carries information but doesn't generate an entry in the packet list; similar to the Interface Descriptor Block (IDB). This is the simplest kind of block to handle. There are two steps:

It looks something like this:

gboolean tsdb_read_block(FILE_T fh, guint32 block_data_len, gboolean c, wtapng_block_t *wtapng_block,
    int *err, gchar **err_info)
    /* Use i as a general purpose index */
    size_t i;

    /* Signal that this isn't a record block */
    wtapng_block->internal = TRUE;

    * Is the size of this block reasonable for a TSDB?
    if (block_data_len == 0 || block_data_len > wtapng_block->frame_buffer->allocated) {
        /* Not looking good. */
        *err = WTAP_ERR_BAD_FILE;
        *err_info = wmem_strdup_printf(wmem_file_scope(), "tsdb_read_block: block data length of %u is invalid",
        return FALSE;

    /* read block content */
    if (!wtap_read_bytes(fh, wtapng_block->frame_buffer->data, block_data_len, err, err_info)) {
        wmem_strdup_printf(wmem_file_scope(), "tsdb_read_block: failed to read TSDB");
        return FALSE;

    Do more stuff

    return TRUE;

    Do stuff
    register_pcapng_block_type_handler(BLOCK_TYPE_TSDB, tsdb_read_block, NULL);

See Appendix B for sample code.

Record Block


Within the Wireshark code, any block that generates an entry in the packet list is referred to as a record block although historically they have also been called packet block and some code comments still use this term.


A record block encapsulates payload in a "frame" format. The encapsulation is specified at three levels:

There are 16 available user values (WTAP_ENCAP_USER0 to WTAP_ENCAP_USER15) and I use WTAP_ENCAP_USER11 for the TRBs.

Timestamp Precision

The timestamp precision can be specified at three levels:

wtapng_block structure and substructures

In the tsdb_read_block(...) function above, I don't populate any of the fields in the wtapng_block structure. That's OK for a silent block but we need Wireshark to create a dissection chain (?) for the TRBs, i.e. a block that we wish to dissect.

What we need is for the content of the block to be treated as a new protocol, in the same way as the content of an EPB is becomes a Frame.

The wtapng_block structure and substructure fields I believe have to be completed by a block read function are:

The relevant code looks like this:

    /* Populate the wtapng_block */
    if (is_byte_swapped) {
        wtapng_block->packet_header->ts.secs = GUINT32_SWAP_LE_BE(tr_hdr->timestamp_high);
        wtapng_block->packet_header->ts.nsecs = GUINT32_SWAP_LE_BE(tr_hdr->timestamp_low);
        wtapng_block->packet_header->caplen = GUINT32_SWAP_LE_BE(block_data_len);
        wtapng_block->packet_header->len = GUINT32_SWAP_LE_BE(block_data_len);
    else {
        wtapng_block->packet_header->ts.secs = tr_hdr->timestamp_high;
        wtapng_block->packet_header->ts.nsecs = tr_hdr->timestamp_low;
        wtapng_block->packet_header->caplen = block_data_len;
        wtapng_block->packet_header->len = block_data_len;
    wtapng_block->internal = FALSE;
    wtapng_block->packet_header->interface_id = 0;
    wtapng_block->packet_header->drop_count = -1; /* invalid */
    wtapng_block->packet_header->caplen = block_data_len;
    wtapng_block->packet_header->len = block_data_len;
    wtapng_block->packet_header->pkt_encap = WTAP_ENCAP_USER11;
    wtapng_block->packet_header->presence_flags |= WTAP_HAS_TS;
    wtapng_block->packet_header->presence_flags |= WTAP_HAS_INTERFACE_ID;
    wtapng_block->packet_header->presence_flags |= WTAP_HAS_CAP_LEN;
    wtapng_block->packet_header->rec_type = REC_TYPE_PACKET;

See the complete code in Appendix B

Related information

Appendix A - XML Example

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
        <header headerline="false" skipheaderlines="0">
                <description>Descriptor file for Apache access log in common format</description>
                <generator>Babel 3.0</generator>
                <owner>Paul Offord</owner>
                <nativeformat>LogFormat "%h %l %u %t \"%r\" %>s %b" common</nativeformat>
                <example> - user01 [09/Jul/2012:08:25:35 +0100] "GET /Setup.php HTTP/1.1" 200 1824</example>
                <record type="1">
                        <eols enforce="true">
                                <criterium type="string" offset="*">*</criterium>
                                        <informat quoted="false">%i</informat>
                                        <blurb>This is the IP address of the client (remote host) which made the request to the server.</blurb>
                                        <type quoted="false">FT_IPvx</type>
                                        <informat quoted="false">%s</informat>
                                        <blurb>The identity of the client determined by a request to the identd server on the clients machine.</blurb>
                                        <type quoted="false">FT_STRINGZ</type>
                                        <informat quoted="false">%s</informat>
                                        <blurb>This is the userid of the person requesting the document as determined by HTTP authentication.</blurb>
                                        <type quoted="false">FT_STRINGZ</type>
                                        <informat quoted="false" start-bracket="[" end-bracket="]">[%d/%b/%Y:%H:%M:%S %z]</informat>
                                        <blurb>The time that the request was received.</blurb>
                                        <informat quoted="true">%s</informat>
                                        <blurb>The request line from the client is given in double quotes.</blurb>
                                        <informat quoted="false">%d</informat>
                                        <name>response code</name>
                                        <blurb>This is the status code that the server sends back to the client.</blurb>
                                        <informat quoted="false">%d</informat>
                                        <name>bytes returned</name>
                                        <blurb>This indicates the size of the object returned to the client, not including the response headers.</blurb>
                        <infofield>%4 - %5</infofield>

Appendix B - Sample Code

Note that this is still a very early cut - it's quite messy. There is also a bug with the timestamp handling.

Appendix C - Sample PCAP-NG File

This sample is a converted Apache HTTPD access log.


Appendix D - Request for PCAP-NG Block Types

-----Original Message-----
From: pcap-ng-format [] On Behalf Of
Sent: 22 January 2018 08:24
To: Paul Offord <>
Subject: Your message to pcap-ng-format awaits moderator approval

Your mail to 'pcap-ng-format' with the subject

    Request for Two PCAP-NG Block Types

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive notification of the moderator's decision.  If you would like to cancel this posting, please visit the following URL: