Changes between Version 13 and Version 14 of SupportedTraceFormats


Ignore:
Timestamp:
09/20/10 11:41:17 (11 years ago)
Author:
salcock
Comment:

Tables are nice

Legend:

Unmodified
Added
Removed
Modified
  • SupportedTraceFormats

    v13 v14  
    1 == Supported Input Formats ==
    2 Libtrace supports reading from the following trace capture and storage formats:
    31
    4 === Live Capture ===
    5  * Endace DAG cards
    6  * pcap interfaces
    7  * Native Linux PF_PACKET interfaces
    8  * Native BSD BPF interfaces
    9  * Receiving packets over a network via the RT protocol
     2|| '''Format'''|| '''URI''' || '''Input''' || '''Output''' ||
     3|| Live pcap interface || pcapint:<interface> || Yes || Yes ||
     4|| pcap trace file || pcapfile:<filename> || Yes || Yes ||
     5|| ERF trace file || erf:<filename> || Yes || Yes ||
     6|| DAG device || dag:<device location> || Yes || Yes ||
     7|| Native Linux interface || int:<interface> || Yes || Yes ||
     8|| Native BSD interface || bpf:<interface> || Yes || No ||
     9|| TSH trace file || tsh:<filename> || Yes || No ||
     10|| FR+ trace file || fr+:<filename> || Yes || No ||
     11|| Legacy DAG ATM trace file || legacyatm:<filename> || Yes || No ||
     12|| Legacy DAG POS trace file || legacypos:<filename> || Yes || No ||
     13|| Legacy DAG Ethernet trace file   || legacyeth:<filename>   || Yes || No ||
     14|| Legacy DAG NZIX trace file || legacynzix:<filename> || Yes || No ||
     15|| ATM cell header trace file || atmhdr:<filename> || Yes || No ||
     16|| RT network protocol || rt:<host>:<port> || Yes || No ||
    1017
    11 === Trace Formats ===
    12  * pcap traces
    13  * ERF (Extensible Record Format) traces
    14  * Legacy DAG formats, such as those used in various Auckland tracesets
    15  * TSH and FR+ traces
     18Libtrace input and output sources are specified using URIs which describe both the format and location of the trace, interface or device in question.
     19To do so, simply append the location of the trace file, interface or device to the URI for the appropriate format as specified in the table above.
    1620
    17 == Supported Output Formats ==
    18 In addition, libtrace can write traces in the following formats:
     21For example, {{{pcapfile:sample.pcap.gz}}} describes the PCAP trace file called sample.pcap.gz. {{{dag:/dev/dag0}}} describes the DAG device present at /dev/dag0.
     22{{{int:eth0}}} is the URI for the Linux interface eth0.
    1923
    20  * pcap traces
    21  * ERF (Extensible Record Format) traces
    22  * pcap interfaces
    23  * Native Linux PF_PACKET interfaces
    24 
    25 == Format URIs ==
    26 Libtrace input and output sources are specified using URIs which describe both the format and location of the trace, interface or device in question.
    27 Below is a definitive list of URIs for all the trace formats supported by libtrace.
    28 
    29  '''Live pcap interface'''::
    30   {{{pcapint:}}}<interface>
    31  '''pcap trace file'''::
    32   {{{pcapfile:}}}<filename>
    33  '''Live DAG capture'''::
    34   {{{dag:}}}<DAG device location e.g. {{{/dev/dag0}}}>
    35  '''ERF trace file'''::
    36   {{{erf:}}}<filename>
    37  '''Native Linux interface'''::
    38   {{{int:}}}<interface>
    39  '''Native BSD BPF interface'''::
    40   {{{bpf:}}}<interface>
    41  '''RT protocol'''::
    42   {{{rt:}}}<host>{{{:}}}<port>
    43  '''Legacy ATM'''::
    44   {{{legacyatm:}}}<filename>
    45  '''Legacy Ethernet'''::
    46   {{{legacyeth:}}}<filename>
    47  '''Legacy Packet over Sonet'''::
    48   {{{legacypos:}}}<filename>
    49  '''Legacy NZIX'''::
    50   {{{legacynzix:}}}<filename>
    51  '''ATM Cell Header'''::
    52   {{{atmhdr:}}}<filename>
    53  '''TSH'''::
    54   {{{tsh:}}}<filename>
    55  '''FR+'''::
    56   {{{fr+:}}}<filename>
    57  
    58 URI's that include a filename usually accept '-' to represent stdin, e.g. {{{erf:-}}} will read ERF records from stdin.
     24URIs that include a filename usually accept '-' to represent stdin, e.g. {{{erf:-}}} will read ERF records from stdin.
    5925
    6026== Per format notes ==