| 16 | == Format URIs == |
| 17 | Libtrace input and output sources are specified using URIs which describe both the format and location of the trace, interface or device in question. |
| 18 | Below 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 | |
| 41 | URI's that include a filename usually accept '-' to represent stdin, e.g. erf:- will read ERF records from stdin. |