Changes between Version 1 and Version 2 of SupportedTraceFormats

Timestamp:

02/27/07 10:47:27 (15 years ago)

Author:

spa1

Comment:

--

SupportedTraceFormats

@@ -2 +2 @@
 Libtrace supports the following trace capture and storage formats:
 
-== Live Capture ==
+=== Live Capture ===
  * Endace DAG cards
  * pcap interfaces
@@ -8 +8 @@
  * WAG cards (internal WAND project)
 
-== Trace Formats ==
+=== Trace Formats ===
  * pcap traces
  * ERF (Extensible Record Format) traces
@@ -14 +14 @@
  * WTF (WAG Trace Format) traces
 
+== Format URIs ==
+Libtrace input and output sources are specified using URIs which describe both the format and location of the trace, interface or device in question.
+Below is a definitive list of URIs for all the trace formats supported by libtrace.
+
+ '''Live pcap interface'''::
+  pcap:<interface>
+ '''pcap trace file'''::
+  pcapfile:<filename>
+ '''Live DAG capture'''::
+  dag:<DAG device location e.g. /dev/dag0>
+ '''ERF trace file'''::
+  erf:<filename>
+ '''Native Linux interface'''::
+  int:<interface>
+ '''Legacy ATM'''::
+  legacyatm:<filename>
+ '''Legacy Ethernet'''::
+  legacyeth:<filename>
+ '''Legacy Packet over Sonet'''::
+  legacypos:<filename>
+ '''Live WAG capture'''::
+  wag:<WAG device location e.g. /dev/wag>
+ '''WTF trace file'''::
+  wtf:<filename>
+ 
+URI's that include a filename usually accept '-' to represent stdin, e.g. erf:- will read ERF records from stdin.