aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorsahlberg <sahlberg@f5534014-38df-0310-8fa8-9805f1628bb7>2003-08-24 03:31:54 +0000
committersahlberg <sahlberg@f5534014-38df-0310-8fa8-9805f1628bb7>2003-08-24 03:31:54 +0000
commit68cfc48175d5407116e3e0bc57c884a55356a383 (patch)
tree8799fa7e8623c4d6388e6eb8c166567799c0198a /doc
parent37daec022e2307f1eef174fc3794aad7e46eeca8 (diff)
Update manpage for ethereal.
Update the talkers tap for tethereal (iousers) and change the command line to invoke the tethereal version from -z io,users, to -z talkers, to be the same as for ethereal. Sorry if it breaks some scripts but io,users was a very nonintuitive name for this option. talkers is not much better but at least a little bit more descriptive/intuitive. Anyone with a better name for this are welcome to provide a patch. The tethereal version is now agnostic to wether v4 or v6 are transporting UDP/TCP git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@8236 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'doc')
-rw-r--r--doc/ethereal.pod.template33
-rw-r--r--doc/tethereal.pod.template6
2 files changed, 36 insertions, 3 deletions
diff --git a/doc/ethereal.pod.template b/doc/ethereal.pod.template
index fe2651b2e3..b8ff1bffcb 100644
--- a/doc/ethereal.pod.template
+++ b/doc/ethereal.pod.template
@@ -379,6 +379,29 @@ on those calls that match that filter.
Example: use B<-z "mgcp,srt,ip.addr==1.2.3.4"> to only collect stats for
MGCP packets exchanged by the host at IP address 1.2.3.4 .
+B<-z> talkers,I<type>[,I<filter>]
+
+Create a table that lists all conversations that could be seen in the capture.
+I<type> specifies which type of conversation we want to generate the
+statistics for, currently the supported ones are
+ "eth" Ethernet
+ "ip" IP addresses
+ "tcp" TCP/IP socketpairs Both IPv4 and IPv6 are supported
+ "tr" TokenRing
+ "udp" UDP/IP socketpairs Both IPv4 and IPv6 are supported
+ "fc" Fibre Channel addresses
+
+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
+number of frames/bytes in each direction as well as total number of
+frames/bytes.
+By default table is sorted according to total number of frames.
+
+These tables can also be generated at runtime by selecting the appropriate
+conversation type from the menu "Tools/Statistics/EndpointTalkers/"
+
=back
=head1 INTERFACE
@@ -792,6 +815,16 @@ the calculation. The stats will only be calculated
on those calls matching that filter.
+=item Tools:Statistics:Endpoint Talkers
+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.
+
+By default the list is sorted according to the number of frames but by clicking on the column header it is possible to resort the list in ascending or descending order by any column.
+
+These statistics windows can also be invoked from the ethereal command line using the -z talkers, argument.
+
+
=item Tools:Statistics:Traffic:IO-Stat
Open a window where up to 5 graphs in different colors can be displayed
diff --git a/doc/tethereal.pod.template b/doc/tethereal.pod.template
index cef55deb78..6775fa2457 100644
--- a/doc/tethereal.pod.template
+++ b/doc/tethereal.pod.template
@@ -445,16 +445,16 @@ time and average response time.
-B<-z> io,users,I<type>[,I<filter>]
+B<-z> talkers,I<type>[,I<filter>]
Create a table that lists all conversations that could be seen in the capture.
I<type> specifies which type of conversation we want to generate the
statistics for, currently the supported ones are
"eth" Ethernet
"ip" IP addresses
- "tcpip" TCP/IP socketpairs
+ "tcp" TCP/IP socketpairs Both IPv4 and IPv6 are supported
"tr" TokenRing
- "udpip" UDP/IP socketpairs
+ "udp" UDP/IP socketpairs Both IPv4 and IPv6 are supported
If the optional filter string is specified, only those packets that match the
filter will be used in the calculations.