diff options
author | Guy Harris <guy@alum.mit.edu> | 2002-01-22 22:38:05 +0000 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2002-01-22 22:38:05 +0000 |
commit | be0b8a2d3106a9b659fef656e37359e2805db4f1 (patch) | |
tree | 2739fa8ddf713ac90caf4cf22a9ee53424a81b56 /doc/editcap.pod | |
parent | f953bd74158564f3c7d8ddff0145a16e36baa452 (diff) |
Fix up various product names and descriptions in the lists of file
formats we can read; include vendor names.
We should be able to read TokenPeek captures, as well as captures from
the Windows versions of EtherPeek.
Don't list the version numbers for EtherPeek and TokenPeek - those are
file format version numbers, not program version numbers.
svn path=/trunk/; revision=4599
Diffstat (limited to 'doc/editcap.pod')
-rw-r--r-- | doc/editcap.pod | 31 |
1 files changed, 16 insertions, 15 deletions
diff --git a/doc/editcap.pod b/doc/editcap.pod index b75703aadf..e2bb90102c 100644 --- a/doc/editcap.pod +++ b/doc/editcap.pod @@ -24,21 +24,22 @@ or all of the packets in that capture file to another capture file. B<Editcap> knows how to read B<libpcap> capture files, including those of B<tcpdump>, B<Ethereal>, and other tools that write captures in that format. In addition, B<Editcap> can read capture files from B<snoop> -(including B<Shomiti>) and B<atmsnoop>, B<LanAlyzer>, B<Sniffer> -(compressed or uncompressed), Microsoft B<Network Monitor>, AIX's -B<iptrace>, B<NetXray>, B<Sniffer Pro>, B<EtherPeek> versions 5, 6, and -7 for Macintosh, B<RADCOM>'s WAN/LAN analyzer, B<Lucent/Ascend> router -debug output, HP-UX's B<nettl>, the dump output from B<Toshiba's> ISDN -routers, the output from B<i4btrace> from the ISDN4BSD project, the -output in B<IPLog> format from the Cisco Secure Intrusion Detection -System, B<pppd logs> (pppdump format), the output from VMS's -B<TCPIPtrace> utility, the text output from the B<DBS Etherwatch> VMS -utility, and traffic capture files from Visual Networks' Visual UpTime. -There is no need to tell B<Editcap> what type of file you are reading; -it will determine the file type by itself. B<Editcap> is also capable -of reading any of these file formats if they are compressed using gzip. -B<Editcap> recognizes this directly from the file; the '.gz' extension -is not required for this purpose. +and B<atmsnoop>, Shomiti/Finisar B<Surveyor>, Novell B<LANalyzer>, +Network General/Network Associates DOS-based B<Sniffer> (compressed or +uncompressed), Microsoft B<Network Monitor>, AIX's B<iptrace>, Cinco +Networks B<NetXRay>, Network Associates Windows-based B<Sniffer>, AG +Group/WildPackets B<EtherPeek> and B<TokenPeek>, B<RADCOM>'s WAN/LAN +analyzer, B<Lucent/Ascend> router debug output, HP-UX's B<nettl>, the +dump output from B<Toshiba's> ISDN routers, the output from B<i4btrace> +from the ISDN4BSD project, the output in B<IPLog> format from the Cisco +Secure Intrusion Detection System, B<pppd logs> (pppdump format), the +output from VMS's B<TCPIPtrace> utility, the text output from the B<DBS +Etherwatch> VMS utility, and traffic capture files from Visual Networks' +Visual UpTime. There is no need to tell B<Editcap> what type of file +you are reading; it will determine the file type by itself. B<Editcap> +is also capable of reading any of these file formats if they are +compressed using gzip. B<Editcap> recognizes this directly from the +file; the '.gz' extension is not required for this purpose. By default, it writes the capture file in B<libpcap> format, and writes all of the packets in the capture file to the output file. The B<-F> |