osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Update the manual pages to reflect the addition of support for reading 

and writing Visual Networks traffic capture files.

svn path=/trunk/; revision=4329
This commit is contained in:
Guy Harris 2001-12-04 22:37:56 +00:00
parent bc225c2a87
commit e52dab213d
4 changed files with 36 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/editcap.pod
View File

@ -30,13 +30,13 @@ 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, and the
text output from the B<DBS Etherwatch> VMS utility. 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.
(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' software. 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>
@ -45,8 +45,9 @@ file; it can write the file in B<libpcap> format (standard B<libpcap>
format, a modified format used by some patched versions of B<libpcap>,
the format used by Red Hat Linux 6.1, or the format used by SuSE Linux
6.3), B<snoop> format, uncompressed B<Sniffer> format, Microsoft
B<Network Monitor> 1.x format, and the format used by Windows-based
versions of the B<Sniffer> software.
B<Network Monitor> 1.x format, the format used by Windows-based versions
of the B<Sniffer> software, and the format used by Visual Networks'
software.
A list of packet numbers can be specified on the command line; the
packets with those numbers will I<not> be written to the capture file,

13
doc/ethereal.pod.template
View File

@ -46,12 +46,13 @@ 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, and the text output from the B<DBS Etherwatch>
VMS utility. 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.
B<TCPIPtrace> utility, the text output from the B<DBS Etherwatch> VMS
utility, and traffic capture files from Visual Networks' software.
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

18
doc/mergecap.pod
View File

@ -27,12 +27,13 @@ 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, and the text output from the
B<DBS Etherwatch> VMS utility. 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.
from VMS's B<TCPIPtrace> utility, the text output from the B<DBS
Etherwatch> VMS utility, and traffic capture files from Visual Networks'
software. 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
@ -41,8 +42,9 @@ capture file; it can write the file in B<libpcap> format (standard
B<libpcap> format, a modified format used by some patched versions of
B<libpcap>, the format used by Red Hat Linux 6.1, or the format used by
SuSE Linux 6.3), B<snoop> format, uncompressed B<Sniffer> format,
Microsoft B<Network Monitor> 1.x format, and the format used by
Windows-based versions of the B<Sniffer> software.
Microsoft B<Network Monitor> 1.x format, the format used by
Windows-based versions of the B<Sniffer> software, and the format used
by Visual Networks' software.
Packets from the input files are merged in chronological order based on
each frame's timestamp, unless the B<-a> flag is specified. B<Mergecap>

18
doc/tethereal.pod.template
View File

@ -44,13 +44,13 @@ 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, and the text output from the
B<DBS Etherwatch> VMS utility. 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.
from VMS's B<TCPIPtrace> utility, the text output from the B<DBS
Etherwatch> VMS utility, and traffic capture files from Visual Networks'
software. 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
@ -72,8 +72,8 @@ to write the file; it can write the file in B<libpcap> format (standard
B<libpcap> format, a modified format used by some patched versions of
B<libpcap>, or the format used by Red Hat Linux 6.1), B<snoop> format,
uncompressed B<Sniffer> format, Microsoft B<Network Monitor> 1.x format,
and the format used by Windows-based versions of the B<Sniffer>
software.
the format used by Windows-based versions of the B<Sniffer>
software, and the format used by Visual Networks' software.
Read filters in B<Tethereal>, which allow you to select which packets
are to be decoded or written to a file, are very powerful; more fields