Changes between Version 1 and Version 2 of SupportedTraceFormats


Ignore:
Timestamp:
02/27/07 10:47:27 (15 years ago)
Author:
spa1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SupportedTraceFormats

    v1 v2  
    22Libtrace supports the following trace capture and storage formats:
    33
    4 == Live Capture ==
     4=== Live Capture ===
    55 * Endace DAG cards
    66 * pcap interfaces
     
    88 * WAG cards (internal WAND project)
    99
    10 == Trace Formats ==
     10=== Trace Formats ===
    1111 * pcap traces
    1212 * ERF (Extensible Record Format) traces
     
    1414 * WTF (WAG Trace Format) traces
    1515
     16== Format URIs ==
     17Libtrace input and output sources are specified using URIs which describe both the format and location of the trace, interface or device in question.
     18Below is a definitive list of URIs for all the trace formats supported by libtrace.
     19
     20 '''Live pcap interface'''::
     21  pcap:<interface>
     22 '''pcap trace file'''::
     23  pcapfile:<filename>
     24 '''Live DAG capture'''::
     25  dag:<DAG device location e.g. /dev/dag0>
     26 '''ERF trace file'''::
     27  erf:<filename>
     28 '''Native Linux interface'''::
     29  int:<interface>
     30 '''Legacy ATM'''::
     31  legacyatm:<filename>
     32 '''Legacy Ethernet'''::
     33  legacyeth:<filename>
     34 '''Legacy Packet over Sonet'''::
     35  legacypos:<filename>
     36 '''Live WAG capture'''::
     37  wag:<WAG device location e.g. /dev/wag>
     38 '''WTF trace file'''::
     39  wtf:<filename>
     40 
     41URI's that include a filename usually accept '-' to represent stdin, e.g. erf:- will read ERF records from stdin.