1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
|
2001-07-05 21:27:11 +00:00
|
|
|
|
ethereal - Interactively browse network traffic
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=head1 SYNOPSYS
|
|
|
|
|
|
|
|
|
|
B<ethereal>
|
2001-12-04 07:32:05 +00:00
|
|
|
|
S<[ B<-a> capture autostop condition ] ...>
|
2003-05-15 13:40:20 +00:00
|
|
|
|
S<[ B<-b> number of ring buffer files [:duration] ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-B> byte view height ]>
|
|
|
|
|
S<[ B<-c> count ]>
|
2001-01-10 09:39:24 +00:00
|
|
|
|
S<[ B<-f> capture filter expression ]>
|
1998-09-17 02:01:50 +00:00
|
|
|
|
S<[ B<-h> ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-i> interface ]>
|
1999-05-11 20:07:12 +00:00
|
|
|
|
S<[ B<-k> ]>
|
2001-05-01 00:41:46 +00:00
|
|
|
|
S<[ B<-l> ]>
|
2003-11-01 02:30:18 +00:00
|
|
|
|
S<[ B<-L> ]>
|
1998-09-17 02:01:50 +00:00
|
|
|
|
S<[ B<-m> font ]>
|
|
|
|
|
S<[ B<-n> ]>
|
2001-12-04 07:32:05 +00:00
|
|
|
|
S<[ B<-N> resolving flags ] >
|
2000-07-09 04:09:09 +00:00
|
|
|
|
S<[ B<-o> preference setting ] ...>
|
2000-09-15 05:32:49 +00:00
|
|
|
|
S<[ B<-p> ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-P> packet list height ]>
|
1999-05-11 20:07:12 +00:00
|
|
|
|
S<[ B<-Q> ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-r> infile ]>
|
2001-01-10 09:39:24 +00:00
|
|
|
|
S<[ B<-R> display filter expression ]>
|
1999-05-11 20:07:12 +00:00
|
|
|
|
S<[ B<-S> ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-s> snaplen ]>
|
|
|
|
|
S<[ B<-T> tree view height ]>
|
1998-09-27 22:12:47 +00:00
|
|
|
|
S<[ B<-t> time stamp format ]>
|
1998-09-17 02:01:50 +00:00
|
|
|
|
S<[ B<-v> ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
S<[ B<-w> savefile]>
|
2003-11-01 02:30:18 +00:00
|
|
|
|
S<[ B<-y> link type ]>
|
2002-09-05 06:46:38 +00:00
|
|
|
|
S<[ B<-z> statistics-string ]>
|
2001-11-24 08:46:13 +00:00
|
|
|
|
S<[ infile ]>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
1999-11-29 07:33:53 +00:00
|
|
|
|
B<Ethereal> is a GUI network protocol analyzer. It lets you
|
|
|
|
|
interactively browse packet data from a live network or from a
|
2001-12-05 20:01:03 +00:00
|
|
|
|
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
|
2003-10-31 00:43:21 +00:00
|
|
|
|
from B<snoop> and B<atmsnoop>, Shomiti/Finisar B<Surveyor> captures,
|
|
|
|
|
Novell B<LANalyzer> captures, Network General/Network Associates
|
|
|
|
|
DOS-based B<Sniffer> (compressed or uncompressed) captures, Microsoft
|
|
|
|
|
B<Network Monitor> captures, files from AIX's B<iptrace>, Cinco Networks
|
|
|
|
|
B<NetXRay> captures, captures from Network Associates Windows-based
|
|
|
|
|
B<Sniffer>, AG Group/WildPackets B<EtherPeek>/B<TokenPeek>/B<AiroPeek>
|
|
|
|
|
captures, captures from B<RADCOM>'s WAN/LAN analyzer, B<Lucent/Ascend>
|
|
|
|
|
router debug output, files from 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
|
2003-05-20 20:26:05 +00:00
|
|
|
|
B<TCPIPtrace>/B<TCPtrace>/B<UCX$TRACE> utilities, the text output from
|
|
|
|
|
the B<DBS Etherwatch> VMS utility, traffic capture files from Visual
|
2003-10-31 00:43:21 +00:00
|
|
|
|
Networks' Visual UpTime, the output from B<CoSine> L2 debug, the output
|
|
|
|
|
from Accellent's 5Views LAN agents, captures in Endace Measurement
|
2003-10-31 08:13:07 +00:00
|
|
|
|
Systems' ERF format, Linux Bluez Bluetooth stack B<hcidump -w> traces,
|
2003-10-31 00:43:21 +00:00
|
|
|
|
and captures from Network Instruments Observer version 9. 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.
|
1999-08-03 16:33:12 +00:00
|
|
|
|
|
1999-12-16 08:05:46 +00:00
|
|
|
|
Like other protocol analyzers, B<Ethereal>'s main window shows 3 views
|
|
|
|
|
of a packet. It shows a summary line, briefly describing what the
|
|
|
|
|
packet is. A protocol tree is shown, allowing you to drill down to
|
|
|
|
|
exact protocol or field that you interested in. Finally, a hex dump
|
1999-08-03 16:33:12 +00:00
|
|
|
|
shows you exactly what the packet looks like when it goes over the wire.
|
|
|
|
|
|
1999-10-30 06:42:10 +00:00
|
|
|
|
In addition, B<Ethereal> has some features that make it unique. It can
|
|
|
|
|
assemble all the packets in a TCP conversation and show you the ASCII
|
2000-08-09 06:38:53 +00:00
|
|
|
|
(or EBCDIC, or hex) data in that conversation. Display filters in
|
|
|
|
|
B<Ethereal> are very powerful; more fields are filterable in B<Ethereal>
|
|
|
|
|
than in other protocol analyzers, and the syntax you can use to create
|
|
|
|
|
your filters is richer. As B<Ethereal> progresses, expect more and more
|
|
|
|
|
protocol fields to be allowed in display filters.
|
1999-08-03 16:33:12 +00:00
|
|
|
|
|
1999-12-16 08:05:46 +00:00
|
|
|
|
Packet capturing is performed with the pcap library. The capture filter
|
|
|
|
|
syntax follows the rules of the pcap library. This syntax is different
|
|
|
|
|
from the display filter syntax.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-16 08:05:46 +00:00
|
|
|
|
Compressed file support uses (and therefore requires) the zlib library.
|
|
|
|
|
If the zlib library is not present, B<Ethereal> will compile, but will
|
|
|
|
|
be unable to read compressed files.
|
1999-09-22 01:38:00 +00:00
|
|
|
|
|
2001-11-24 08:46:13 +00:00
|
|
|
|
The pathname of a capture file to be read can be specified with the
|
|
|
|
|
B<-r> option or can be specified as a command-line argument.
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=head1 OPTIONS
|
|
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
2002-04-26 00:04:23 +00:00
|
|
|
|
Most users will want to start B<Ethereal> without options and configure
|
|
|
|
|
it from the menus instead. Those users may just skip this section.
|
|
|
|
|
|
2001-12-04 07:32:05 +00:00
|
|
|
|
=item -a
|
|
|
|
|
|
2002-04-26 00:04:23 +00:00
|
|
|
|
Specify a criterion that specifies when B<Ethereal> is to stop writing
|
2001-12-04 07:32:05 +00:00
|
|
|
|
to a capture file. The criterion is of the form I<test>B<:>I<value>,
|
|
|
|
|
where I<test> is one of:
|
|
|
|
|
|
|
|
|
|
=for man .RS
|
|
|
|
|
|
|
|
|
|
=for html <P><DL>
|
|
|
|
|
|
|
|
|
|
=item duration
|
|
|
|
|
|
|
|
|
|
Stop writing to a capture file after I<value> seconds have elapsed.
|
|
|
|
|
|
|
|
|
|
=item filesize
|
|
|
|
|
|
|
|
|
|
Stop writing to a capture file after it reaches a size of I<value>
|
|
|
|
|
kilobytes (where a kilobyte is 1000 bytes, not 1024 bytes).
|
|
|
|
|
|
|
|
|
|
=for man .RE
|
|
|
|
|
|
|
|
|
|
=for html </DL>
|
|
|
|
|
|
2001-12-04 09:56:10 +00:00
|
|
|
|
=item -b
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
If a maximum capture file size was specified, cause B<Ethereal> to run
|
2001-12-04 09:56:10 +00:00
|
|
|
|
in "ring buffer" mode, with the specified number of files. In "ring
|
2003-06-22 16:09:04 +00:00
|
|
|
|
buffer" mode, B<Ethereal> will write to several capture files.
|
|
|
|
|
Their name is based on the number of the file and on the creation date
|
|
|
|
|
and time.
|
2001-12-04 09:56:10 +00:00
|
|
|
|
|
|
|
|
|
When the first capture file fills up, B<Ethereal> will switch to writing
|
|
|
|
|
to the next file, until it fills up the last file, at which point it'll
|
2003-06-22 16:09:04 +00:00
|
|
|
|
discard the data in the first file (unless 0 is specified, in which case,
|
|
|
|
|
the number of files is unlimited) and start writing to that file and so on.
|
2001-12-04 09:56:10 +00:00
|
|
|
|
|
2003-05-15 13:40:20 +00:00
|
|
|
|
If the optional duration is specified, B<Ethereal> will switch also
|
|
|
|
|
to the next file when the specified number of seconds has elapsed even
|
|
|
|
|
if the current file is not completely fills up.
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -B
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the initial height of the byte view (bottom) pane.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item -c
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the default number of packets to read when capturing live
|
1999-07-20 03:54:53 +00:00
|
|
|
|
data.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-05-11 20:07:12 +00:00
|
|
|
|
=item -f
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the capture filter expression.
|
1999-05-11 20:07:12 +00:00
|
|
|
|
|
1998-09-17 02:01:50 +00:00
|
|
|
|
=item -h
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Print the version and options and exit.
|
1998-09-17 02:01:50 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -i
|
|
|
|
|
|
2002-12-29 22:40:10 +00:00
|
|
|
|
Set the name of the network interface or pipe to use for live packet
|
|
|
|
|
capture.
|
|
|
|
|
|
2002-11-03 17:38:27 +00:00
|
|
|
|
Network interface names should match one of the names listed in
|
2002-12-29 22:40:10 +00:00
|
|
|
|
"B<tethereal -D>". If you're using Unix, "B<netstat -i>" or "B<ifconfig
|
|
|
|
|
-a>" might also work to list interface names, although not all versions
|
|
|
|
|
of Unix support the B<-a> flag to B<ifconfig>.
|
|
|
|
|
|
|
|
|
|
Pipe names should be either the name of a FIFO (named pipe) or ``-'' to
|
|
|
|
|
read data from the standard input. Data read from pipes must be in
|
|
|
|
|
standard libpcap format.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-05-11 20:07:12 +00:00
|
|
|
|
=item -k
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Start the capture session immediately. If the B<-i> flag was
|
2000-01-15 06:05:21 +00:00
|
|
|
|
specified, the capture uses the specified interface. Otherwise,
|
2000-01-16 02:48:12 +00:00
|
|
|
|
B<Ethereal> searches the list of interfaces, choosing the first
|
|
|
|
|
non-loopback interface if there are any non-loopback interfaces, and
|
|
|
|
|
choosing the first loopback interface if there are no non-loopback
|
|
|
|
|
interfaces; if there are no interfaces, B<Ethereal> reports an error and
|
|
|
|
|
doesn't start the capture.
|
1999-05-11 20:07:12 +00:00
|
|
|
|
|
2001-05-01 00:41:46 +00:00
|
|
|
|
=item -l
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Turn on automatic scrolling if the packet display is being updated
|
2001-05-01 00:41:46 +00:00
|
|
|
|
automatically as packets arrive during a capture (as specified by the
|
|
|
|
|
B<-S> flag).
|
|
|
|
|
|
2003-11-01 02:30:18 +00:00
|
|
|
|
=item -L
|
|
|
|
|
|
|
|
|
|
List the data link types supported by the interface and exit.
|
|
|
|
|
|
1998-09-17 02:01:50 +00:00
|
|
|
|
=item -m
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the name of the font used by B<Ethereal> for most text.
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
|
|
|
|
B<Ethereal> will construct the name of the bold font used for the data
|
|
|
|
|
in the byte view pane that corresponds to the field selected in the
|
|
|
|
|
protocol tree pane from the name of the main text font.
|
1998-09-17 02:01:50 +00:00
|
|
|
|
|
|
|
|
|
=item -n
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Disable network object name resolution (such as hostname, TCP and UDP port
|
1998-09-17 02:01:50 +00:00
|
|
|
|
names).
|
|
|
|
|
|
2001-05-31 08:36:46 +00:00
|
|
|
|
=item -N
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Turn on name resolving for particular types of addresses and port
|
|
|
|
|
numbers, with name resolving for other types of addresses and port
|
|
|
|
|
numbers turned off; the argument is a string that may contain the
|
|
|
|
|
letters B<m> to enable MAC address resolution, B<n> to enable network
|
|
|
|
|
address resolution, and B<t> to enable transport-layer port number
|
|
|
|
|
resolution. This overrides B<-n> if both B<-N> and B<-n> are present.
|
2003-07-22 03:14:31 +00:00
|
|
|
|
The letter B<C> enables concurrent (asynchronous) DNS lookups.
|
2001-05-31 08:36:46 +00:00
|
|
|
|
|
2000-07-09 04:09:09 +00:00
|
|
|
|
=item -o
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set a preference value, overriding the default value and any value read
|
2000-07-09 04:09:09 +00:00
|
|
|
|
from a preference file. The argument to the flag is a string of the
|
|
|
|
|
form I<prefname>B<:>I<value>, where I<prefname> is the name of the
|
|
|
|
|
preference (which is the same name that would appear in the preference
|
|
|
|
|
file), and I<value> is the value to which it should be set.
|
|
|
|
|
|
2000-09-15 05:32:49 +00:00
|
|
|
|
=item -p
|
|
|
|
|
|
|
|
|
|
I<Don't> put the interface into promiscuous mode. Note that the
|
|
|
|
|
interface might be in promiscuous mode for some other reason; hence,
|
|
|
|
|
B<-p> cannot be used to ensure that the only traffic that is captured is
|
|
|
|
|
traffic sent to or from the machine on which B<Ethereal> is running,
|
|
|
|
|
broadcast traffic, and multicast traffic to addresses received by that
|
|
|
|
|
machine.
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -P
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the initial height of the packet list (top) pane.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-05-11 20:07:12 +00:00
|
|
|
|
=item -Q
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Cause B<Ethereal> to exit after the end of capture session (useful in
|
1999-07-20 03:54:53 +00:00
|
|
|
|
batch mode with B<-c> option for instance); this option requires the
|
|
|
|
|
B<-i> and B<-w> parameters.
|
1999-05-11 20:07:12 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -r
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Read packet data from I<infile>.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-08-08 01:29:24 +00:00
|
|
|
|
=item -R
|
|
|
|
|
|
2000-02-19 00:18:45 +00:00
|
|
|
|
When reading a capture file specified with the B<-r> flag, causes the
|
|
|
|
|
specified filter (which uses the syntax of display filters, rather than
|
|
|
|
|
that of capture filters) to be applied to all packets read from the
|
|
|
|
|
capture file; packets not matching the filter are discarded.
|
1999-08-08 01:29:24 +00:00
|
|
|
|
|
1999-05-11 20:07:12 +00:00
|
|
|
|
=item -S
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Perform the live packet capture in a separate process, and automatically
|
|
|
|
|
update the packet display as packets are seen.
|
1999-05-11 20:07:12 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -s
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the default snapshot length to use when capturing live data.
|
1999-07-20 03:54:53 +00:00
|
|
|
|
No more than I<snaplen> bytes of each network packet will be read into
|
|
|
|
|
memory, or saved to disk.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item -T
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the initial height of the tree view (middle) pane.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1998-09-27 22:12:47 +00:00
|
|
|
|
=item -t
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the format of the packet timestamp displayed in the packet list
|
2000-11-01 08:31:36 +00:00
|
|
|
|
window. The format can be one of 'r' (relative), 'a' (absolute), 'ad'
|
|
|
|
|
(absolute with date), or 'd' (delta). The relative time is the time
|
|
|
|
|
elapsed between the first packet and the current packet. The absolute
|
|
|
|
|
time is the actual time the packet was captured, with no date displayed;
|
|
|
|
|
the absolute date and time is the actual time and date the packet was
|
|
|
|
|
captured. The delta time is the time since the previous packet was
|
|
|
|
|
captured. The default is relative.
|
1998-09-27 22:12:47 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item -v
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Print the version and exit.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item -w
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the default capture file name.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2003-11-01 02:30:18 +00:00
|
|
|
|
=item -y
|
|
|
|
|
|
|
|
|
|
If a capture is started from the command line with B<-k>, set the data
|
|
|
|
|
link type to use while capturing packets. The values reported by B<-L>
|
|
|
|
|
are the values that can be used.
|
|
|
|
|
|
2002-09-05 06:46:38 +00:00
|
|
|
|
=item -z
|
|
|
|
|
|
|
|
|
|
Get B<Ethereal> to collect various types of statistics and display the result
|
|
|
|
|
in a window that updates in semi-real time.
|
|
|
|
|
Currently implemented statistics are:
|
|
|
|
|
|
2003-06-21 01:42:46 +00:00
|
|
|
|
B<-z> dcerpc,srt,I<uuid>,I<major>.I<minor>[,I<filter>]
|
2002-10-25 01:08:49 +00:00
|
|
|
|
|
2003-06-21 01:42:46 +00:00
|
|
|
|
Collect call/reply SRT (Service Response Time) data for DCERPC interface I<uuid>,
|
2002-10-25 01:08:49 +00:00
|
|
|
|
version I<major>.I<minor>.
|
2003-06-21 01:42:46 +00:00
|
|
|
|
Data collected is number of calls for each procedure, MinSRT, MaxSRT
|
|
|
|
|
and AvgSRT.
|
|
|
|
|
Example: use B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0> to collect data for CIFS SAMR Interface.
|
2002-10-25 01:08:49 +00:00
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
2003-06-21 01:42:46 +00:00
|
|
|
|
Example: use B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4> to collect SAMR
|
|
|
|
|
SRT statistics for a specific host.
|
2002-10-25 01:08:49 +00:00
|
|
|
|
|
2002-11-15 10:55:19 +00:00
|
|
|
|
B<-z> io,stat
|
|
|
|
|
|
|
|
|
|
Collect frame/bytes statistics for the capture in intervals of 1 seconds.
|
|
|
|
|
This option will open a window with up to 5 color-coded graphs where
|
|
|
|
|
number-of-frames-per-second or number-of-bytes-per-second statistics
|
|
|
|
|
can be calculated and displayed.
|
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
This graph window can also be opened from the Tools:Statistics:Traffic:IO-Stat
|
|
|
|
|
menu item.
|
|
|
|
|
|
|
|
|
|
|
2003-06-21 03:24:06 +00:00
|
|
|
|
B<-z> rpc,srt,I<program>,I<version>[,<filter>]
|
2002-09-05 06:46:38 +00:00
|
|
|
|
|
2003-06-21 03:24:06 +00:00
|
|
|
|
Collect call/reply SRT (Service Response Time) data for I<program>/I<version>. Data collected
|
|
|
|
|
is number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
|
|
|
|
|
Example: use B<-z rpc,srt,100003,3> to collect data for NFS v3. This
|
2002-09-05 06:46:38 +00:00
|
|
|
|
option can be used multiple times on the command line.
|
|
|
|
|
|
2002-09-27 11:07:16 +00:00
|
|
|
|
If the optional filter string is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
2003-06-21 03:24:06 +00:00
|
|
|
|
Example: use B<-z rpc,srt,100003,3,nfs.fh.hash==0x12345678> to collect NFS v3
|
|
|
|
|
SRT statistics for a specific file.
|
2002-09-27 11:07:16 +00:00
|
|
|
|
|
2002-09-06 10:13:17 +00:00
|
|
|
|
B<-z> rpc,programs
|
|
|
|
|
|
|
|
|
|
Collect call/reply RTT data for all known ONC-RPC programs/versions.
|
|
|
|
|
Data collected is number of calls for each protocol/version, MinRTT,
|
|
|
|
|
MaxRTT and AvgRTT.
|
|
|
|
|
|
2003-06-21 06:40:48 +00:00
|
|
|
|
B<-z> smb,srt[,I<filter>]
|
2003-01-22 00:40:36 +00:00
|
|
|
|
|
2003-06-21 06:40:48 +00:00
|
|
|
|
Collect call/reply SRT (Service Response Time) data for SMB. Data collected
|
|
|
|
|
is number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
|
|
|
|
|
Example: use B<-z smb,srt>.
|
2003-01-22 00:40:36 +00:00
|
|
|
|
|
|
|
|
|
The data will be presented as separate tables for all normal SMB commands,
|
|
|
|
|
all Transaction2 commands and all NT Transaction commands.
|
|
|
|
|
Only those commands that are seen in the capture will have its stats
|
|
|
|
|
displayed.
|
|
|
|
|
Only the first command in a xAndX command chain will be used in the
|
|
|
|
|
calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
|
|
|
|
|
only the SessionSetupAndX call will be used in the statistics.
|
|
|
|
|
This is a flaw that might be fixed in the future.
|
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
2003-06-21 06:40:48 +00:00
|
|
|
|
Example: use B<-z "smb,srt,ip.addr==1.2.3.4"> to only collect stats for
|
2003-01-22 00:40:36 +00:00
|
|
|
|
SMB packets echanged by the host at IP address 1.2.3.4 .
|
|
|
|
|
|
2003-06-25 11:15:34 +00:00
|
|
|
|
B<-z> fc,srt[,I<filter>]
|
|
|
|
|
|
|
|
|
|
Collect call/reply SRT (Service Response Time) data for FC. Data collected
|
|
|
|
|
is number of calls for each Fibre Channel command, MinSRT, MaxSRT and AvgSRT.
|
|
|
|
|
Example: use B<-z fc,srt>.
|
|
|
|
|
The Service Response Time is calculated as the time delta between the
|
|
|
|
|
First frame of the exchange and the Last frame of the exchange.
|
|
|
|
|
|
|
|
|
|
The data will be presented as separate tables for all normal FC commands,
|
|
|
|
|
Only those commands that are seen in the capture will have its stats
|
|
|
|
|
displayed.
|
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
|
|
|
|
Example: use B<-z "fc,srt,fc.id==01.02.03"> to only collect stats for
|
|
|
|
|
FC packets echanged by the host at FC address 01.02.03 .
|
|
|
|
|
|
2003-11-05 09:04:17 +00:00
|
|
|
|
B<-z> ldap,srt[,I<filter>]
|
|
|
|
|
|
|
|
|
|
Collect call/reply SRT (Service Response Time) data for LDAP. Data collected
|
|
|
|
|
is number of calls for each implemented LDAP command, MinSRT, MaxSRT and AvgSRT.
|
|
|
|
|
Example: use B<-z ldap,srt>.
|
|
|
|
|
The Service Response Time is calculated as the time delta between the
|
|
|
|
|
Request and the Response.
|
|
|
|
|
|
|
|
|
|
The data will be presented as separate tables for all implemented LDAP commands,
|
|
|
|
|
Only those commands that are seen in the capture will have its stats
|
|
|
|
|
displayed.
|
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
|
|
|
|
Example: use B<-z "ldap,srt,ip.addr==10.1.1.1"> to only collect stats for
|
|
|
|
|
LDAP packets echanged by the host at IP address 10.1.1.1 .
|
|
|
|
|
|
|
|
|
|
The only LDAP command that are currently implemented and the stats will be available for are:
|
|
|
|
|
BIND
|
|
|
|
|
SEARCH
|
|
|
|
|
MODIFY
|
|
|
|
|
ADD
|
|
|
|
|
DELETE
|
|
|
|
|
MODRDN
|
|
|
|
|
COMPARE
|
|
|
|
|
EXTENDED
|
|
|
|
|
|
|
|
|
|
|
2003-08-21 17:48:04 +00:00
|
|
|
|
B<-z> mgcp,srt[I<,filter>]
|
2003-04-27 21:52:24 +00:00
|
|
|
|
|
2003-08-21 17:48:04 +00:00
|
|
|
|
Collect requests/response SRT (Service Response Time) data for MGCP.
|
|
|
|
|
This is similar to B<-z smb,srt>). Data collected is number of calls
|
|
|
|
|
for each known MGCP Type, Minimum SRT, Maximum SRT and Average SRT.
|
|
|
|
|
Example: use B<-z mgcp,srt>.
|
2003-04-27 21:52:24 +00:00
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
2003-08-21 17:48:04 +00:00
|
|
|
|
Example: use B<-z "mgcp,srt,ip.addr==1.2.3.4"> to only collect stats for
|
2003-04-27 21:52:24 +00:00
|
|
|
|
MGCP packets exchanged by the host at IP address 1.2.3.4 .
|
|
|
|
|
|
2003-09-04 23:37:45 +00:00
|
|
|
|
B<-z> conv,I<type>[,I<filter>]
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2003-08-24 20:32:40 +00:00
|
|
|
|
Create a table that lists all conversations that could be seen in the
|
|
|
|
|
capture. I<type> specifies for which type of conversation we want to
|
|
|
|
|
generate the statistics; currently the supported ones are
|
|
|
|
|
|
2003-08-24 03:31:54 +00:00
|
|
|
|
"eth" Ethernet
|
2003-08-29 10:59:12 +00:00
|
|
|
|
"fc" Fibre Channel addresses
|
|
|
|
|
"fddi" FDDI addresses
|
2003-08-24 03:31:54 +00:00
|
|
|
|
"ip" IP addresses
|
2003-08-24 05:38:23 +00:00
|
|
|
|
"ipx" IPX addresses
|
2003-08-24 20:32:40 +00:00
|
|
|
|
"tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
|
2003-08-24 03:31:54 +00:00
|
|
|
|
"tr" TokenRing
|
2003-08-24 20:32:40 +00:00
|
|
|
|
"udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
|
|
|
|
If the optional filter string is specified, only those packets that match the
|
|
|
|
|
filter will be used in the calculations.
|
|
|
|
|
|
|
|
|
|
The table is presented with one line for each conversation and displays
|
2003-08-24 20:32:40 +00:00
|
|
|
|
number of frames/bytes in each direction as well as total number of
|
|
|
|
|
frames/bytes. By default, the table is sorted according to total number
|
|
|
|
|
of frames.
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
|
|
|
|
These tables can also be generated at runtime by selecting the appropriate
|
2003-09-04 23:37:45 +00:00
|
|
|
|
conversation type from the menu "Tools/Statistics/Conversation List/".
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2003-10-28 00:31:17 +00:00
|
|
|
|
B<-z> h225,counter[I<,filter>]
|
|
|
|
|
|
|
|
|
|
Count ITU-T H.225 messages and their reasons. In the first column you get a
|
|
|
|
|
list of H.225 messages and H.225 message reasons, which occur in the current
|
|
|
|
|
capture file. The number of occurences of each message or reason is displayed
|
|
|
|
|
in the second column.
|
|
|
|
|
|
|
|
|
|
Example: use B<-z h225,counter>.
|
|
|
|
|
|
|
|
|
|
This option can be used multiple times on the command line.
|
|
|
|
|
|
|
|
|
|
If the optional filterstring is provided, the stats will only be calculated
|
|
|
|
|
on those calls that match that filter.
|
|
|
|
|
Example: use B<-z "h225,counter,ip.addr==1.2.3.4"> to only collect stats for
|
|
|
|
|
H.225 packets exchanged by the host at IP address 1.2.3.4 .
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=back
|
|
|
|
|
|
|
|
|
|
=head1 INTERFACE
|
|
|
|
|
|
|
|
|
|
=head2 MENU ITEMS
|
|
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=item File:Open, File:Close, File:Reload
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-08-10 07:16:47 +00:00
|
|
|
|
Open, close, or reload a capture file. The I<File:Open> dialog box
|
|
|
|
|
allows a filter to be specified; when the capture file is read, the
|
|
|
|
|
filter is applied to all packets read from the file, and packets not
|
|
|
|
|
matching the filter are discarded.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
Allow the user to save either all of the current capture, or only the
packets that are currently being displayed from that capture.
Centralize the code to control whether "File:Save" and "File:Save As"
are enabled (and *always* have "File:Save As" enabled if you have a
capture; "File:Save" is enabled only if you have a live capture you've
not yet saved, although it does the same thing as "File:Save As").
Have the "save_file" member of a "capture_file" structure represent
*only* the file currently being *written* to by a capture, and, if there
is no capture currently in progress, have it be NULL; the name of the
file currently being *displayed" is in the "filename" member, and an
"is_tempfile" member indicates whether it's a temporary file for a live
capture or not.
Have "close_cap_file()" delete the current capture file if it's a
temporary capture file that hasn't been saved (in its entirety - saving
selected frames doesn't count). Do the same (if there *is* a current
capture file) when exiting.
The "Ready to load or capture" message is the only statusbar message in
the "main" context; "close_cap_file()" should never pop it, it should
only pop whatever message exists in the "file" context, and thus has no
need to take, as an argument, the context for the message it should pop.
Update the man page to reflect the new behavior of "File:Save" and
"File:Save As", and to reflect recent changes to "Display:Match Selected".
svn path=/trunk/; revision=1170
1999-11-30 20:50:15 +00:00
|
|
|
|
=item File:Save, File:Save As
|
|
|
|
|
|
|
|
|
|
Save the current capture, or the packets currently displayed from that
|
2000-08-23 19:40:12 +00:00
|
|
|
|
capture, to a file. Check boxes let you select whether to save all
|
|
|
|
|
packets, or just those that have passed the current display filter and/or
|
|
|
|
|
those that are currently marked, and an option menu lets you select (from
|
|
|
|
|
a list of file formats in which at particular capture, or the packets
|
|
|
|
|
currently displayed from that capture, can be saved), a file format in
|
|
|
|
|
which to save it.
|
Allow the user to save either all of the current capture, or only the
packets that are currently being displayed from that capture.
Centralize the code to control whether "File:Save" and "File:Save As"
are enabled (and *always* have "File:Save As" enabled if you have a
capture; "File:Save" is enabled only if you have a live capture you've
not yet saved, although it does the same thing as "File:Save As").
Have the "save_file" member of a "capture_file" structure represent
*only* the file currently being *written* to by a capture, and, if there
is no capture currently in progress, have it be NULL; the name of the
file currently being *displayed" is in the "filename" member, and an
"is_tempfile" member indicates whether it's a temporary file for a live
capture or not.
Have "close_cap_file()" delete the current capture file if it's a
temporary capture file that hasn't been saved (in its entirety - saving
selected frames doesn't count). Do the same (if there *is* a current
capture file) when exiting.
The "Ready to load or capture" message is the only statusbar message in
the "main" context; "close_cap_file()" should never pop it, it should
only pop whatever message exists in the "file" context, and thus has no
need to take, as an argument, the context for the message it should pop.
Update the man page to reflect the new behavior of "File:Save" and
"File:Save As", and to reflect recent changes to "Display:Match Selected".
svn path=/trunk/; revision=1170
1999-11-30 20:50:15 +00:00
|
|
|
|
|
1999-07-23 08:33:44 +00:00
|
|
|
|
=item File:Print
|
|
|
|
|
|
2003-09-10 22:33:31 +00:00
|
|
|
|
Print, for all the packets in the current capture, or for only the
|
|
|
|
|
marked packets in the current capture, either the summary line for the
|
|
|
|
|
packet or the protocol tree view of the packet; when printing the
|
|
|
|
|
protocol tree view, the hex dump of the packet can be printed as well.
|
|
|
|
|
Printing options can be set with the I<Edit:Preferences> menu item, or
|
|
|
|
|
in the dialog box popped up by this item.
|
1999-07-23 08:33:44 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item File:Print Packet
|
|
|
|
|
|
2000-01-06 07:32:44 +00:00
|
|
|
|
Print a fully-expanded protocol tree view of the currently-selected
|
|
|
|
|
packet. Printing options can be set with the I<Edit:Preferences> menu
|
|
|
|
|
item.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item File:Quit
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Exit the application.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-01-18 09:05:30 +00:00
|
|
|
|
=item Edit:Find Frame
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Search forward or backward, starting with the currently selected packet
|
2003-09-09 02:41:00 +00:00
|
|
|
|
(or the most recently selected packet, if no packet is selected). Search
|
|
|
|
|
criteria can be a display filter expression, a string of hexadecimal
|
|
|
|
|
digits, or a text string.
|
|
|
|
|
|
2003-09-10 22:33:31 +00:00
|
|
|
|
When searching for a text string, you can search the packet data, or you
|
|
|
|
|
can search the text in the Info column in the packet list pane or in the
|
|
|
|
|
protocol tree pane.
|
|
|
|
|
|
2003-09-09 02:41:00 +00:00
|
|
|
|
Hexadecimal digits can be separated by colons, periods, or dashes.
|
|
|
|
|
Text string searches can be ASCII or Unicode (or both), and may be
|
|
|
|
|
case insensitive.
|
2002-05-03 21:55:15 +00:00
|
|
|
|
|
|
|
|
|
=item Edit:Find Next
|
|
|
|
|
|
|
|
|
|
Search forward, starting with the currently selected packet
|
|
|
|
|
(or the most recently selected packet, if no packet is selected), for a
|
|
|
|
|
packet matching the filter from the previous search.
|
|
|
|
|
|
|
|
|
|
=item Edit:Find Previous
|
|
|
|
|
|
|
|
|
|
Search backward, starting with the currently selected packet (or the
|
|
|
|
|
most recently selected packet, if no packet is selected), for a packet
|
|
|
|
|
matching the filter from the previous search.
|
2000-01-18 09:05:30 +00:00
|
|
|
|
|
|
|
|
|
=item Edit:Go To Frame
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Go to a particular numbered packet.
|
2000-01-18 09:05:30 +00:00
|
|
|
|
|
2003-09-12 02:48:23 +00:00
|
|
|
|
=item Edit:Set Time Reference
|
|
|
|
|
|
|
|
|
|
Set (or unset if currently set) the selected packet as a Time Reference packet.
|
|
|
|
|
When a packet is set as a Time Reference packet, the timestamps in the packet
|
|
|
|
|
pane will be replaced with the string "*REF*".
|
|
|
|
|
The relative time timestamp in later packets will then be calculated relative
|
|
|
|
|
to the timestamp of this Time Reference frame and not the first frame in
|
|
|
|
|
the capture.
|
|
|
|
|
|
|
|
|
|
Packets that have been selected as Time Reference packets will always be
|
|
|
|
|
displayed in the packet pane. Display filters will not affect or hide these
|
|
|
|
|
packets.
|
|
|
|
|
|
|
|
|
|
|
2000-08-23 19:40:12 +00:00
|
|
|
|
=item Edit:Mark Frame
|
|
|
|
|
|
2002-05-03 21:38:20 +00:00
|
|
|
|
Mark (or unmark if currently marked) the selected packet. The field
|
|
|
|
|
"frame.marked" is set for frames that are marked, so that, for example,
|
|
|
|
|
a display filters can be used to display only marked frames, and so that
|
|
|
|
|
the L<Find Frame> menu item can be used to find the next or previous
|
|
|
|
|
marked frame.
|
2000-08-23 19:40:12 +00:00
|
|
|
|
|
|
|
|
|
=item Edit:Mark All Frames
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Mark all packets that are currently displayed.
|
2000-08-23 19:40:12 +00:00
|
|
|
|
|
|
|
|
|
=item Edit:Unmark All Frames
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Unmark all packets that are currently displayed.
|
2000-08-23 19:40:12 +00:00
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=item Edit:Preferences
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Set the packet printing, column display, TCP stream coloring, and GUI
|
1999-12-10 06:28:24 +00:00
|
|
|
|
options (see L<"Preferences"> below).
|
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
=item Edit:Capture Filters
|
1999-12-10 06:28:24 +00:00
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Edit the saved list of capture filters, allowing filters to be added,
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
changed, or deleted.
|
|
|
|
|
|
|
|
|
|
=item Edit:Display Filters
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Edit the saved list of display filters, allowing filters to be added,
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
changed, or deleted.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
Add the "Edit:Protocols..." feature which currently only implements
the following:
It is now possible to enable/disable a particular protocol decoding
(i.e. the protocol dissector is void or not). When a protocol
is disabled, it is displayed as Data and of course, all linked
sub-protocols are disabled as well.
Disabling a protocol could be interesting:
- in case of buggy dissectors
- in case of wrong heuristics
- for performance reasons
- to decode the data as another protocol (TODO)
Currently (if I am not wrong), all dissectors but NFS can be disabled
(and dissectors that do not register protocols :-)
I do not like the way the RPC sub-dissectors are disabled (in the
sub-dissectors) since this could be done in the RPC dissector itself,
knowing the sub-protocol hfinfo entry (this is why, I've not modified
the NFS one yet).
Two functions are added in proto.c :
gboolean proto_is_protocol_enabled(int n);
void proto_set_decoding(int n, gboolean enabled);
and two MACROs which can be used in dissectors:
OLD_CHECK_DISPLAY_AS_DATA(index, pd, offset, fd, tree)
CHECK_DISPLAY_AS_DATA(index, tvb, pinfo, tree)
See also the XXX in proto_dlg.c and proto.c around the new functions.
svn path=/trunk/; revision=2268
2000-08-13 14:20:32 +00:00
|
|
|
|
=item Edit:Protocols
|
|
|
|
|
|
2002-12-01 19:11:54 +00:00
|
|
|
|
Allow protocol dissection to be enabled or disabled for a specific
|
2002-12-02 02:28:54 +00:00
|
|
|
|
protocol. Individual protocols can be enabled or disabled by clicking
|
|
|
|
|
on them in the list or by highlighting them and pressing the space bar.
|
|
|
|
|
The entire list can be enabled, disabled, or inverted using the buttons
|
|
|
|
|
below the list.
|
2002-12-01 19:11:54 +00:00
|
|
|
|
|
|
|
|
|
When a protocol is disabled, dissection in a particular packet stops
|
|
|
|
|
when that protocol is reached, and Ethereal moves on to the next packet.
|
|
|
|
|
Any higher-layer protocols that would otherwise have been processed will
|
|
|
|
|
not be displayed. For example, disabling TCP will prevent the dissection
|
|
|
|
|
and display of TCP, HTTP, SMTP, Telnet, and any other protocol exclusively
|
|
|
|
|
dependent on TCP.
|
Add the "Edit:Protocols..." feature which currently only implements
the following:
It is now possible to enable/disable a particular protocol decoding
(i.e. the protocol dissector is void or not). When a protocol
is disabled, it is displayed as Data and of course, all linked
sub-protocols are disabled as well.
Disabling a protocol could be interesting:
- in case of buggy dissectors
- in case of wrong heuristics
- for performance reasons
- to decode the data as another protocol (TODO)
Currently (if I am not wrong), all dissectors but NFS can be disabled
(and dissectors that do not register protocols :-)
I do not like the way the RPC sub-dissectors are disabled (in the
sub-dissectors) since this could be done in the RPC dissector itself,
knowing the sub-protocol hfinfo entry (this is why, I've not modified
the NFS one yet).
Two functions are added in proto.c :
gboolean proto_is_protocol_enabled(int n);
void proto_set_decoding(int n, gboolean enabled);
and two MACROs which can be used in dissectors:
OLD_CHECK_DISPLAY_AS_DATA(index, pd, offset, fd, tree)
CHECK_DISPLAY_AS_DATA(index, tvb, pinfo, tree)
See also the XXX in proto_dlg.c and proto.c around the new functions.
svn path=/trunk/; revision=2268
2000-08-13 14:20:32 +00:00
|
|
|
|
|
2003-08-07 00:56:30 +00:00
|
|
|
|
The list of protocols can be saved, so that Ethereal will start up with
|
|
|
|
|
the protocols in that list disabled.
|
|
|
|
|
|
1999-06-19 08:48:30 +00:00
|
|
|
|
=item Capture:Start
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Initiate a live packet capture (see L<"Capture Options"> below). A
|
1999-12-16 08:05:46 +00:00
|
|
|
|
temporary file will be created to hold the capture. The location of the
|
1999-04-06 16:35:47 +00:00
|
|
|
|
file can be chosen by setting your TMPDIR environment variable before
|
1999-12-16 08:05:46 +00:00
|
|
|
|
starting B<Ethereal>. Otherwise, the default TMPDIR location is
|
2000-05-10 06:00:22 +00:00
|
|
|
|
system-dependent, but is likely either F</var/tmp> or F</tmp>.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-10-11 06:01:16 +00:00
|
|
|
|
=item Capture:Stop
|
|
|
|
|
|
|
|
|
|
In a capture that updates the packet display as packets arrive (so that
|
|
|
|
|
Ethereal responds to user input other than pressing the "Stop" button in
|
2002-03-22 23:42:27 +00:00
|
|
|
|
the capture packet statistics dialog box), stop the capture.
|
2000-10-11 06:01:16 +00:00
|
|
|
|
|
1999-06-19 08:48:30 +00:00
|
|
|
|
=item Display:Options
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Pop up a dialog allowing you to set the format of the packet timestamp
|
|
|
|
|
displayed in the packet list window to relative, absolute, absolute date
|
|
|
|
|
and time, or delta, to enable or disable the automatic scrolling of the
|
|
|
|
|
packet list while a live capture is in progress or to enable or disable
|
|
|
|
|
translation of addresses to names in the display.
|
1999-06-19 08:48:30 +00:00
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item Display:Match
|
1999-08-28 23:47:50 +00:00
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Create a display filter, or add to the display filter strip at the
|
2002-01-11 09:02:15 +00:00
|
|
|
|
bottom, a display filter based on the data currently highlighted in the
|
2002-03-22 23:42:27 +00:00
|
|
|
|
protocol tree, and apply the filter.
|
2002-01-11 09:02:15 +00:00
|
|
|
|
|
|
|
|
|
If that data is a field that can be tested in a display filter
|
|
|
|
|
expression, the display filter will test that field; otherwise, the
|
|
|
|
|
display filter will be based on absolute offset within the packet, and
|
|
|
|
|
so could be unreliable if the packet contains protocols with
|
|
|
|
|
variable-length headers, such as a source-routed token-ring packet.
|
|
|
|
|
|
|
|
|
|
The B<Selected> option creates a display filter that tests for a match
|
|
|
|
|
of the data; the B<Not Selected> option creates a display filter that
|
|
|
|
|
tests for a non-match of the data. The B<And Selected>, B<Or Selected>,
|
|
|
|
|
B<And Not Selected>, and B<Or Not Selected> options add to the end of
|
|
|
|
|
the display filter in the strip at the bottom an AND or OR operator
|
|
|
|
|
followed by the new display filter expression.
|
|
|
|
|
|
|
|
|
|
=item Display:Prepare
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Create a display filter, or add to the display filter strip at the
|
2002-01-11 09:02:15 +00:00
|
|
|
|
bottom, a display filter based on the data currently highlighted in the
|
2002-03-22 23:42:27 +00:00
|
|
|
|
protocol tree, but don't apply the filter.
|
1999-08-28 23:47:50 +00:00
|
|
|
|
|
|
|
|
|
=item Display:Colorize Display
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Change the foreground and background colors of the packet information in
|
|
|
|
|
the list of packets, based upon display filters. The list of display
|
|
|
|
|
filters is applied to each packet sequentially. After the first display
|
|
|
|
|
filter matches a packet, any additional display filters in the list are
|
|
|
|
|
ignored. Therefore, if you are filtering on the existence of protocols,
|
1999-08-28 23:47:50 +00:00
|
|
|
|
you should list the higher-level protocols first, and the lower-level
|
|
|
|
|
protocols last.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=over
|
|
|
|
|
|
|
|
|
|
=item How Colorization Works
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Packets are colored according to a list of color filters. Each filter
|
|
|
|
|
consists of a name, a filter expression and a coloration. A packet is
|
|
|
|
|
colored according to the first filter that it matches, Color filter
|
|
|
|
|
expressions use exactly the same syntax as display filter expressions.
|
|
|
|
|
|
|
|
|
|
When Ethereal starts the color filters are loaded from:
|
2003-08-27 22:55:51 +00:00
|
|
|
|
1. The user's personal color filters file or, if that does not exist,
|
|
|
|
|
2. The global color filters file.
|
2003-08-18 21:27:11 +00:00
|
|
|
|
If neither of these exist then the packets will not be colored.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item The Color Filters Dialog
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
This dialog displays a list of color filters and allows it to be
|
|
|
|
|
modified.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=over
|
|
|
|
|
|
|
|
|
|
=item THE FILTER LIST
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Single rows may be selected by clicking. Multiple rows may be selected
|
|
|
|
|
by using the ctrl and shift keys in combination with the mouse button.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item UP
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Moves the selected filter(s) up the list, making it more likely that
|
|
|
|
|
they will be used to color packets.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item DOWN
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Moves the selected filter(s) down the list, making it less likely that
|
|
|
|
|
they will be used to color packets.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item NEW
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Adds a new filter at the bottom of the list and opens the Edit Color
|
|
|
|
|
Filter dialog box. You will have to alter the filter expression at
|
|
|
|
|
least before the filter will be accepted. The format of color filter
|
|
|
|
|
expressions is identical to that of display filters. The new filter is
|
|
|
|
|
selected, so it may immediately be moved up and down, deleted or edited.
|
|
|
|
|
To avoid confusion all filters are unselected before the new filter is
|
|
|
|
|
created.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item EDIT
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Opens the Edit Color Filter dialog box for the selected filter. (If this
|
|
|
|
|
button is disabled you may have more than one filter selected, making it
|
|
|
|
|
ambiguous which is to be edited.)
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item DELETE
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Deletes the selected color filter(s).
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item OK
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Closes the dialog and uses the color filters as they stand.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item APPLY
|
|
|
|
|
|
2003-08-18 21:27:11 +00:00
|
|
|
|
Colors the packets according to the current list of color filters, but
|
|
|
|
|
does not close the dialog.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item SAVE
|
|
|
|
|
|
|
|
|
|
Saves the current list of color filters in your personal color filters
|
2003-08-18 21:27:11 +00:00
|
|
|
|
file. Unless you do this they will not be used the next time you start
|
|
|
|
|
Ethereal.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=item REVERT
|
|
|
|
|
|
|
|
|
|
Deletes your personal color filters file, reloads the global
|
|
|
|
|
color filters file, if any, and closes the dialog.
|
|
|
|
|
|
|
|
|
|
=item EXPORT
|
2003-08-18 21:27:11 +00:00
|
|
|
|
|
|
|
|
|
Allows you to choose a file in which to save the current list of color
|
|
|
|
|
filters. You may also choose to save only the selected filters. A
|
2003-08-27 22:55:51 +00:00
|
|
|
|
button is provided to save the filters in the global color filters file
|
|
|
|
|
(you must have sufficient permissions to write this file, of course).
|
|
|
|
|
|
|
|
|
|
=item IMPORT
|
2003-08-18 21:27:11 +00:00
|
|
|
|
|
|
|
|
|
Allows you to choose a file containing color filters which are then
|
|
|
|
|
added to the bottom of the current list. All the added filters are
|
|
|
|
|
selected, so they may be moved to the correct position in the list as a
|
2003-08-27 22:55:51 +00:00
|
|
|
|
group. To avoid confusion, all filters are unselected before the new
|
2003-08-18 21:27:11 +00:00
|
|
|
|
filters are imported. A button is provided to load the filters from the
|
2003-08-27 22:55:51 +00:00
|
|
|
|
global color filters file.
|
|
|
|
|
|
|
|
|
|
=item CANCEL
|
2003-08-18 21:27:11 +00:00
|
|
|
|
|
|
|
|
|
Closes the dialog without changing the coloration of the packets. Note
|
2003-08-27 22:55:51 +00:00
|
|
|
|
that changes you have made to the current list of color filters are not
|
2003-08-18 21:27:11 +00:00
|
|
|
|
undone.
|
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
=back
|
|
|
|
|
|
|
|
|
|
=back
|
2003-08-18 21:27:11 +00:00
|
|
|
|
|
1999-09-11 15:47:38 +00:00
|
|
|
|
=item Display:Collapse All
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Collapse the protocol tree branches.
|
1999-09-11 15:47:38 +00:00
|
|
|
|
|
|
|
|
|
=item Display:Expand All
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Expand all branches of the protocol tree.
|
1999-09-11 15:47:38 +00:00
|
|
|
|
|
2000-02-29 06:24:41 +00:00
|
|
|
|
=item Display:Expand All
|
|
|
|
|
|
|
|
|
|
Expands all branches of the protocol tree.
|
|
|
|
|
|
|
|
|
|
=item Display:Show Packet In New Window
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Create a new window containing a protocol tree view and a hex dump
|
2000-02-29 06:24:41 +00:00
|
|
|
|
window of the currently selected packet; this window will continue to
|
|
|
|
|
display that packet's protocol tree and data even if another packet is
|
|
|
|
|
selected.
|
|
|
|
|
|
2001-02-14 07:15:39 +00:00
|
|
|
|
=item Display:User Specified Decodes
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Create a new window showing whether any protocol ID to dissector
|
2001-02-14 07:15:39 +00:00
|
|
|
|
mappings have been changed by the user. This window also allows the
|
|
|
|
|
user to reset all decodes to their default values.
|
|
|
|
|
|
1999-12-13 12:29:42 +00:00
|
|
|
|
=item Tools:Plugins
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
See what dynamically loadable dissector plugin modules have been loaded
|
|
|
|
|
(see I<"Plugins"> below).
|
1999-12-13 12:29:42 +00:00
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=item Tools:Follow TCP Stream
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
If you have a TCP packet selected, display the contents of the data
|
|
|
|
|
stream for the TCP connection to which that packet belongs, as text, in
|
|
|
|
|
a separate window, and leave the list of packets in a filtered state,
|
|
|
|
|
with only those packets that are part of that TCP connection being
|
|
|
|
|
displayed. You can revert to your old view by pressing ENTER in the
|
|
|
|
|
display filter text box, thereby invoking your old display filter (or
|
|
|
|
|
resetting it back to no display filter).
|
1999-10-30 06:42:10 +00:00
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
The window in which the data stream is displayed lets you select:
|
2000-08-09 06:38:53 +00:00
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=over 8
|
2000-08-09 06:38:53 +00:00
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=item *
|
2000-08-09 06:38:53 +00:00
|
|
|
|
|
|
|
|
|
whether to display the entire conversation, or one or the other side of
|
|
|
|
|
it;
|
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=item *
|
2000-08-09 06:38:53 +00:00
|
|
|
|
|
|
|
|
|
whether the data being displayed is to be treated as ASCII or EBCDIC
|
|
|
|
|
text or as raw hex data;
|
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=back 4
|
2000-08-09 06:38:53 +00:00
|
|
|
|
|
|
|
|
|
and lets you print what's currently being displayed, using the same
|
|
|
|
|
print options that are used for the I<File:Print Packet> menu item, or
|
|
|
|
|
save it as text to a file.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2001-02-14 07:15:39 +00:00
|
|
|
|
=item Tools:Decode As
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
If you have a packet selected, present a dialog allowing you to change
|
|
|
|
|
which dissectors are used to decode this packet. The dialog has one
|
|
|
|
|
panel each for the link layer, network layer and transport layer
|
|
|
|
|
protocol/port numbers, and will allow each of these to be changed
|
|
|
|
|
independently. For example, if the selected packet is a TCP packet to
|
|
|
|
|
port 12345, using this dialog you can instruct Ethereal to decode all
|
|
|
|
|
packets to or from that TCP port as HTTP packets.
|
2001-02-14 07:15:39 +00:00
|
|
|
|
|
2002-12-19 05:26:42 +00:00
|
|
|
|
=item Tools:Go To Corresponding Frame
|
|
|
|
|
|
|
|
|
|
If a field in the protocol tree pane containing a frame number is
|
|
|
|
|
selected, go to the frame number specified by that field. (This works
|
|
|
|
|
only if the dissector that put that entry into the protocol tree put it
|
|
|
|
|
into the tree as a filterable field rather than just as text.) This can
|
|
|
|
|
be used, for example, to go to the frame for the request corresponding
|
|
|
|
|
to a reply, or the reply corresponding to a request, if that frame
|
|
|
|
|
number has been put into the protocol tree.
|
|
|
|
|
|
2003-09-02 22:10:32 +00:00
|
|
|
|
=item Tools:Summary
|
|
|
|
|
|
|
|
|
|
Show summary information about the capture, including elapsed time,
|
|
|
|
|
packet counts, byte counts, and the like. If a display filter is in
|
|
|
|
|
effect, summary information will be shown about the capture and about
|
|
|
|
|
the packets currently being displayed.
|
|
|
|
|
|
2001-03-22 23:54:47 +00:00
|
|
|
|
=item Tools:Protocol Hierarchy Statistics
|
|
|
|
|
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Show the number of packets, and the number of bytes in those packets,
|
|
|
|
|
for each protocol in the trace. It organizes the protocols in the same
|
|
|
|
|
hierarchy in which they were found in the trace. Besides counting the
|
|
|
|
|
packets in which the protocol exists, a count is also made for packets
|
|
|
|
|
in which the protocol is the last protocol in the stack. These
|
|
|
|
|
last-protocol counts show you how many packets (and the byte count
|
|
|
|
|
associated with those packets) B<ended> in a particular protocol. In
|
|
|
|
|
the table, they are listed under "End Packets" and "End Bytes".
|
2001-03-22 23:54:47 +00:00
|
|
|
|
|
2002-09-27 11:07:16 +00:00
|
|
|
|
=item Tools:Statistics:ONC-RPC:Programs
|
|
|
|
|
|
|
|
|
|
This dialog will open a window showing aggregated RTT statistics for all
|
|
|
|
|
ONC-RPC Programs/versions that exist in the capture file.
|
|
|
|
|
|
2003-06-21 01:42:46 +00:00
|
|
|
|
=item Tools:Statistics:Service Response Time:DCE-RPC
|
2002-10-25 01:08:49 +00:00
|
|
|
|
|
2003-06-21 01:42:46 +00:00
|
|
|
|
Open a window to display Service Response Time statistics for an
|
|
|
|
|
arbitrary DCE-RPC program
|
|
|
|
|
interface and display B<Procedure>, B<Number of Calls>, B<Minimum SRT>,
|
|
|
|
|
B<Maximum SRT> and B<Average SRT> for all procedures for that
|
2003-06-10 17:34:01 +00:00
|
|
|
|
program/version. These windows opened will update in semi-real time to
|
|
|
|
|
reflect changes when doing live captures or when reading new capture
|
|
|
|
|
files into B<Ethereal>.
|
2002-10-25 01:08:49 +00:00
|
|
|
|
|
|
|
|
|
This dialog will also allow an optional filter string to be used.
|
|
|
|
|
If an optional filter string is used only such DCE-RPC request/response pairs
|
|
|
|
|
that match that filter will be used to calculate the statistics. If no filter
|
|
|
|
|
string is specified all request/response pairs will be used.
|
2002-09-05 06:46:38 +00:00
|
|
|
|
|
2003-06-25 11:15:34 +00:00
|
|
|
|
=item Tools:Statistics:Service Response Time:Fibre Channel
|
|
|
|
|
|
|
|
|
|
Open a window to display Service Response Time statistics for Fibre Channel
|
|
|
|
|
and display B<FC Type>, B<Number of Calls>, B<Minimum SRT>,
|
|
|
|
|
B<Maximum SRT> and B<Average SRT> for all FC types.
|
|
|
|
|
These windows opened will update in semi-real time to
|
|
|
|
|
reflect changes when doing live captures or when reading new capture
|
|
|
|
|
files into B<Ethereal>.
|
|
|
|
|
The Service Response Time is calculated as the time delta between the
|
|
|
|
|
First frame of the exchange and the Last frame of the exchange.
|
|
|
|
|
|
|
|
|
|
This dialog will also allow an optional filter string to be used.
|
|
|
|
|
If an optional filter string is used only such FC first/last exchange pairs
|
|
|
|
|
that match that filter will be used to calculate the statistics. If no filter
|
|
|
|
|
string is specified all request/response pairs will be used.
|
|
|
|
|
|
2003-06-21 03:24:06 +00:00
|
|
|
|
=item Tools:Statistics:Service Response Time:ONC-RPC
|
|
|
|
|
|
|
|
|
|
Open a window to display statistics for an arbitrary ONC-RPC program interface
|
|
|
|
|
and display B<Procedure>, B<Number of Calls>, B<Minimum SRT>, B<Maximum SRT> and B<Average SRT> for all procedures for that program/version.
|
|
|
|
|
These windows opened will update in semi-real time to reflect changes when
|
|
|
|
|
doing live captures or when reading new capture files into B<Ethereal>.
|
|
|
|
|
|
|
|
|
|
This dialog will also allow an optional filter string to be used.
|
|
|
|
|
If an optional filter string is used only such ONC-RPC request/response pairs
|
|
|
|
|
that match that filter will be used to calculate the statistics. If no filter
|
|
|
|
|
string is specified all request/response pairs will be used.
|
|
|
|
|
|
2003-09-05 10:26:44 +00:00
|
|
|
|
By first selecting a conversation by clicking on it and then using the
|
|
|
|
|
right mouse button (on those platforms that have a right
|
|
|
|
|
mouse button) ethereal will display a popup menu offering several different
|
|
|
|
|
filter operations to apply to the capture.
|
|
|
|
|
|
2003-06-21 06:40:48 +00:00
|
|
|
|
=item Tools:Statistics:Service Response Time:SMB
|
|
|
|
|
|
|
|
|
|
Collect call/reply SRT (Service Response Time) data for SMB. Data collected
|
|
|
|
|
is number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
|
|
|
|
|
|
|
|
|
|
The data will be presented as separate tables for all normal SMB commands,
|
|
|
|
|
all Transaction2 commands and all NT Transaction commands.
|
|
|
|
|
Only those commands that are seen in the capture will have its stats
|
|
|
|
|
displayed.
|
|
|
|
|
Only the first command in a xAndX command chain will be used in the
|
|
|
|
|
calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
|
|
|
|
|
only the SessionSetupAndX call will be used in the statistics.
|
|
|
|
|
This is a flaw that might be fixed in the future.
|
|
|
|
|
|
|
|
|
|
You can apply an optional filter string in a dialog box, before starting
|
|
|
|
|
the calculation. The stats will only be calculated
|
|
|
|
|
on those calls matching that filter.
|
|
|
|
|
|
2003-09-05 10:26:44 +00:00
|
|
|
|
By first selecting a conversation by clicking on it and then using the
|
|
|
|
|
right mouse button (on those platforms that have a right
|
|
|
|
|
mouse button) ethereal will display a popup menu offering several different
|
|
|
|
|
filter operations to apply to the capture.
|
2003-06-21 06:40:48 +00:00
|
|
|
|
|
2003-09-04 23:37:45 +00:00
|
|
|
|
=item Tools:Statistics:Conversation List
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2003-08-24 20:32:40 +00:00
|
|
|
|
This option will open a new window that displays a list of all
|
|
|
|
|
conversations between two endpoints. The list has one row for each
|
|
|
|
|
unique conversation and displays total number of frames/bytes seen as
|
|
|
|
|
well as number of frames/bytes in each direction.
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2003-08-24 20:32:40 +00:00
|
|
|
|
By default the list is sorted according to the number of frames but by
|
|
|
|
|
clicking on the column header; it is possible to re-sort the list in
|
|
|
|
|
ascending or descending order by any column.
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2003-09-05 06:22:21 +00:00
|
|
|
|
By first selecting a conversation by clicking on it and then using the
|
|
|
|
|
right mouse button (on those platforms that have a right
|
|
|
|
|
mouse button) ethereal will display a popup menu offering several different
|
|
|
|
|
filter operations to apply to the capture.
|
|
|
|
|
|
|
|
|
|
|
2003-08-24 20:32:40 +00:00
|
|
|
|
These statistics windows can also be invoked from the Ethereal command
|
2003-09-04 23:37:45 +00:00
|
|
|
|
line using the B<-z conv> argument.
|
2003-08-24 03:31:54 +00:00
|
|
|
|
|
2002-11-15 10:55:19 +00:00
|
|
|
|
=item Tools:Statistics:Traffic:IO-Stat
|
|
|
|
|
|
|
|
|
|
Open a window where up to 5 graphs in different colors can be displayed
|
|
|
|
|
to indicate number of frames or number of bytes per second for all packets
|
|
|
|
|
matching the specified filter.
|
|
|
|
|
By default only one graph will be displayed showing number of frames per second.
|
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
The top part of the window contains the graphs and scales for the X and
|
|
|
|
|
Y axis. If the graph is too long to fit inside the window there is a
|
|
|
|
|
horizontal scrollbar below the drawing area that can scroll the graphs
|
|
|
|
|
to the left or the right. The horizontal axis displays the time into
|
|
|
|
|
the capture and the vertical axis will display the measured quantity at
|
|
|
|
|
that time.
|
|
|
|
|
|
|
|
|
|
Below the drawing area and the scrollbar are the controls. On the
|
|
|
|
|
bottom left there will be five similar sets of controls to control each
|
|
|
|
|
induvidual graph such as "Display:<button>" which button will toggle
|
|
|
|
|
that individual graph on/off. If <button> is ticked, the graph will be
|
|
|
|
|
displayed. "Color:<color>" which is just a button to show which color
|
|
|
|
|
will be used to draw that graph (color is only available in Gtk2
|
|
|
|
|
version) and finally "Filter:<filter-text>" which can be used to specify
|
|
|
|
|
a display filter for that particular graph.
|
|
|
|
|
|
|
|
|
|
If filter-text is empty then all packets will be used to calculate the
|
|
|
|
|
quantity for that graph. If filter-text is specified only those packets
|
|
|
|
|
that match that display filter will be considered in the calculation of
|
|
|
|
|
quantity.
|
|
|
|
|
|
|
|
|
|
To the right of the 5 graph controls there are four menus to control
|
|
|
|
|
global aspects of the draw area and graphs. The "Unit:" menu is used to
|
|
|
|
|
control what to measure; "frames/tick", "bytes/tick" or "advanced..."
|
|
|
|
|
|
|
|
|
|
frames/tick will measure the number of frames matching the (if
|
|
|
|
|
specified) display filter for the graph in each measurement interval.
|
|
|
|
|
|
|
|
|
|
bytes/tick will measure the total number of bytes in all frames matching
|
|
|
|
|
the (if specified) display filter for the graph in each measurement
|
|
|
|
|
interval.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
|
|
|
|
advanced... see below
|
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
"Tick interval:" specifies what measurement intervals to use. The
|
|
|
|
|
default is 1 second and means that the data will be counted over 1
|
|
|
|
|
second intervals.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
"Pixels per tick:" specifies how many pixels wide each measurement
|
|
|
|
|
interval will be in the drawing area. The default is 5 pixels per tick.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
"Y-scale:" controls the max value for the y-axis. Default value is
|
|
|
|
|
"auto" which means that B<Ethereal> will try to adjust the maxvalue
|
|
|
|
|
automatically.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
"advanced..." If Unit:advanced... is selected the window will display
|
|
|
|
|
two more controls for each of the five graphs. One control will be a
|
|
|
|
|
menu where the type of calculation can be selected from
|
2003-10-15 13:10:54 +00:00
|
|
|
|
SUM,COUNT,MAX,MIN,AVG and LOAD, and one control, textbox, where the name of a
|
2003-06-10 17:34:01 +00:00
|
|
|
|
single display filter field can be specified.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
|
|
|
|
The following restrictions apply to type and field combinations:
|
2003-06-10 17:34:01 +00:00
|
|
|
|
SUM: available for all types of integers.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
COUNT: available for all field types.
|
|
|
|
|
MAX: available for all integer and relative time fields.
|
|
|
|
|
MIN: available for all integer and relative time fields.
|
|
|
|
|
AVG: available for all integer and relative time fields.
|
2003-10-15 13:10:54 +00:00
|
|
|
|
LOAD: available only for relative time fields (response times).
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
2003-06-10 17:34:01 +00:00
|
|
|
|
NOTE: due to the way this is implemented in B<Ethereal> there is a
|
|
|
|
|
requirement that whatever field is specified in the textbox, that field
|
|
|
|
|
MUST also be part of the filter for the graph or else the calculations
|
|
|
|
|
will fail.
|
2002-11-29 11:37:33 +00:00
|
|
|
|
|
|
|
|
|
Example of advanced:
|
|
|
|
|
Display how NFS response time MAX/MIN/AVG changes over time:
|
|
|
|
|
|
|
|
|
|
Set first graph to filter:nfs&&rpc.time Calc:MAX rpc.time
|
|
|
|
|
Set second graph to filter:nfs&&rpc.time Calc:AVG rpc.time
|
|
|
|
|
Set third graph to filter:nfs&&rpc.time Calc:MIN rpc.time
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Example of advanced:
|
|
|
|
|
Display how the average packetsize from host a.b.c.d changes over time.
|
|
|
|
|
|
|
|
|
|
Set first graph to filter:ip.addr==a.b.c.d&&frame.pkt_len Calc:AVG frame.pkt_len
|
|
|
|
|
|
|
|
|
|
|
2003-10-15 13:10:54 +00:00
|
|
|
|
LOAD:
|
|
|
|
|
The LOAD io-stat type is very different from anything you have ever seen
|
|
|
|
|
before! While the response times themself as plotted by MIN,MAX,AVG are
|
|
|
|
|
indications on the Server load (which affects the Server response time),
|
|
|
|
|
the LOAD measurement measures the Client LOAD.
|
|
|
|
|
What this measures is how much workload the client generates,
|
|
|
|
|
i.e. how fast will the client issue new commands when the previous ones
|
|
|
|
|
completed.
|
|
|
|
|
i.e. the level of concurrency the client can maintain.
|
|
|
|
|
The higher the number, the more and faster is the client issuing new
|
|
|
|
|
commands. When the LOAD goes down, it may be due to client load making
|
|
|
|
|
the client slower in issuing new commands (there may be other reasons as
|
|
|
|
|
well, maybe the client just dont have any commands it wants to issue
|
|
|
|
|
right then).
|
|
|
|
|
|
|
|
|
|
Load is measured in concurrency/number of overlapping i/o and the value
|
|
|
|
|
1000 means there is a constant load of one i/o.
|
|
|
|
|
|
|
|
|
|
In each tick interval the amount of overlap is measured.
|
|
|
|
|
See the graph below containing three commands:
|
|
|
|
|
Below the graph are the LOAD values for each interval that would be calculated.
|
|
|
|
|
| | | | | | | | |
|
|
|
|
|
| | | | | | | | |
|
|
|
|
|
| | o=====* | | | | | |
|
|
|
|
|
| | | | | | | | |
|
|
|
|
|
| o========* | o============* | | |
|
|
|
|
|
| | | | | | | | |
|
|
|
|
|
--------------------------------------------------> Time
|
|
|
|
|
500 1500 500 750 1000 500 0 0
|
|
|
|
|
|
|
|
|
|
|
2003-08-21 17:48:04 +00:00
|
|
|
|
=item Tools:Statistics:Service Response Time:MGCP
|
2003-04-27 21:52:24 +00:00
|
|
|
|
|
2003-08-21 17:48:04 +00:00
|
|
|
|
Collect requests/response SRT (Service Response Time) data for MGCP.
|
|
|
|
|
Data collected is B<number of calls> for each known MGCP Type,
|
|
|
|
|
B<Minimum SRT>, B<Maximum SRT> and B<Average SRT>.
|
|
|
|
|
These windows opened will update in semi-real time to reflect changes when
|
|
|
|
|
doing live captures or when reading new capture files into B<Ethereal>.
|
2003-04-27 21:52:24 +00:00
|
|
|
|
|
|
|
|
|
You can apply an optional filter string in a dialog box, before starting
|
2003-08-21 17:48:04 +00:00
|
|
|
|
the calculation. The statistics will only be calculated
|
2003-04-27 21:52:24 +00:00
|
|
|
|
on those calls matching that filter.
|
|
|
|
|
|
2003-10-28 00:31:17 +00:00
|
|
|
|
=item Tools:Statistics:Watch protocol:ITU-T H.225
|
|
|
|
|
|
|
|
|
|
Count ITU-T H.225 messages and their reasons. In the first column you get a
|
|
|
|
|
list of H.225 messages and H.225 message reasons, which occur in the current
|
|
|
|
|
capture file. The number of occurences of each message or reason will be displayed
|
|
|
|
|
in the second column.
|
|
|
|
|
This window opened will update in semi-real time to reflect changes when
|
|
|
|
|
doing live captures or when reading new capture files into B<Ethereal>.
|
|
|
|
|
|
|
|
|
|
You can apply an optional filter string in a dialog box, before starting
|
|
|
|
|
the counter. The statistics will only be calculated
|
|
|
|
|
on those calls matching that filter.
|
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=back
|
2002-11-15 10:55:19 +00:00
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=head2 WINDOWS
|
|
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
|
|
=item Main Window
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
The main window is split into three panes. You can resize each pane using
|
|
|
|
|
a "thumb" at the right end of each divider line. Below the panes is a
|
2000-07-03 08:36:52 +00:00
|
|
|
|
strip that shows the current filter and informational text.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-05-10 06:00:22 +00:00
|
|
|
|
=over 6
|
|
|
|
|
|
|
|
|
|
=item Top Pane
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
The top pane contains the list of network packets that you can scroll
|
2000-05-10 06:00:22 +00:00
|
|
|
|
through and select. By default, the packet number, packet timestamp,
|
|
|
|
|
source and destination addresses, protocol, and description are
|
|
|
|
|
displayed for each packet; the I<Columns> page in the dialog box popped
|
|
|
|
|
up by I<Edit:Preferences> lets you change this (although, unfortunately,
|
|
|
|
|
you currently have to save the preferences, and exit and restart
|
|
|
|
|
Ethereal, for those changes to take effect).
|
|
|
|
|
|
|
|
|
|
If you click on the heading for a column, the display will be sorted by
|
|
|
|
|
that column; clicking on the heading again will reverse the sort order
|
|
|
|
|
for that column.
|
|
|
|
|
|
|
|
|
|
An effort is made to display information as high up the protocol stack
|
|
|
|
|
as possible, e.g. IP addresses are displayed for IP packets, but the
|
|
|
|
|
MAC layer address is displayed for unknown packet types.
|
|
|
|
|
|
|
|
|
|
The right mouse button can be used to pop up a menu of operations.
|
|
|
|
|
|
2000-08-23 19:40:12 +00:00
|
|
|
|
The middle mouse button can be used to mark a packet.
|
|
|
|
|
|
2000-05-10 06:00:22 +00:00
|
|
|
|
=item Middle Pane
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
The middle pane contains a I<protocol tree> for the currently-selected
|
2000-01-18 08:38:18 +00:00
|
|
|
|
packet. The tree displays each field and its value in each protocol
|
|
|
|
|
header in the stack. The right mouse button can be used to pop up a
|
|
|
|
|
menu of operations.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-05-10 06:00:22 +00:00
|
|
|
|
=item Bottom Pane
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
The lowest pane contains a hex dump of the actual packet data.
|
|
|
|
|
Selecting a field in the I<protocol tree> highlights the corresponding
|
|
|
|
|
bytes in this section.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-08-23 19:40:12 +00:00
|
|
|
|
The right mouse button can be used to pop up a menu of operations.
|
|
|
|
|
|
2000-05-10 06:00:22 +00:00
|
|
|
|
=item Current Filter
|
|
|
|
|
|
1999-07-15 15:33:52 +00:00
|
|
|
|
A display filter can be entered into the strip at the bottom.
|
|
|
|
|
A filter for HTTP, HTTPS, and DNS traffic might look like this:
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-07-12 05:47:29 +00:00
|
|
|
|
tcp.port == 80 || tcp.port == 443 || tcp.port == 53
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
Selecting the I<Filter:> button lets you choose from a list of named
|
1999-07-12 05:47:29 +00:00
|
|
|
|
filters that you can optionally save. Pressing the Return or Enter
|
2002-01-11 09:02:15 +00:00
|
|
|
|
keys, or selecting the I<Apply> button, will cause the filter to be
|
|
|
|
|
applied to the current list of packets. Selecting the I<Reset> button
|
|
|
|
|
clears the display filter so that all packets are displayed.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2000-05-10 06:00:22 +00:00
|
|
|
|
=back
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=item Preferences
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-16 08:05:46 +00:00
|
|
|
|
The I<Preferences> dialog lets you control various personal preferences
|
|
|
|
|
for the behavior of B<Ethereal>.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=over 6
|
|
|
|
|
|
|
|
|
|
=item Printing Preferences
|
|
|
|
|
|
|
|
|
|
The radio buttons at the top of the I<Printing> page allow you choose
|
1999-12-16 08:05:46 +00:00
|
|
|
|
between printing packets with the I<File:Print Packet> menu item as text
|
|
|
|
|
or PostScript, and sending the output directly to a command or saving it
|
2002-01-11 09:02:15 +00:00
|
|
|
|
to a file. The I<Command:> text entry box, on UNIX-compatible systems,
|
|
|
|
|
is the command to send files to (usually B<lpr>), and the I<File:> entry
|
|
|
|
|
box lets you enter the name of the file you wish to save to.
|
|
|
|
|
Additionally, you can select the I<File:> button to browse the file
|
|
|
|
|
system for a particular save file.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
=item Column Preferences
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
The I<Columns> page lets you specify the number, title, and format
|
|
|
|
|
of each column in the packet list.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
The I<Column title> entry is used to specify the title of the column
|
|
|
|
|
displayed at the top of the packet list. The type of data that the column
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
displays can be specified using the I<Column format> option menu.
|
|
|
|
|
The row of buttons on the left perform the following actions:
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1998-12-29 04:05:38 +00:00
|
|
|
|
=over 6
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
2002-04-22 02:03:53 +00:00
|
|
|
|
=item Add New
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
Adds a new column to the list.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item Delete
|
|
|
|
|
|
|
|
|
|
Deletes the currently selected list item.
|
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
=item Up / Down
|
|
|
|
|
|
|
|
|
|
Moves the selected list item up or down one position.
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=item OK
|
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
Currently has no effect.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item Save
|
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
Saves the current column format as the default.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=item Cancel
|
|
|
|
|
|
|
|
|
|
Closes the dialog without making any changes.
|
|
|
|
|
|
1998-10-13 02:10:57 +00:00
|
|
|
|
=back
|
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item TCP Streams Preferences
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
The I<TCP Streams> page can be used to change the color of the text
|
|
|
|
|
displayed in the TCP stream window. To change a color, simply select
|
|
|
|
|
an attribute from the "Set:" menu and use the color selector to get the
|
|
|
|
|
desired color. The new text colors are displayed in a sample window.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item User Interface Preferences
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
The I<User Interface> page is used to modify small aspects of the GUI to
|
|
|
|
|
your own personal taste:
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
|
|
|
|
|
|
|
|
|
=over 6
|
|
|
|
|
|
|
|
|
|
=item Scrollbars
|
|
|
|
|
|
|
|
|
|
The vertical scrollbars in the three panes can be set to be either on
|
|
|
|
|
the left or the right.
|
|
|
|
|
|
|
|
|
|
=item Selection Bars
|
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
The selection bar in the packet list and protocol tree can have either a
|
|
|
|
|
"browse" or "select" behavior. If the selection bar has a "browse"
|
|
|
|
|
behavior, the arrow keys will move an outline of the selection bar,
|
|
|
|
|
allowing you to browse the rest of the list or tree without changing the
|
|
|
|
|
selection until you press the space bar. If the selection bar has a
|
|
|
|
|
"select" behavior, the arrow keys will move the selection bar and change
|
Changed the protocol tree widget from a GtkTree to a GtkCTree. The two reasons
I did this:
First, Havoc Pennington, in "GTK+/Gnome Application Development", in
Appendix seciton A.3.88, recommends using GtkCTree instead of GtkTree
because GtkCtree is faster, and GtkTree has limitation on its total row
height: since it must fit inside a GdkWindow, it is limited to 32,768
pixels of height. GtkTree is more flexible with regards to the types of
widgets that can be placed in the tree, but since we deal only with text,
that doesn't matter, at least for now.
Secondly, a GtkTree doesn't allow arrow-key navigation (at least as far
as I could tell). It always bothered me that the up and down arrow keys
worked in the packet list and in the hex dump, but no in the protocol tree.
GtkCTree does allow arrow-key navigation. In fact, GtkCTree is a subclass
of GtkCList (the packet list widget), so they behave a lot alike.
I went ahead and fixed the selection bar which has been bothering Richard
for a long time now. :) In the GUI preferences dialogue, you can now set
both the packet list selection bar and the protocol tree selection bar
to either "browse" or "select" mode. "browse" mode is what you're used to:
the arrow keys move an outline of the selection bar, but do not change
the selection. "select" mode does change the selection when the arrow keys
are pressed. The default behavior is set to "select", which seems more
natural for a first-time user.
svn path=/trunk/; revision=1393
1999-12-29 20:10:12 +00:00
|
|
|
|
the selection to the new item in the packet list or protocol tree.
|
2002-01-11 09:02:15 +00:00
|
|
|
|
|
|
|
|
|
=item Tree Line Style
|
|
|
|
|
|
|
|
|
|
Trees can be drawn with no lines, solid lines, or dotted lines between
|
|
|
|
|
items, or can be drawn with "tab" headings.
|
|
|
|
|
|
|
|
|
|
=item Tree Expander Style
|
|
|
|
|
|
|
|
|
|
The expander item that can be clicked to show or hide items under a tree
|
|
|
|
|
item can be omitted (note that this will prevent you from changing
|
|
|
|
|
whether those items are shown or hidden!), or can be drawn as squares,
|
|
|
|
|
triangles, or circles.
|
|
|
|
|
|
|
|
|
|
=item Hex Display
|
|
|
|
|
|
2000-09-08 09:50:08 +00:00
|
|
|
|
The highlight method in the hex dump display for the selected protocol
|
|
|
|
|
item can be set to use either inverse video, or bold characters.
|
1999-12-16 06:20:18 +00:00
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item Save Window Position
|
|
|
|
|
|
|
|
|
|
If this item is selected, the position of the main Ethereal window will
|
|
|
|
|
be saved when Ethereal exits, and used when Ethereal is started again.
|
|
|
|
|
|
|
|
|
|
=item Save Window Size
|
|
|
|
|
|
|
|
|
|
If this item is selected, the size of the main Ethereal window will
|
|
|
|
|
be saved when Ethereal exits, and used when Ethereal is started again.
|
|
|
|
|
|
2003-10-14 23:20:17 +00:00
|
|
|
|
=item File Open Dialog Behavior
|
|
|
|
|
|
|
|
|
|
This item allows the user to select how Ethereal handles the listing
|
|
|
|
|
of the "File Open" Dialog when opening trace files. "Remember Last
|
|
|
|
|
Directory" causes Ethereal to automatically position the dialog in the
|
|
|
|
|
directory of the most recently opened file, even between launches of Ethereal.
|
|
|
|
|
"Always Open in Directory" allows the user to define a persistent directory
|
|
|
|
|
that the dialog will always default to.
|
|
|
|
|
|
|
|
|
|
=item Directory:
|
|
|
|
|
|
|
|
|
|
Allows the user to specify a persistent File Open directory. Trailing
|
|
|
|
|
slashes or backslashes will automatically be added.
|
|
|
|
|
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
|
|
|
|
=item Fonts
|
|
|
|
|
|
|
|
|
|
The "Font..." button lets you select the font to be used for most text.
|
|
|
|
|
|
2000-08-23 19:40:12 +00:00
|
|
|
|
=item Colors
|
|
|
|
|
|
|
|
|
|
The "Colors..." button lets you select the colors to be used for instance
|
|
|
|
|
for the marked frames.
|
|
|
|
|
|
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
|
|
|
|
=back
|
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item Capture Preferences
|
|
|
|
|
|
|
|
|
|
The I<Capture> page lets you specify various parameters for capturing
|
|
|
|
|
live packet data; these are used the first time a capture is started.
|
|
|
|
|
|
|
|
|
|
The I<Interface:> combo box lets you specify the interface from which to
|
|
|
|
|
capture packet data, or the name of a FIFO from which to get the packet
|
2003-11-01 02:30:18 +00:00
|
|
|
|
data.
|
|
|
|
|
|
|
|
|
|
The I<Data link type:> option menu lets you, for some interfaces, select
|
|
|
|
|
the data link header you want to see on the packets you capture. For
|
|
|
|
|
example, in some OSes and with some versions of libpcap, you can choose,
|
|
|
|
|
on an 802.11 interface, whether the packets should appear as Ethernet
|
|
|
|
|
packets (with a fake Ethernet header) or as 802.11 packets.
|
|
|
|
|
|
|
|
|
|
The I<Limit each packet to ... bytes> check box lets you set the
|
|
|
|
|
snapshot length to use when capturing live data; turn on the check box,
|
|
|
|
|
and then set the number of bytes to use as the snapshot length.
|
|
|
|
|
|
|
|
|
|
The I<Filter:> text entry lets you set a capture filter expression to be
|
|
|
|
|
used when capturing.
|
|
|
|
|
|
|
|
|
|
The I<Capture packets in promiscuous mode> check box lets you specify
|
|
|
|
|
whether to put the interface in promiscuous mode when capturing.
|
|
|
|
|
|
|
|
|
|
The I<Update list of packets in real time> check box lets you specify
|
|
|
|
|
that the display should be updated as packets are seen.
|
|
|
|
|
|
|
|
|
|
The I<Automatic scrolling in live capture> check box lets you specify
|
|
|
|
|
whether, in an "Update list of packets in real time" capture, the packet
|
|
|
|
|
list pane should automatically scroll to show the most recently captured
|
|
|
|
|
packets.
|
2002-01-11 09:02:15 +00:00
|
|
|
|
|
2000-07-09 04:09:09 +00:00
|
|
|
|
=item Protocol Preferences
|
|
|
|
|
|
|
|
|
|
There are also pages for various protocols that Ethereal dissects,
|
|
|
|
|
controlling the way Ethereal handles those protocols.
|
|
|
|
|
|
1999-12-16 06:20:18 +00:00
|
|
|
|
=back
|
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
=item Edit Capture Filter List
|
|
|
|
|
|
|
|
|
|
=item Edit Display Filter List
|
|
|
|
|
|
|
|
|
|
=item Capture Filter
|
|
|
|
|
|
|
|
|
|
=item Display Filter
|
|
|
|
|
|
|
|
|
|
=item Read Filter
|
|
|
|
|
|
|
|
|
|
=item Search Filter
|
|
|
|
|
|
|
|
|
|
The I<Edit Capture Filter List> dialog lets you create, modify, and
|
|
|
|
|
delete capture filters, and the I<Edit Display Filter List> dialog lets
|
|
|
|
|
you create, modify, and delete display filters.
|
|
|
|
|
|
|
|
|
|
The I<Capture Filter> dialog lets you do all of the editing operations
|
|
|
|
|
listed, and also lets you choose or construct a filter to be used when
|
|
|
|
|
capturing packets.
|
|
|
|
|
|
|
|
|
|
The I<Display Filter> dialog lets you do all of the editing operations
|
|
|
|
|
listed, and also lets you choose or construct a filter to be used to
|
|
|
|
|
filter the current capture being viewed.
|
|
|
|
|
|
|
|
|
|
The I<Read Filter> dialog lets you do all of the editing operations
|
|
|
|
|
listed, and also lets you choose or construct a filter to be used to
|
|
|
|
|
as a read filter for a capture file you open.
|
1999-12-10 06:28:24 +00:00
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
The I<Search Filter> dialog lets you do all of the editing operations
|
|
|
|
|
listed, and also lets you choose or construct a filter expression to be
|
|
|
|
|
used in a find operation.
|
1999-12-10 06:28:24 +00:00
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
In all of those dialogs, the I<Filter name> entry specifies a
|
|
|
|
|
descriptive name for a filter, e.g. B<Web and DNS traffic>. The
|
|
|
|
|
I<Filter string> entry is the text that actually describes the filtering
|
|
|
|
|
action to take, as described above.The dialog buttons perform the
|
|
|
|
|
following actions:
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=over 6
|
|
|
|
|
|
|
|
|
|
=item New
|
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
If there is text in the two entry boxes, creates a new associated list
|
1999-12-10 06:28:24 +00:00
|
|
|
|
item.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=item Change
|
|
|
|
|
|
1999-12-10 06:28:24 +00:00
|
|
|
|
Modifies the currently selected list item to match what's in the entry
|
|
|
|
|
boxes.
|
|
|
|
|
|
|
|
|
|
=item Copy
|
|
|
|
|
|
|
|
|
|
Makes a copy of the currently selected list item.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=item Delete
|
|
|
|
|
|
|
|
|
|
Deletes the currently selected list item.
|
|
|
|
|
|
2001-01-02 01:32:21 +00:00
|
|
|
|
=item Add Expression...
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
For display filter expressions, pops up a dialog box to allow you to
|
|
|
|
|
construct a filter expression to test a particular field; it offers
|
|
|
|
|
lists of field names, and, when appropriate, lists from which to select
|
|
|
|
|
tests to perform on the field and values with which to compare it. In
|
|
|
|
|
that dialog box, the OK button will cause the filter expression you
|
|
|
|
|
constructed to be entered into the I<Filter string> entry at the current
|
|
|
|
|
cursor position.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=item OK
|
|
|
|
|
|
2001-01-28 21:30:53 +00:00
|
|
|
|
In the I<Capture Filter> dialog, closes the dialog box and makes the
|
|
|
|
|
filter in the I<Filter string> entry the filter in the I<Capture
|
|
|
|
|
Preferences> dialog. In the I<Display Filter> dialog, closes the dialog
|
|
|
|
|
box and makes the filter in the I<Filter string> entry the current
|
|
|
|
|
display filter, and applies it to the current capture. In the I<Read
|
|
|
|
|
Filter> dialog, closes the dialog box and makes the filter in the
|
|
|
|
|
I<Filter string> entry the filter in the I<Open Capture File> dialog.
|
|
|
|
|
In the I<Search Filter> dialog, closes the dialog box and makes the
|
|
|
|
|
filter in the I<Filter string> entry the filter in the I<Find Frame>
|
|
|
|
|
dialog.
|
2001-01-02 01:32:21 +00:00
|
|
|
|
|
|
|
|
|
=item Apply
|
|
|
|
|
|
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
|
|
|
|
Makes the filter in the I<Filter string> entry the current display
|
|
|
|
|
filter, and applies it to the current capture.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=item Save
|
|
|
|
|
|
2001-10-23 08:15:11 +00:00
|
|
|
|
Saves the current filter list in F<$HOME/.ethereal/cfilters> on
|
2001-10-24 06:13:07 +00:00
|
|
|
|
UNIX-compatible systems, and F<%APPDATA%\Ethereal\cfilters> (or, if
|
|
|
|
|
%APPDATA% isn't defined,
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\cfilters>)
|
|
|
|
|
on Windows systems, if the list of filters being edited is the list of
|
2001-10-23 08:15:11 +00:00
|
|
|
|
capture filters, or in F<$HOME/.ethereal/dfilters> on UNIX-compatible
|
2001-10-24 06:13:07 +00:00
|
|
|
|
systems, and F<%APPDATA%\Ethereal\dfilters> (or, if %APPDATA% isn't
|
|
|
|
|
defined, F<%USERPROFILE%\Application Data\Ethereal\dfilters>) on Windows
|
|
|
|
|
systems, if the list of filters being edited is the list of display
|
|
|
|
|
filters.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
2001-01-28 21:30:53 +00:00
|
|
|
|
=item Close
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
2001-01-28 21:30:53 +00:00
|
|
|
|
Closes the dialog without doing anything with the filter in the I<Filter
|
|
|
|
|
string> entry.
|
1998-12-29 04:05:38 +00:00
|
|
|
|
|
|
|
|
|
=back
|
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
=item Capture Options
|
1998-10-13 02:10:57 +00:00
|
|
|
|
|
2002-01-11 09:02:15 +00:00
|
|
|
|
The I<Capture Options> dialog lets you specify various parameters for
|
1998-10-13 02:10:57 +00:00
|
|
|
|
capturing live packet data.
|
|
|
|
|
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
The I<Interface:> field lets you specify the interface from which to
|
2002-01-11 09:02:15 +00:00
|
|
|
|
capture packet data or a command from which to get the packet data via a
|
|
|
|
|
pipe.
|
|
|
|
|
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
The I<Limit each packet to ... bytes> check box and field lets you
|
|
|
|
|
specify a maximum number of bytes per packet to capture and save; if the
|
|
|
|
|
check box is not checked, the limit will be 65535 bytes.
|
2002-01-11 09:02:15 +00:00
|
|
|
|
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
The I<Capture packets in promiscuous mode> check box lets you specify
|
|
|
|
|
whether the interface should be put into promiscuous mode when
|
|
|
|
|
capturing.
|
2002-01-11 09:02:15 +00:00
|
|
|
|
|
|
|
|
|
The I<Filter:> entry lets you specify the capture filter using a
|
|
|
|
|
tcpdump-style filter string as described above.
|
|
|
|
|
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
The I<File:> entry lets you specify the file into which captured packets
|
|
|
|
|
should be saved, as in the I<Printer Options> dialog above. If not
|
|
|
|
|
specified, the captured packets will be saved in a temporary file; you
|
|
|
|
|
can save those packets to a file with the I<File:Save As> menu item.
|
|
|
|
|
|
|
|
|
|
The I<Use ring buffer> check box lets you specify that the capture
|
|
|
|
|
should be done in "ring buffer" mode; the I<Number of files> field
|
2003-06-22 16:09:04 +00:00
|
|
|
|
lets you specify the number of files in the ring buffer (0 means unlimited).
|
2003-05-15 13:40:20 +00:00
|
|
|
|
|
|
|
|
|
The I<Rotate capture file every ... second(s)> check box and field lets
|
|
|
|
|
you to specify that the swith to a next ring buffer file should be done
|
|
|
|
|
if the specified duration has elapsed even if the specified capture size
|
|
|
|
|
is not reached.
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
|
|
|
|
|
The I<Update list of packets in real time> check box lets you specify
|
|
|
|
|
whether the display should be updated as packets are captured and, if
|
|
|
|
|
you specify that, the I<Automatic scrolling in live capture> check box
|
|
|
|
|
lets you specify the packet list pane should automatically scroll to
|
|
|
|
|
show the most recently captured packets as new packets arrive.
|
|
|
|
|
|
|
|
|
|
The I<Stop capture after ... packet(s) captured> check box and field let
|
|
|
|
|
you specify that Ethereal should stop capturing after having captured
|
|
|
|
|
some number of packets; if the check box is not checked, Ethereal will
|
|
|
|
|
not stop capturing at some fixed number of captured packets.
|
|
|
|
|
|
|
|
|
|
If "ring buffer" mode is not specified, the I<Stop capture after ...
|
|
|
|
|
kilobyte(s) captured> check box and field let you specify that Ethereal
|
|
|
|
|
should stop capturing after the the file to which captured packets are
|
|
|
|
|
being saved grows as large as or larger than some specified number of
|
|
|
|
|
kilobytes (where a kilobyte is 1000 bytes, not 1024 bytes). If the
|
|
|
|
|
check box is not checked, Ethereal will not stop capturing at some
|
|
|
|
|
capture file size (although the operating system on which Ethereal is
|
|
|
|
|
running, or the available disk space, may still limit the maximum size
|
|
|
|
|
of a capture file).
|
|
|
|
|
|
|
|
|
|
If "ring buffer" mode is specified, that field becomes the I<Rotate
|
2003-05-15 13:40:20 +00:00
|
|
|
|
capture file every ... kilobyte(s)> field, and specifies the number
|
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
|
|
|
|
of kilobytes at which to start writing to a new ring buffer file; the
|
|
|
|
|
check box is forced to be checked, as "ring buffer" mode requires a file
|
|
|
|
|
size to be specified.
|
|
|
|
|
|
|
|
|
|
The I<Stop capture after ... second(s)> check box and field let you
|
|
|
|
|
specify that Ethereal should stop capturing after it has been capturing
|
|
|
|
|
for some number of seconds; if the check box is not checked, Ethereal
|
|
|
|
|
will not stop capturing after some fixed time has elapsed.
|
|
|
|
|
|
|
|
|
|
The I<Enable MAC name resolution>, I<Enable network name resolution> and
|
|
|
|
|
I<Enable transport name resolution> check boxes let you specify whether
|
|
|
|
|
MAC addresses, network addresses, and transport-layer port numbers
|
|
|
|
|
should be translated to names.
|
1998-10-13 02:10:57 +00:00
|
|
|
|
|
1999-06-19 08:48:30 +00:00
|
|
|
|
=item Display Options
|
|
|
|
|
|
2000-11-01 08:31:36 +00:00
|
|
|
|
The I<Display Options> dialog lets you specify the format of the time
|
|
|
|
|
stamp in the packet list. You can select "Time of day" for absolute
|
|
|
|
|
time stamps, "Date and time of day" for absolute time stamps with the
|
|
|
|
|
date, "Seconds since beginning of capture" for relative time stamps, or
|
1999-09-23 06:34:18 +00:00
|
|
|
|
"Seconds since previous frame" for delta time stamps. You can also
|
|
|
|
|
specify whether, when the display is updated as packets are captured,
|
|
|
|
|
the list should automatically scroll to show the most recently captured
|
2001-05-31 08:36:46 +00:00
|
|
|
|
packets or not and whether addresses or port numbers should be
|
|
|
|
|
translated to names in the display on a MAC, network and transport layer
|
|
|
|
|
basis.
|
1999-06-19 08:48:30 +00:00
|
|
|
|
|
1999-12-13 12:29:42 +00:00
|
|
|
|
=item Plugins
|
|
|
|
|
|
2001-01-28 21:22:54 +00:00
|
|
|
|
The I<Plugins> dialog lets you view the dissector plugin modules
|
|
|
|
|
available on your system.
|
|
|
|
|
|
|
|
|
|
The I<Plugins List> shows the name and version of each dissector plugin
|
|
|
|
|
module found on your system. The plugins are searched in the following
|
2001-10-23 08:15:11 +00:00
|
|
|
|
directories: the F<lib/ethereal/plugins/$VERSION> directory under the
|
|
|
|
|
main installation directory (for example,
|
|
|
|
|
F</usr/local/lib/ethereal/plugins/$VERSION>),
|
|
|
|
|
F</usr/lib/ethereal/plugins/$VERSION>,
|
|
|
|
|
F</usr/local/lib/ethereal/plugins/$VERSION>, and
|
|
|
|
|
F<$HOME/.ethereal/plugins> on UNIX-compatible systems, and in the
|
|
|
|
|
F<plugins\$VERSION> directory under the main installation directory (for
|
|
|
|
|
example, F<C:\Program Files\Ethereal\plugins\$VERSION>) and
|
2001-10-24 06:13:07 +00:00
|
|
|
|
F<%APPDATA%\Ethereal\plugins\$VERSION> (or, if %APPDATA% isn't defined,
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\plugins\$VERSION>) on Windows
|
2001-10-23 08:15:11 +00:00
|
|
|
|
systems; $VERSION is the version number of the plugin interface, which
|
|
|
|
|
is typically the version number of Ethereal. Note that a dissector
|
|
|
|
|
plugin module may support more than one protocol; there is not
|
|
|
|
|
necessarily a one-to-one correspondence between dissector plugin modules
|
|
|
|
|
and protocols. Protocols supported by a dissector plugin module are
|
|
|
|
|
enabled and disabled using the I<Edit:Protocols> dialog box, just as
|
2001-01-28 21:22:54 +00:00
|
|
|
|
protocols built into Ethereal are.
|
1999-12-13 12:29:42 +00:00
|
|
|
|
|
2003-03-10 04:27:01 +00:00
|
|
|
|
=back
|
|
|
|
|
|
1999-10-10 16:25:28 +00:00
|
|
|
|
=head1 CAPTURE FILTER SYNTAX
|
|
|
|
|
|
2003-10-15 02:13:33 +00:00
|
|
|
|
See the tcpdump(8) manual page.
|
1999-10-10 16:25:28 +00:00
|
|
|
|
|
2003-10-01 20:36:36 +00:00
|
|
|
|
=head1 DISPLAY FILTER SYNTAX
|
1999-07-15 15:33:52 +00:00
|
|
|
|
|
2003-10-01 14:59:41 +00:00
|
|
|
|
For a complete table of protocol and protocol fields that are filterable
|
2003-10-15 02:13:33 +00:00
|
|
|
|
in B<Ethereal> see ethereal-filter(4).
|
1999-07-15 15:33:52 +00:00
|
|
|
|
|
1999-11-20 03:39:27 +00:00
|
|
|
|
=head1 FILES
|
1999-11-20 03:56:10 +00:00
|
|
|
|
|
2001-10-21 19:54:49 +00:00
|
|
|
|
The F<ethereal.conf> file, which is installed in the F<etc> directory
|
|
|
|
|
under the main installation directory (for example, F</usr/local/etc>)
|
|
|
|
|
on UNIX-compatible systems, and in the main installation directory (for
|
2001-10-23 08:15:11 +00:00
|
|
|
|
example, F<C:\Program Files\Ethereal>) on Windows systems, and the
|
|
|
|
|
personal preferences file, which is F<$HOME/.ethereal/preferences> on
|
2001-10-24 06:13:07 +00:00
|
|
|
|
UNIX-compatible systems and F<%APPDATA%\Ethereal\preferences> (or, if
|
|
|
|
|
%APPDATA% isn't defined,
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\preferences>) on
|
2001-10-23 08:15:11 +00:00
|
|
|
|
Windows systems, contain system-wide and personal preference settings,
|
|
|
|
|
respectively. The file contains preference settings of the form
|
|
|
|
|
I<prefname>B<:>I<value>, one per line, where I<prefname> is the name of
|
|
|
|
|
the preference (which is the same name that would appear in the
|
|
|
|
|
preference file), and I<value> is the value to which it should be set;
|
|
|
|
|
white space is allowed between B<:> and I<value>. A preference setting
|
|
|
|
|
can be continued on subsequent lines by indenting the continuation lines
|
|
|
|
|
with white space. A B<#> character starts a comment that runs to the
|
|
|
|
|
end of the line.
|
2000-07-09 04:09:09 +00:00
|
|
|
|
|
|
|
|
|
The system-wide preference file is read first, if it exists, overriding
|
|
|
|
|
B<Ethereal>'s default values; the personal preferences file is then
|
|
|
|
|
read, if it exists, overriding default values and values read from the
|
|
|
|
|
system-wide preference file.
|
|
|
|
|
|
|
|
|
|
Note that whenever the preferences are saved by using the I<Save> button
|
2001-10-23 08:15:11 +00:00
|
|
|
|
in the I<Edit:Preferences> dialog box, your personal preferences file
|
2000-07-09 04:09:09 +00:00
|
|
|
|
will be overwritten with the new settings, destroying any comments that
|
|
|
|
|
were in the file.
|
|
|
|
|
|
2003-08-07 00:56:30 +00:00
|
|
|
|
The disabled protocols file, which is F<$HOME/.ethereal/disabled_protos>
|
|
|
|
|
on UNIX-compatible systems and F<%APPDATA%\Ethereal\disabled_protos>
|
|
|
|
|
(or, if %APPDATA% isn't defined, F<%USERPROFILE%\Application
|
|
|
|
|
Data\Ethereal\disabled_protos>) on Windows systems, contain a list of
|
|
|
|
|
protocols that have been disabled, so that their dissectors are never
|
|
|
|
|
called. The file contains protocol names, one per line, where the
|
|
|
|
|
protocol name is the same name that would be used in a display filter
|
|
|
|
|
for the protocol. A B<#> character starts a comment that runs to the
|
|
|
|
|
end of the line.
|
|
|
|
|
|
|
|
|
|
Note that whenever the disabled protocols list is saved by using the
|
|
|
|
|
I<Save> button in the I<Edit:Protocols> dialog box, your disabled
|
|
|
|
|
protocols file will be overwritten with the new settings, destroying any
|
|
|
|
|
comments that were in the file.
|
|
|
|
|
|
2001-10-21 19:54:49 +00:00
|
|
|
|
The F<ethers> file, which is found in the F</etc> directory on
|
|
|
|
|
UNIX-compatible systems, and in the main installation directory (for
|
|
|
|
|
example, F<C:\Program Files\Ethereal>) on Windows systems, is consulted
|
|
|
|
|
to correlate 6-byte hardware addresses to names. If an address is not
|
2001-10-23 08:15:11 +00:00
|
|
|
|
found in the F<ethers> file, the F<$HOME/.ethereal/ethers> file on
|
2001-10-24 06:13:07 +00:00
|
|
|
|
UNIX-compatible systems, and the F<%APPDATA%\Ethereal\ethers> file (or, if
|
|
|
|
|
%APPDATA% isn't defined, the
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\ethers> file) on Windows
|
|
|
|
|
systems is consulted next. Each line contains one hardware
|
2001-10-23 08:15:11 +00:00
|
|
|
|
address and name, separated by whitespace. The digits of the hardware
|
|
|
|
|
address are separated by either a colon (:), a dash (-), or a period
|
|
|
|
|
(.). The following three lines are valid lines of an ethers file:
|
1999-11-21 16:32:23 +00:00
|
|
|
|
|
|
|
|
|
ff:ff:ff:ff:ff:ff Broadcast
|
|
|
|
|
c0-00-ff-ff-ff-ff TR_broadcast
|
|
|
|
|
00.00.00.00.00.00 Zero_broadcast
|
|
|
|
|
|
2001-10-11 01:21:50 +00:00
|
|
|
|
The F<manuf> file, which is installed in the F<etc> directory under the
|
|
|
|
|
main installation directory (for example, F</usr/local/etc>) on
|
|
|
|
|
UNIX-compatible systems, and in the main installation directory (for
|
2001-10-21 19:54:49 +00:00
|
|
|
|
example, F<C:\Program Files\Ethereal>) on Windows systems, matches the
|
2001-10-11 01:21:50 +00:00
|
|
|
|
3-byte vendor portion of a 6-byte hardware address with the
|
2002-09-09 19:53:38 +00:00
|
|
|
|
manufacturer's name; it can also contain well-known MAC addresses and
|
|
|
|
|
address ranges specified with a netmask. The format of the file is the
|
|
|
|
|
same as the F<ethers> file, except that entries of the form
|
|
|
|
|
|
|
|
|
|
00:00:0C Cisco
|
|
|
|
|
|
|
|
|
|
can be provided, with the 3-byte OUI and the name for a vendor, and
|
|
|
|
|
entries of the form
|
|
|
|
|
|
|
|
|
|
00-00-0C-07-AC/40 All-HSRP-routers
|
|
|
|
|
|
|
|
|
|
can be specified, with a MAC address and a mask indicating how many bits
|
|
|
|
|
of the address must match. Trailing zero bytes can be omitted from
|
|
|
|
|
address ranges. That entry, for example, will match addresses from
|
|
|
|
|
00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a
|
|
|
|
|
multiple of 8.
|
2001-10-21 19:54:49 +00:00
|
|
|
|
|
|
|
|
|
The F<ipxnets> file, which is found in the F</etc> directory on
|
|
|
|
|
UNIX-compatible systems, and in the main installation directory (for
|
|
|
|
|
example, F<C:\Program Files\Ethereal>) on Windows systems, correlates
|
|
|
|
|
4-byte IPX network numbers to names. If a network number is not found
|
2001-10-23 08:15:11 +00:00
|
|
|
|
in the F<ipxnets> file, the F<$HOME/.ethereal/ipxnets> file on
|
2001-10-24 06:13:07 +00:00
|
|
|
|
UNIX-compatible systems, and the F<%APPDATA%\Ethereal\ipxnets> file (or,
|
|
|
|
|
if %APPDATA% isn't defined, the
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\ipxnets> file)
|
2001-10-23 08:15:11 +00:00
|
|
|
|
on Windows systems, is consulted next. The format is the same as the
|
|
|
|
|
F<ethers> file, except that each address if four bytes instead of six.
|
|
|
|
|
Additionally, the address can be represented a single hexadecimal
|
|
|
|
|
number, as is more common in the IPX world, rather than four hex octets.
|
|
|
|
|
For example, these four lines are valid lines of an ipxnets file.
|
1999-11-21 16:32:23 +00:00
|
|
|
|
|
|
|
|
|
C0.A8.2C.00 HR
|
|
|
|
|
c0-a8-1c-00 CEO
|
|
|
|
|
00:00:BE:EF IT_Server1
|
|
|
|
|
110f FileServer3
|
1999-11-20 03:39:27 +00:00
|
|
|
|
|
2003-08-27 22:55:51 +00:00
|
|
|
|
The global color filters file, F<colorfilters>, which is installed in
|
|
|
|
|
the F<etc> directory under the main installation directory (for example,
|
|
|
|
|
F</usr/local/etc>) on UNIX-compatible systems, and in the main
|
|
|
|
|
installation directory (for example, F<C:\Program Files\Ethereal>) on
|
|
|
|
|
Windows systems, and the personal color filters file, which is
|
|
|
|
|
F<$HOME/.ethereal/colorfilters> on UNIX-compatible systems and
|
|
|
|
|
F<%APPDATA%\Ethereal\colorfilters> (or, if %APPDATA% isn't defined,
|
|
|
|
|
F<%USERPROFILE%\Application Data\Ethereal\color filters>) on Windows
|
|
|
|
|
systems, contain system-wide and personal color filters,
|
|
|
|
|
respectively.
|
|
|
|
|
|
1998-09-16 02:39:15 +00:00
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
|
2003-10-01 14:59:41 +00:00
|
|
|
|
I<ethereal-filter(4)> I<tethereal(1)>, I<editcap(1)>, I<tcpdump(8)>, I<pcap(3)>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=head1 NOTES
|
|
|
|
|
|
1999-12-16 08:05:46 +00:00
|
|
|
|
The latest version of B<Ethereal> can be found at
|
2000-10-09 03:10:01 +00:00
|
|
|
|
B<http://www.ethereal.com>.
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
=head1 AUTHORS
|
|
|
|
|
|
|
|
|
|
Original Author
|
|
|
|
|
-------- ------
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Gerald Combs <gerald[AT]ethereal.com>
|
1998-09-16 02:39:15 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Contributors
|
|
|
|
|
------------
|
2001-11-13 23:55:44 +00:00
|
|
|
|
Gilbert Ramirez <gram[AT]alumni.rice.edu>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Hannes R. Boehm <hannes[AT]boehm.org>
|
2002-11-23 03:25:06 +00:00
|
|
|
|
Mike Hall <mike [AT] hallzone.net>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Bobo Rajec <bobo[AT]bsp-consulting.sk>
|
2003-01-26 19:35:31 +00:00
|
|
|
|
Laurent Deniel <laurent.deniel[AT]free.fr>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Don Lafontaine <lafont02[AT]cn.ca>
|
|
|
|
|
Guy Harris <guy[AT]alum.mit.edu>
|
|
|
|
|
Simon Wilkinson <sxw[AT]dcs.ed.ac.uk>
|
|
|
|
|
Joerg Mayer <jmayer[AT]loplof.de>
|
|
|
|
|
Martin Maciaszek <fastjack[AT]i-s-o.net>
|
|
|
|
|
Didier Jorand <Didier.Jorand[AT]alcatel.fr>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Jun-ichiro itojun Hagino <itojun[AT]itojun.org>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Richard Sharpe <sharpe[AT]ns.aus.com>
|
|
|
|
|
John McDermott <jjm[AT]jkintl.com>
|
|
|
|
|
Jeff Jahr <jjahr[AT]shastanets.com>
|
|
|
|
|
Brad Robel-Forrest <bradr[AT]watchguard.com>
|
|
|
|
|
Ashok Narayanan <ashokn[AT]cisco.com>
|
|
|
|
|
Aaron Hillegass <aaron[AT]classmax.com>
|
|
|
|
|
Jason Lango <jal[AT]netapp.com>
|
|
|
|
|
Johan Feyaerts <Johan.Feyaerts[AT]siemens.atea.be>
|
2002-09-01 14:30:34 +00:00
|
|
|
|
Olivier Abad <oabad[AT]noos.fr>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Thierry Andry <Thierry.Andry[AT]advalvas.be>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Jeff Foster <jfoste[AT]woodward.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Peter Torvals <petertv[AT]xoommail.com>
|
|
|
|
|
Christophe Tronche <ch.tronche[AT]computer.org>
|
|
|
|
|
Nathan Neulinger <nneul[AT]umr.edu>
|
|
|
|
|
Tomislav Vujec <tvujec[AT]carnet.hr>
|
|
|
|
|
Kojak <kojak[AT]bigwig.net>
|
|
|
|
|
Uwe Girlich <Uwe.Girlich[AT]philosys.de>
|
|
|
|
|
Warren Young <tangent[AT]mail.com>
|
|
|
|
|
Heikki Vatiainen <hessu[AT]cs.tut.fi>
|
|
|
|
|
Greg Hankins <gregh[AT]twoguys.org>
|
|
|
|
|
Jerry Talkington <jerryt[AT]netapp.com>
|
|
|
|
|
Dave Chapeskie <dchapes[AT]ddm.on.ca>
|
|
|
|
|
James Coe <jammer[AT]cin.net>
|
|
|
|
|
Bert Driehuis <driehuis[AT]playbeing.org>
|
|
|
|
|
Stuart Stanley <stuarts[AT]mxmail.net>
|
|
|
|
|
John Thomes <john[AT]ensemblecom.com>
|
|
|
|
|
Laurent Cazalet <laurent.cazalet[AT]mailclub.net>
|
|
|
|
|
Thomas Parvais <thomas.parvais[AT]advalvas.be>
|
|
|
|
|
Gerrit Gehnen <G.Gehnen[AT]atrie.de>
|
|
|
|
|
Craig Newell <craign[AT]cheque.uq.edu.au>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Ed Meaney <emeaney[AT]cisco.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Dietmar Petras <DPetras[AT]ELSA.de>
|
|
|
|
|
Fred Reimer <fwr[AT]ga.prestige.net>
|
|
|
|
|
Florian Lohoff <flo[AT]rfc822.org>
|
|
|
|
|
Jochen Friedrich <jochen+ethereal[AT]scram.de>
|
|
|
|
|
Paul Welchinski <paul.welchinski[AT]telusplanet.net>
|
|
|
|
|
Doug Nazar <nazard[AT]dragoninc.on.ca>
|
|
|
|
|
Andreas Sikkema <andreas.sikkema[AT]philips.com>
|
|
|
|
|
Mark Muhlestein <mmm[AT]netapp.com>
|
|
|
|
|
Graham Bloice <graham.bloice[AT]trihedral.com>
|
|
|
|
|
Ralf Schneider <ralf.schneider[AT]alcatel.se>
|
|
|
|
|
Yaniv Kaul <ykaul[AT]netvision.net.il>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Paul Ionescu <paul[AT]acorp.ro>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Mark Burton <markb[AT]ordern.com>
|
|
|
|
|
Stefan Raab <sraab[AT]cisco.com>
|
|
|
|
|
Mark Clayton <clayton[AT]shore.net>
|
|
|
|
|
Michael Rozhavsky <mike[AT]tochna.technion.ac.il>
|
|
|
|
|
Dug Song <dugsong[AT]monkey.org>
|
2002-12-02 20:08:45 +00:00
|
|
|
|
Michael Tuexen <Michael.Tuexen [AT] siemens.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Bruce Korb <bkorb[AT]sco.com>
|
|
|
|
|
Jose Pedro Oliveira <jpo[AT]di.uminho.pt>
|
|
|
|
|
David Frascone <dave[AT]frascone.com>
|
|
|
|
|
Peter Kjellerstedt <pkj[AT]axis.com>
|
|
|
|
|
Phil Techau <phil_t[AT]altavista.net>
|
|
|
|
|
Wes Hardaker <wjhardaker[AT]ucdavis.edu>
|
|
|
|
|
Robert Tsai <rtsai[AT]netapp.com>
|
|
|
|
|
Craig Metz <cmetz[AT]inner.net>
|
|
|
|
|
Per Flock <per.flock[AT]axis.com>
|
|
|
|
|
Jack Keane <jkeane[AT]OpenReach.com>
|
|
|
|
|
Brian Wellington <bwelling[AT]xbill.org>
|
|
|
|
|
Santeri Paavolainen <santtu[AT]ssh.com>
|
|
|
|
|
Ulrich Kiermayr <uk[AT]ap.univie.ac.at>
|
|
|
|
|
Neil Hunter <neil.hunter[AT]energis-squared.com>
|
|
|
|
|
Ralf Holzer <ralf[AT]well.com>
|
2003-02-13 01:23:37 +00:00
|
|
|
|
Craig Rodrigues <rodrigc [AT] attbi.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Ed Warnicke <hagbard[AT]physics.rutgers.edu>
|
|
|
|
|
Johan Jorgensen <johan.jorgensen[AT]axis.com>
|
|
|
|
|
Frank Singleton <frank.singleton[AT]ericsson.com>
|
|
|
|
|
Kevin Shi <techishi[AT]ms22.hinet.net>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Mike Frisch <mfrisch[AT]isurfer.ca>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Burke Lau <burke_lau[AT]agilent.com>
|
2001-10-22 21:05:15 +00:00
|
|
|
|
Martti Kuparinen <martti.kuparinen[AT]iki.fi>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
David Hampton <dhampton[AT]mac.com>
|
|
|
|
|
Kent Engstr<74>m <kent[AT]unit.liu.se>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Ronnie Sahlberg <sahlberg[AT]optushome.com.au>
|
|
|
|
|
Borosa Tomislav <tomislav.borosa[AT]SIEMENS.HR>
|
|
|
|
|
Alexandre P. Ferreira <alexandref[AT]tcoip.com.br>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Simharajan Srishylam <Simharajan.Srishylam[AT]netapp.com>
|
|
|
|
|
Greg Kilfoyle <gregk[AT]redback.com>
|
|
|
|
|
James E. Flemer <jflemer[AT]acm.jhu.edu>
|
|
|
|
|
Peter Lei <peterlei[AT]cisco.com>
|
|
|
|
|
Thomas Gimpel <thomas.gimpel[AT]ferrari.de>
|
|
|
|
|
Albert Chin <china[AT]thewrittenword.com>
|
|
|
|
|
Charles Levert <charles[AT]comm.polymtl.ca>
|
|
|
|
|
Todd Sabin <tas[AT]webspan.net>
|
|
|
|
|
Eduardo P<>rez Ureta <eperez[AT]dei.inf.uc3m.es>
|
|
|
|
|
Martin Thomas <martin_a_thomas[AT]yahoo.com>
|
|
|
|
|
Hartmut Mueller <hartmut[AT]wendolene.ping.de>
|
|
|
|
|
Michal Melerowicz <Michal.Melerowicz[AT]nokia.com>
|
|
|
|
|
Hannes Gredler <hannes[AT]juniper.net>
|
|
|
|
|
Inoue <inoue[AT]ainet.or.jp>
|
2003-02-12 01:17:07 +00:00
|
|
|
|
Olivier Biot <Olivier.Biot[AT]siemens.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Patrick Wolfe <pjw[AT]zocalo.cellular.ameritech.com>
|
|
|
|
|
Martin Held <Martin.Held[AT]icn.siemens.de>
|
|
|
|
|
Riaan Swart <rswart[AT]cs.sun.ac.za>
|
|
|
|
|
Christian Lacunza <celacunza[AT]gmx.net>
|
|
|
|
|
Scott Renfro <scott[AT]renfro.org>
|
|
|
|
|
Juan Toledo <toledo[AT]users.sourceforge.net>
|
|
|
|
|
Jean-Christian Pennetier <jeanchristian.pennetier[AT]rd.francetelecom.fr>
|
|
|
|
|
Jian Yu <bgp4news[AT]yahoo.com>
|
|
|
|
|
Eran Mann <emann[AT]opticalaccess.com>
|
|
|
|
|
Andy Hood <ahood[AT]westpac.com.au>
|
|
|
|
|
Randy McEoin <rmceoin[AT]pe.net>
|
|
|
|
|
Edgar Iglesias <edgar.iglesias[AT]axis.com>
|
|
|
|
|
Martina Obermeier <Martina.Obermeier[AT]icn.siemens.de>
|
|
|
|
|
Javier Achirica <achirica[AT]ttd.net>
|
|
|
|
|
B. Johannessen <bob[AT]havoq.com>
|
|
|
|
|
Thierry Pelle <thierry.pelle[AT]rd.francetelecom.fr>
|
|
|
|
|
Francisco Javier Cabello <fjcabello[AT]vtools.es>
|
|
|
|
|
Laurent Rabret <laurent.rabret[AT]rd.francetelecom.fr>
|
|
|
|
|
nuf si <gnippiks[AT]yahoo.com>
|
|
|
|
|
Jeff Morriss <jeff.morriss[AT]ulticom.com>
|
|
|
|
|
Aamer Akhter <aakhter[AT]cisco.com>
|
|
|
|
|
Pekka Savola <pekkas[AT]netcore.fi>
|
|
|
|
|
David Eisner <cradle[AT]Glue.umd.edu>
|
|
|
|
|
Steve Dickson <steved[AT]talarian.com>
|
|
|
|
|
Markus Seehofer <mseehofe[AT]nt.hirschmann.de>
|
2001-08-04 19:57:30 +00:00
|
|
|
|
Lee Berger <lberger[AT]roy.org>
|
2001-08-05 10:09:40 +00:00
|
|
|
|
Motonori Shindo <mshindo[AT]mshindo.net>
|
2001-08-21 18:56:15 +00:00
|
|
|
|
Terje Krogdahl <tekr[AT]nextra.com>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Jean-Francois Mule <jfm[AT]cablelabs.com>
|
2001-09-04 01:01:48 +00:00
|
|
|
|
Thomas Wittwer <thomas.wittwer[AT]iclip.ch>
|
2001-12-04 07:32:05 +00:00
|
|
|
|
Matthias Nyffenegger <matthias.nyffenegger[AT]iclip.ch>
|
2001-09-05 19:53:42 +00:00
|
|
|
|
Palle Lyckegaard <Palle[AT]lyckegaard.dk>
|
2001-09-11 08:14:39 +00:00
|
|
|
|
Nicolas Balkota <balkota[AT]mac.com>
|
2001-09-11 14:36:33 +00:00
|
|
|
|
Tom Uijldert <Tom.Uijldert[AT]cmg.nl>
|
2003-01-28 05:25:18 +00:00
|
|
|
|
Akira Endoh <endoh[AT]netmarks.co.jp>
|
2001-09-28 18:50:19 +00:00
|
|
|
|
Graeme Hewson <graeme.hewson[AT]oracle.com>
|
2001-10-01 08:51:31 +00:00
|
|
|
|
Pasi Eronen <pasi.eronen[at]nixu.com>
|
2001-10-07 08:37:29 +00:00
|
|
|
|
Georg von Zezschwitz <gvz[AT]2scale.net>
|
2001-10-15 03:54:05 +00:00
|
|
|
|
Steffen Weinreich <steve[AT]weinreich.org>
|
2003-01-17 23:54:19 +00:00
|
|
|
|
Marc Milgram <ethereal[AT]mmilgram.NOSPAMmail.net>
|
2001-10-21 17:38:43 +00:00
|
|
|
|
Gordon McKinney <gordon[AT]night-ray.com>
|
|
|
|
|
Tim Farley <tfarley[AT]iss.net>
|
|
|
|
|
Daniel Thompson <daniel.thompson[AT]st.com>
|
|
|
|
|
Chris Jepeway <thai-dragon[AT]eleven29.com>
|
2001-10-23 04:11:58 +00:00
|
|
|
|
Pavel Novotny <Pavel.Novotny[AT]icn.siemens.de>
|
2001-10-30 10:11:00 +00:00
|
|
|
|
Shinsuke Suzuki <suz[AT]kame.net>
|
2001-11-03 01:56:11 +00:00
|
|
|
|
Andrew C. Feren <aferen[AT]cetacean.com>
|
2002-11-25 19:07:53 +00:00
|
|
|
|
Tomas Kukosa <tomas.kukosa [AT] siemens.com>
|
2001-11-24 10:00:50 +00:00
|
|
|
|
Andreas Stockmeier <a.stockmeier[AT]avm.de>
|
2001-11-06 20:30:40 +00:00
|
|
|
|
Pekka Nikander <pekka.nikander[AT]nomadiclab.com>
|
2001-11-07 20:26:38 +00:00
|
|
|
|
Hamish Moffatt <hamish[AT]cloud.net.au>
|
2001-11-09 08:16:25 +00:00
|
|
|
|
Kazushi Sugyo <k-sugyou[AT]nwsl.mesh.ad.jp>
|
2001-11-12 08:58:45 +00:00
|
|
|
|
Tim Potter <tpot[AT]samba.org>
|
2001-11-27 00:50:47 +00:00
|
|
|
|
Raghu Angadi <rangadi[AT]inktomi.com>
|
2001-11-28 06:44:44 +00:00
|
|
|
|
Taisuke Sasaki <sasaki[AT]soft.net.fujitsu.co.jp>
|
2001-11-28 07:11:11 +00:00
|
|
|
|
Tim Newsham <newsham[AT]lava.net>
|
2001-12-04 22:28:19 +00:00
|
|
|
|
Tom Nisbet <Tnisbet[AT]VisualNetworks.com>
|
2001-12-08 01:45:36 +00:00
|
|
|
|
Darren New <dnew[AT]san.rr.com>
|
2001-12-08 09:27:51 +00:00
|
|
|
|
Pavel Mores <pvl[AT]uh.cz>
|
2001-12-15 20:40:19 +00:00
|
|
|
|
Bernd Becker <bb[AT]bernd-becker.de>
|
2001-12-16 22:30:11 +00:00
|
|
|
|
Heinz Prantner <Heinz.Prantner[AT]radisys.com>
|
2001-12-17 22:22:42 +00:00
|
|
|
|
Irfan Khan <ikhan[AT]qualcomm.com>
|
2002-01-03 20:30:33 +00:00
|
|
|
|
Jayaram V.R <vjayar[AT]cisco.com>
|
2002-01-10 01:28:45 +00:00
|
|
|
|
Dinesh Dutt <ddutt[AT]cisco.com>
|
2002-01-10 22:21:14 +00:00
|
|
|
|
Nagarjuna Venna <nvenna[AT]Brixnet.com>
|
2002-01-11 08:21:02 +00:00
|
|
|
|
Jirka Novak <j.novak[AT]netsystem.cz>
|
2002-01-21 22:15:18 +00:00
|
|
|
|
Ricardo Barroetave<76>a <rbarroetavena[AT]veufort.com>
|
2002-01-21 23:45:58 +00:00
|
|
|
|
Alan Harrison <alanharrison[AT]mail.com>
|
2002-01-29 08:44:53 +00:00
|
|
|
|
Mike Frantzen <frantzen[AT]w4g.org>
|
2002-02-02 03:42:18 +00:00
|
|
|
|
Charlie Duke <cduke[AT]fvc.com>
|
2002-02-02 12:04:24 +00:00
|
|
|
|
Alfred Arnold <Alfred.Arnold[AT]elsa.de>
|
2002-02-22 07:23:25 +00:00
|
|
|
|
Dermot Bradley <dermot.bradley[AT]openwave.com>
|
2002-02-22 09:52:01 +00:00
|
|
|
|
Adam Sulmicki <adam[AT]cfar.umd.edu>
|
2002-04-28 00:48:02 +00:00
|
|
|
|
Kari Tiirikainen <kari.tiirikainen[AT]nokia.com>
|
2002-02-23 02:16:12 +00:00
|
|
|
|
John Mackenzie <John.A.Mackenzie[AT]t-online.de>
|
2002-02-24 01:26:45 +00:00
|
|
|
|
Peter Valchev <pvalchev[AT]openbsd.org>
|
2002-02-27 10:03:10 +00:00
|
|
|
|
Alex Ruzin <alexr[AT]nbase.co.il>
|
2002-03-09 22:41:51 +00:00
|
|
|
|
Jouni Malinen <jkmaline[AT]cc.hut.fi>
|
2002-03-18 00:45:11 +00:00
|
|
|
|
Paul E. Erkkila <pee[AT]erkkila.org>
|
2002-03-22 02:38:54 +00:00
|
|
|
|
Jakob Schlyter <jakob[AT]crt.se>
|
|
|
|
|
Jim Sienicki <sienicki[AT]issanni.com>
|
2002-03-22 10:03:36 +00:00
|
|
|
|
Steven French <sfrench[AT]us.ibm.com>
|
2002-03-22 23:42:27 +00:00
|
|
|
|
Diana Eichert <deicher[AT]sandia.gov>
|
2002-04-01 21:12:31 +00:00
|
|
|
|
Blair Cooper <blair[AT]teamon.com>
|
2002-04-01 22:00:00 +00:00
|
|
|
|
Kikuchi Ayamura <ayamura[AT]ayamura.org>
|
2002-04-12 01:18:47 +00:00
|
|
|
|
Didier Gautheron <dgautheron[AT]magic.fr>
|
2002-04-18 20:19:10 +00:00
|
|
|
|
Phil Williams <csypbw[AT]comp.leeds.ac.uk>
|
2002-04-22 07:41:33 +00:00
|
|
|
|
Kevin Humphries <khumphries[AT]networld.com>
|
2002-04-25 23:35:52 +00:00
|
|
|
|
Erik Nordstr<74>m <erik.nordstrom[AT]it.uu.se>
|
2002-04-29 22:43:23 +00:00
|
|
|
|
Devin Heitmueller <dheitmueller[AT]netilla.com>
|
2002-05-07 18:52:27 +00:00
|
|
|
|
Chenjiang Hu <chu[AT]chiaro.com>
|
2002-05-08 08:13:08 +00:00
|
|
|
|
Kan Sasaki <sasaki[AT]fcc.ad.jp>
|
2002-05-08 20:29:47 +00:00
|
|
|
|
Stefan Wenk <stefan.wenk[AT]gmx.at>
|
2002-05-14 10:32:12 +00:00
|
|
|
|
Ruud Linders <ruud[AT]lucent.com>
|
2002-05-15 19:37:26 +00:00
|
|
|
|
Andrew Esh <Andrew.Esh[AT]tricord.com>
|
2002-05-15 21:50:27 +00:00
|
|
|
|
Greg Morris <GMORRIS[AT]novell.com>
|
2002-05-21 21:55:47 +00:00
|
|
|
|
Dirk Steinberg <dws[AT]dirksteinberg.de>
|
2002-05-27 20:33:25 +00:00
|
|
|
|
Kari Heikkila <kari.o.heikkila[AT]nokia.com>
|
2002-05-29 03:07:02 +00:00
|
|
|
|
Olivier Dreux <Olivier.Dreux[AT]alcatel.fr>
|
2002-05-29 18:52:28 +00:00
|
|
|
|
Michael Stiller <ms[AT]2scale.net>
|
2002-05-29 21:32:23 +00:00
|
|
|
|
Antti Tuominen <ajtuomin[AT]tml.hut.fi>
|
2002-05-29 22:52:55 +00:00
|
|
|
|
Martin Gignac <lmcgign[AT]mobilitylab.net>
|
2002-06-09 01:03:19 +00:00
|
|
|
|
John Wells <wells[AT]ieee.org>
|
2002-06-13 06:43:46 +00:00
|
|
|
|
Loic Tortay <tortay[AT]cc.in2p3.fr>
|
2002-06-13 07:18:49 +00:00
|
|
|
|
Steve Housley <Steve_Housley[AT]eur.3com.com>
|
2002-06-13 07:32:34 +00:00
|
|
|
|
Peter Hawkins <peter[AT]hawkins.emu.id.au>
|
2002-06-13 08:48:44 +00:00
|
|
|
|
Bill Fumerola <billf[AT]FreeBSD.org>
|
2002-06-16 00:53:20 +00:00
|
|
|
|
Chris Waters <chris[AT]waters.co.nz>
|
2002-06-18 08:38:19 +00:00
|
|
|
|
Solomon Peachy <pizza[AT]shaftnet.org>
|
2002-06-22 01:30:54 +00:00
|
|
|
|
Jaime Fournier <jafour1[AT]yahoo.com>
|
2002-06-25 20:31:22 +00:00
|
|
|
|
Markus Steinmann <ms[AT]seh.de>
|
2002-06-26 01:24:43 +00:00
|
|
|
|
Tsutomu Mieno <iitom[AT]utouto.com>
|
2002-08-18 19:59:40 +00:00
|
|
|
|
Yasuhiro Shirasaki <yasuhiro[AT]gnome.gr.jp>
|
2003-05-28 14:52:53 +00:00
|
|
|
|
Anand V. Narwani <anand[AT]narwani.org>
|
2002-07-06 20:40:50 +00:00
|
|
|
|
Christopher K. St. John <cks[AT]distributopia.com>
|
|
|
|
|
Nix <nix[AT]esperi.demon.co.uk>
|
2002-07-07 21:52:51 +00:00
|
|
|
|
Liviu Daia <Liviu.Daia[AT]imar.ro>
|
2002-07-19 09:33:17 +00:00
|
|
|
|
Richard Urwin <rurwin[AT]schenck.co.uk>
|
2002-07-20 23:14:39 +00:00
|
|
|
|
Prabhakar Krishnan <Prabhakar.Krishnan[AT]netapp.com>
|
2002-07-31 21:22:39 +00:00
|
|
|
|
Jim McDonough <jmcd[AT]us.ibm.com>
|
2002-08-04 08:44:31 +00:00
|
|
|
|
Sergei Shokhor <sshokhor[AT]uroam.com>
|
|
|
|
|
Hidetaka Ogawa <ogawa[AT]bs2.qnes.nec.co.jp>
|
2002-08-05 08:37:47 +00:00
|
|
|
|
Jan Kratochvil <short[AT]ucw.cz>
|
2002-08-08 09:28:11 +00:00
|
|
|
|
Alfred Koebler <ak[AT]icon-sult.de>
|
2002-08-18 19:59:40 +00:00
|
|
|
|
Vassilii Khachaturov <Vassilii.Khachaturov[AT]comverse.com>
|
|
|
|
|
Bill Studenmund <wrstuden[AT]wasabisystems.com>
|
2002-08-19 21:34:35 +00:00
|
|
|
|
Brian Bruns <camber[AT]ais.org>
|
2002-08-27 19:16:23 +00:00
|
|
|
|
Flavio Poletti <flavio[AT]polettix.it>
|
2002-08-24 10:12:45 +00:00
|
|
|
|
Marcus Haebler <haeblerm[AT]yahoo.com>
|
2002-08-26 19:09:02 +00:00
|
|
|
|
Ulf Lamping <ulf.lamping[AT]web.de>
|
2002-09-04 20:23:55 +00:00
|
|
|
|
Matthew Smart <smart[AT]monkey.org>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Luke Howard <lukeh[AT]au.padl.com>
|
2002-09-16 17:49:20 +00:00
|
|
|
|
PC Drew <drewpc[AT]ibsncentral.com>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Renzo Tomas <renzo.toma [AT] xs4all.nl>
|
2002-09-25 00:52:18 +00:00
|
|
|
|
Clive A. Stubbings <eth[AT]vjet.demon.co.uk>
|
2002-10-08 19:19:00 +00:00
|
|
|
|
Steve Langasek <vorlon [AT] netexpress.net>
|
|
|
|
|
Brad Hards <bhards[AT]bigpond.net.au>
|
|
|
|
|
cjs 2895 <cjs2895[AT]hotmail.com>
|
2002-10-08 19:26:37 +00:00
|
|
|
|
Lutz Jaenicke <Lutz.Jaenicke [AT] aet.TU-Cottbus.DE>
|
2002-10-08 19:35:10 +00:00
|
|
|
|
Senthil Kumar Nagappan <sknagappan [AT] yahoo.com>
|
2002-10-15 05:38:01 +00:00
|
|
|
|
Jason House <jhouse [AT] mitre.org>
|
2002-10-18 21:00:01 +00:00
|
|
|
|
Peter Fales <psfales [AT] lucent.com>
|
2002-11-01 05:30:48 +00:00
|
|
|
|
Fritz Budiyanto <fritzb88 [AT] yahoo.com>
|
2002-11-03 20:24:12 +00:00
|
|
|
|
Jean-Baptiste Marchand <Jean-Baptiste.Marchand [AT] hsc.fr>
|
2002-11-06 22:59:23 +00:00
|
|
|
|
Andreas Trauer <andreas.trauer [AT] siemens.com>
|
2002-11-12 21:37:35 +00:00
|
|
|
|
Ronald Henderson <Ronald.Henderson [AT] CognicaseUSA.com>
|
2002-11-13 21:45:59 +00:00
|
|
|
|
Brian Ginsbach <ginsbach [AT] cray.com>
|
2002-11-16 08:55:13 +00:00
|
|
|
|
Dave Richards <d_m_richards [AT] attbi.com>
|
2002-11-18 15:49:07 +00:00
|
|
|
|
Martin Regner <martin.regner [AT] chello.se>
|
2002-11-25 19:20:44 +00:00
|
|
|
|
Jason Greene <jason [AT] inetgurus.net>
|
2002-11-28 20:28:30 +00:00
|
|
|
|
Marco Molteni <mmolteni [AT] cisco.com>
|
2002-12-17 04:05:25 +00:00
|
|
|
|
James Harris <jharris [AT] fourhorsemen.org>
|
2002-12-29 22:40:10 +00:00
|
|
|
|
rmkml <rmkml [AT] wanadoo.fr>
|
2003-09-11 00:08:14 +00:00
|
|
|
|
Anders Broman <anders.broman [AT] ericsson.com>
|
2003-01-14 23:53:40 +00:00
|
|
|
|
Christian Falckenberg <christian.falckenberg [AT] nortelnetworks.com>
|
2003-01-19 21:29:10 +00:00
|
|
|
|
Huagang Xie <xie [AT] lids.org>
|
2003-01-21 21:47:36 +00:00
|
|
|
|
cjs 2895 <cjs2895 [AT] hotmail.com>
|
2003-01-31 18:45:06 +00:00
|
|
|
|
Pasi Kovanen <Pasi.Kovanen [AT] tahoenetworks.fi>
|
2003-02-04 20:17:01 +00:00
|
|
|
|
Teemu Rinta-aho <teemu.rinta-aho [AT] nomadiclab.com>
|
2003-02-18 21:29:53 +00:00
|
|
|
|
Martijn Schipper <martijn.schipper [AT] intersil.com>
|
2003-03-01 00:09:03 +00:00
|
|
|
|
Wayne Parrott <wayne_p [AT] pacific.net.au>
|
2003-06-13 22:56:28 +00:00
|
|
|
|
Laurent Meyer <laurent.meyer6 [AT] wanadoo.fr>
|
2003-03-08 05:37:32 +00:00
|
|
|
|
Lars Roland <Lars.Roland [AT] gmx.net>
|
|
|
|
|
Miha Jemec <m.jemec [AT] iskratel.si>
|
|
|
|
|
Markus Friedl <markus [AT] openbsd.org>
|
2003-04-06 22:41:34 +00:00
|
|
|
|
Todd Montgomery <tmontgom [AT] tibco.com>
|
|
|
|
|
emre <emre [AT] flash.net>
|
2003-04-16 06:57:38 +00:00
|
|
|
|
Stephen Shelley <steve.shelley [AT] attbi.com>
|
2003-04-22 20:35:49 +00:00
|
|
|
|
Erwin Rol <erwin [AT] muffin.org>
|
2003-04-23 00:24:38 +00:00
|
|
|
|
Duncan Laurie <duncan [AT] sun.com>
|
2003-05-15 22:11:15 +00:00
|
|
|
|
Tony Schene <schene [AT] pcisys.net>
|
2003-04-27 00:41:52 +00:00
|
|
|
|
Matthijs Melchior <mmelchior [AT] xs4all.nl>
|
2003-04-29 02:55:14 +00:00
|
|
|
|
Garth Bushell <gbushell [AT] elipsan.com>
|
2003-05-05 01:01:36 +00:00
|
|
|
|
Mark C. Brown <mbrown [AT] nosila.net>
|
2003-05-15 07:14:46 +00:00
|
|
|
|
Can Erkin Acar <canacar [AT] eee.metu.edu.tr>
|
2003-05-22 20:33:04 +00:00
|
|
|
|
Martin Warnes <martin.warnes [AT] ntlworld.com>
|
|
|
|
|
J Bruce Fields <bfields [AT] fieldses.org>
|
2003-05-30 03:11:45 +00:00
|
|
|
|
tz <tz1 [AT] mac.com>
|
2003-06-04 00:14:47 +00:00
|
|
|
|
Jeff Liu <jqliu [AT] broadcom.com>
|
|
|
|
|
Niels Koot <Niels.Koot [AT] logicacmg.com>
|
2003-06-05 04:47:58 +00:00
|
|
|
|
Lionel Ains <lains [AT] gmx.net>
|
2003-06-11 09:02:19 +00:00
|
|
|
|
Joakim Wiberg <jow [AT] hms-networks.com>
|
2003-06-13 22:31:11 +00:00
|
|
|
|
Jeff Rizzo <riz [AT] boogers.sf.ca.us>
|
2003-07-01 08:00:06 +00:00
|
|
|
|
Christoph Wiest <ch.wiest [AT] tesionmail.de>
|
2003-07-16 21:13:49 +00:00
|
|
|
|
Xuan Zhang <xz [AT] aemail4u.com>
|
2003-07-29 19:42:01 +00:00
|
|
|
|
Thierry Martin <thierry.martin [AT] accellent-group.com>
|
2003-08-07 00:41:28 +00:00
|
|
|
|
Oleg Terletsky <oleg.terletsky [AT] comverse.com>
|
|
|
|
|
Michael Lum <mlum [AT] telostech.com>
|
2003-08-17 00:54:25 +00:00
|
|
|
|
Shiang-Ming Huang <smhuang [AT] pcs.csie.nctu.edu.tw>
|
2003-08-18 18:20:11 +00:00
|
|
|
|
Tony Lindstrom <tony.lindstrom [AT] ericsson.com>
|
2003-08-25 21:48:44 +00:00
|
|
|
|
Niklas Ogren <niklas.ogren [AT] 71.se>
|
2003-08-26 07:07:41 +00:00
|
|
|
|
Jesper Peterson <jesper [AT] endace.com>
|
2003-08-28 00:11:32 +00:00
|
|
|
|
Giles Scott <gscott2 [AT] nortelnetworks.com>
|
2003-09-02 22:10:32 +00:00
|
|
|
|
Vincent Jardin <vincent.jardin [AT] 6wind.com>
|
|
|
|
|
Jean-Michel Fayard <jean-michel.fayard [AT] moufrei.de>
|
2003-09-03 22:26:38 +00:00
|
|
|
|
Josef Korelus <jkor [AT] quick.cz>
|
2003-09-06 08:30:26 +00:00
|
|
|
|
Brian K. Teravskis <Brian_Teravskis [AT] Cargill.com>
|
2003-09-08 21:44:42 +00:00
|
|
|
|
Nathan Jennings <njen [AT] bellsouth.net>
|
2003-09-15 18:40:53 +00:00
|
|
|
|
Hans Viens <hviens [AT] mediatrix.com>
|
2003-09-19 04:16:23 +00:00
|
|
|
|
Kevin A. Noll <knoll [AT] poss.com>
|
2003-09-20 09:41:48 +00:00
|
|
|
|
Emanuele Caratti <wiz [AT] libero.it>
|
2003-09-23 18:40:54 +00:00
|
|
|
|
Graeme Reid <graeme.reid [AT] norwoodsystems.com>
|
2003-09-24 07:48:12 +00:00
|
|
|
|
Lars Ruoff <lars.ruoff [AT] sxb.bsf.alcatel.fr>
|
2003-10-02 06:13:29 +00:00
|
|
|
|
Samuel Qu <samuel.qu [AT] utstar.com>
|
2003-10-27 09:17:21 +00:00
|
|
|
|
Baktha Muralitharan <muralidb [AT] cisco.com>
|
|
|
|
|
Lo<4C>c Minier <lool [AT] dooz.org>
|
2003-10-30 03:11:03 +00:00
|
|
|
|
Marcel Holtmann <marcel [AT] holtmann.org>
|
2003-10-31 00:43:21 +00:00
|
|
|
|
Scott Emberley <scotte [AT] netinst.com>
|
2003-11-01 02:30:18 +00:00
|
|
|
|
Brian Fundakowski Feldman <bfeldman [AT] fla.fujitsu.com>
|
2003-11-11 08:29:34 +00:00
|
|
|
|
Yuriy Sidelnikov <ysidelnikov [AT] hotmail.com>
|
2003-11-12 20:44:36 +00:00
|
|
|
|
Matthias Drochner <M.Drochner [AT] fz-juelich.de>
|
2003-03-04 19:50:23 +00:00
|
|
|
|
Pavel Roskin <proski [AT] gnu.org>
|
2003-02-27 02:07:57 +00:00
|
|
|
|
Georgi Guninski <guninski [AT] guninski.com>
|
2003-02-27 02:31:00 +00:00
|
|
|
|
Jason Copenhaver <jcopenha [AT] typedef.org>
|
2003-04-01 19:17:55 +00:00
|
|
|
|
Eric Perie <eric.perie [AT] colubris.com>
|
2003-04-22 20:35:49 +00:00
|
|
|
|
David Yon <yon [AT] tacticalsoftware.com>
|
2003-04-24 09:06:25 +00:00
|
|
|
|
Marcio Franco <franco.marcio [AT] rd.francetelecom.fr>
|
2003-04-30 18:55:32 +00:00
|
|
|
|
Kaloian Stoilov <kalkata [AT] yahoo.com>
|
2003-05-29 18:29:36 +00:00
|
|
|
|
Steven Lass <stevenlass [AT] mail.com>
|
2003-07-06 00:30:40 +00:00
|
|
|
|
Gregory Stark <gsstark [AT] mit.edu>
|
2003-07-07 22:55:55 +00:00
|
|
|
|
Darren Steele <steeley [AT] steeley.co.uk>
|
2003-07-11 06:46:00 +00:00
|
|
|
|
<smhuang [AT] pcs.csie.nctu.edu.tw>
|
2003-07-15 22:16:52 +00:00
|
|
|
|
Michael Kopp <michael.kopp [AT] isarnet.de>
|
2003-07-31 18:09:08 +00:00
|
|
|
|
Bernd Leibing <bernd.leibing [AT] kiz.uni-ulm.de>
|
2003-08-01 01:39:01 +00:00
|
|
|
|
Chris Heath <chris [AT] heathens.co.nz>
|
2003-08-18 18:40:10 +00:00
|
|
|
|
Gisle Vanem <giva [AT] bgnett.no>
|
2003-09-15 18:40:53 +00:00
|
|
|
|
Ritchie <ritchie [AT] tipsybottle.com>
|
2003-10-09 22:40:28 +00:00
|
|
|
|
Aki Immonen <aki.immonen [AT] golftalma.fi>
|
2003-10-14 23:20:17 +00:00
|
|
|
|
Ian Schorr <ischorr [AT] comcast.net>
|
2003-10-15 19:57:27 +00:00
|
|
|
|
David E. Weekly <david [AT] weekly.org>
|
2003-10-29 21:19:44 +00:00
|
|
|
|
Steve Ford <sford [AT] geeky-boy.com>
|
2003-11-04 18:38:53 +00:00
|
|
|
|
Masaki Chikama <masaki-c [AT] is.aist-nara.ac.jp>
|
2003-11-08 00:09:01 +00:00
|
|
|
|
Mohammad Hanif <mhanif [AT] nexthop.com>
|
2003-11-09 22:55:35 +00:00
|
|
|
|
Martin Mathieson <martin [AT] arca-technologies.com>
|
2001-07-23 18:21:32 +00:00
|
|
|
|
|
|
|
|
|
Alain Magloire <alainm[AT]rcsm.ece.mcgill.ca> was kind enough to give his
|
1998-09-16 02:39:15 +00:00
|
|
|
|
permission to use his version of snprintf.c.
|
|
|
|
|
|
2001-07-23 18:21:32 +00:00
|
|
|
|
Dan Lasley <dlasley[AT]promus.com> gave permission for his dumpit() hex-dump
|
1998-09-16 02:39:15 +00:00
|
|
|
|
routine to be used.
|
2001-07-23 18:21:32 +00:00
|
|
|
|
|
|
|
|
|
Mattia Cazzola <mattiac[AT]alinet.it> provided a patch to the hex dump
|
|
|
|
|
display routine.
|
|
|
|
|
|
|
|
|
|
We use the exception module from Kazlib, a C library written by
|
|
|
|
|
Kaz Kylheku <kaz[AT]ashi.footprints.net>. Thanks goes to him for his
|
|
|
|
|
well-written library. The Kazlib home page can be found at
|
|
|
|
|
http://users.footprints.net/~kaz/kazlib.html
|