I've found that encapsulation and file formats are different. We've mislead ourselves on what's happening with the file formats. The capinfos program from Wireshark reveals that Endace creates:

File type:           Endace ERF capture
File encapsulation:  Endace Record File

[download]

Whereas after being processed through mergecap (also from Wireshark), the file format has changed to

File type:           Wireshark/tcpdump/... - libpcap
File encapsulation:  Endace Record File

[download]

libpcap can read the latter, but not the former. So, the wireshark programs can read the native Endace file format, but libpcap can not. libpcap can however capture live from DAG's and the code seems to be there (pcap-dag.c).

The code from wireshark to read the Endace files is in erf.h, erf.c, but there are so many conditionals in how the specifics of the file can look, that this looks better to be a small C project if I want to avoid manually processing the files before processing with Perl. It would be great to convert this to a perl module, but I just need the data and don't have the time or C->Perl experience to be an open source hero!

Thanks for the feedback!

In reply to Re^2: Parsing ERF (pcap-like) format files by sblanton
in thread Parsing ERF (pcap-like) format files by sblanton

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.