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 | |
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')
-rw-r--r-- | doc/editcap.pod | 31 | ||||
-rw-r--r-- | doc/ethereal.pod.template | 32 | ||||
-rw-r--r-- | doc/mergecap.pod | 33 | ||||
-rw-r--r-- | doc/tethereal.pod.template | 32 |
4 files changed, 67 insertions, 61 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> diff --git a/doc/ethereal.pod.template b/doc/ethereal.pod.template index dc26b8df73..d9ef37dd6b 100644 --- a/doc/ethereal.pod.template +++ b/doc/ethereal.pod.template @@ -39,21 +39,23 @@ interactively browse packet data from a live network or from a previously saved capture file. B<Ethereal>'s native capture file format is B<libpcap> format, which is also the format used by B<tcpdump> and various other tools. In addition, B<Ethereal> 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<Ethereal> what type of file you are reading; -it will determine the file type by itself. B<Ethereal> is also capable -of reading any of these file formats if they are compressed using gzip. -B<Ethereal> recognizes this directly from the file; the '.gz' extension -is not required for this purpose. +from B<snoop> 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<Ethereal> what type of file you are reading; it will determine the +file type by itself. B<Ethereal> is also capable of reading any of +these file formats if they are compressed using gzip. B<Ethereal> +recognizes this directly from the file; the '.gz' extension is not +required for this purpose. Like other protocol analyzers, B<Ethereal>'s main window shows 3 views of a packet. It shows a summary line, briefly describing what the diff --git a/doc/mergecap.pod b/doc/mergecap.pod index c40434584e..57345dea12 100644 --- a/doc/mergecap.pod +++ b/doc/mergecap.pod @@ -20,22 +20,23 @@ B<Mergecap> is a program that combines multiple saved capture files into a single output file specified by the B<-w> argument. B<Mergecap> 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<Mergecap> 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<Mergecap> what type of file you are reading; -it will determine the file type by itself. B<Mergecap> is also capable -of reading any of these file formats if they are compressed using gzip. -B<Mergecap> recognizes this directly from the file; the '.gz' extension -is not required for this purpose. +addition, B<Mergecap> can read capture files from B<snoop> 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<Mergecap> what type of file +you are reading; it will determine the file type by itself. B<Mergecap> +is also capable of reading any of these file formats if they are +compressed using gzip. B<Mergecap> 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 both input capture files to the output file. The diff --git a/doc/tethereal.pod.template b/doc/tethereal.pod.template index 7237b191da..4e546625f5 100644 --- a/doc/tethereal.pod.template +++ b/doc/tethereal.pod.template @@ -37,21 +37,23 @@ capture file, either printing a decoded form of those packets to the standard output or writing the packets to a file. B<Tethereal>'s native capture file format is B<libpcap> format, which is also the format used by B<tcpdump> and various other tools. In addition, B<Tethereal> 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<Tethereal> what type of file -you are reading; it will determine the file type by itself. -B<Tethereal> is also capable of reading any of these file formats if -they are compressed using gzip. B<Tethereal> recognizes this directly -from the file; the '.gz' extension is not required for this purpose. +read capture files from B<snoop> 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<Tethereal> what type of file you are reading; +it will determine the file type by itself. B<Tethereal> is also capable +of reading any of these file formats if they are compressed using gzip. +B<Tethereal> recognizes this directly from the file; the '.gz' extension +is not required for this purpose. If the B<-w> flag is not specified, B<Tethereal> prints a decoded form of the packets it captures or reads; otherwise, it writes those packets |