diff options
author | Gerald Combs <gerald@wireshark.org> | 2018-02-25 17:50:01 -0800 |
---|---|---|
committer | Gerald Combs <gerald@wireshark.org> | 2018-02-26 02:05:17 +0000 |
commit | c1e5e6c92d7a2af922bbfd7e5b474baf122cf9d5 (patch) | |
tree | c9c4b4df952ecd59dbaf1fdf9db9a54c836a865a /docbook/wsug_src/WSUG_chapter_statistics.asciidoc | |
parent | 1585aa950ccfb3a564aa263de5f01c4ab01cc5f1 (diff) |
WSUG: Fixup some quotes and apostrophes.
Switch from AsciiDoc's smart quotes markup to the quotes themselves,
along with apostrophes.
Change-Id: I78930d6902e2691b6a2cb35ed5bae6fef4bb7257
Reviewed-on: https://code.wireshark.org/review/26108
Reviewed-by: Gerald Combs <gerald@wireshark.org>
Diffstat (limited to 'docbook/wsug_src/WSUG_chapter_statistics.asciidoc')
-rw-r--r-- | docbook/wsug_src/WSUG_chapter_statistics.asciidoc | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/docbook/wsug_src/WSUG_chapter_statistics.asciidoc b/docbook/wsug_src/WSUG_chapter_statistics.asciidoc index cbd2912c03..88937380a5 100644 --- a/docbook/wsug_src/WSUG_chapter_statistics.asciidoc +++ b/docbook/wsug_src/WSUG_chapter_statistics.asciidoc @@ -70,11 +70,11 @@ image::wsug_graphics/ws-stats-summary.png[{screenshot-attrs}] [[ChStatHierarchy]] -=== The ``Protocol Hierarchy'' window +=== The “Protocol Hierarchy” window The protocol hierarchy of the captured packets. -.The ``Protocol Hierarchy'' window +.The “Protocol Hierarchy” window image::wsug_graphics/ws-stats-hierarchy.png[{screenshot-attrs}] This is a tree of all the protocols in the capture. Each row contains the @@ -113,7 +113,7 @@ Packets usually contain multiple protocols. As a result more than one protocol w be counted for each packet. Example: In the screenshot IP has 99.9% and TCP 98.5% (which is together much more than 100%). -Protocol layers can consist of packets that won't contain any higher layer +Protocol layers can consist of packets that won’t contain any higher layer protocol, so the sum of all higher layer packets may not sum up to the protocols packet count. Example: In the screenshot TCP has 98.5% but the sum of the subprotocols (SSL, HTTP, etc) is much less. This can be caused by continuation @@ -139,10 +139,10 @@ description of the known endpoint types can be found in The conversations window is similar to the endpoint Window. See <<ChStatEndpointsWindow>> for a description of their common features. Along with addresses, packet counters, and byte counters the conversation window adds four -columns: the start time of the conversation (``Rel Start'') or (``Abs Start''), +columns: the start time of the conversation (“Rel Start”) or (“Abs Start”), the duration of the conversation in seconds, and the average bits (not bytes) per second in each direction. A timeline graph is also drawn across the -``Rel Start'' / ``Abs Start'' and “Duration” columns. +“Rel Start” / “Abs Start” and “Duration” columns. .The “Conversations” window image::wsug_graphics/ws-stats-conversations.png[{screenshot-attrs}] @@ -153,9 +153,9 @@ _Name resolution_ will be done if selected in the window and if it is active for the specific protocol layer (MAC layer for the selected Ethernet endpoints page). _Limit to display filter_ will only show conversations matching the current display filter. _Absolute start time_ switches the start time column -between relative (``Rel Start'') and absolute (``Abs Start'') times. Relative start -times match the ``Seconds Since Beginning of Capture'' time display format in the -packet list and absolute start times match the ``Time of Day'' display format. +between relative (“Rel Start”) and absolute (“Abs Start”) times. Relative start +times match the “Seconds Since Beginning of Capture” time display format in the +packet list and absolute start times match the “Time of Day” display format. The btn:[Copy] button will copy the list values to the clipboard in CSV (Comma Separated Values) or YAML format. The btn:[Follow Stream...] button @@ -187,7 +187,7 @@ following endpoints into account: ==== If you are looking for a feature other network tools call a _hostlist_, here is the right place to look. The list of Ethernet or IP endpoints is usually what -you're looking for. +you’re looking for. ==== .Endpoint and Conversation types @@ -234,7 +234,7 @@ _USB_:: Identical to the 7-bit USB address. .Broadcast and multicast endpoints ==== Broadcast and multicast traffic will be shown separately as additional -endpoints. Of course, as these aren't physical endpoints the real traffic +endpoints. Of course, as these aren’t physical endpoints the real traffic will be received by some or all of the listed unicast endpoints. ==== @@ -248,7 +248,7 @@ This window shows statistics about the endpoints captured. image::wsug_graphics/ws-stats-endpoints.png[{screenshot-attrs}] For each supported protocol, a tab is shown in this window. Each tab label shows -the number of endpoints captured (e.g. the tab label ``Ethernet · 4'' tells +the number of endpoints captured (e.g. the tab label “Ethernet · 4” tells you that four ethernet endpoints have been captured). If no endpoints of a specific protocol were captured, the tab label will be greyed out (although the related page can still be selected). @@ -280,13 +280,13 @@ it before (or while) you are doing a live capture. [[ChStatIOGraphs]] -=== The ``IO Graphs'' window +=== The “IO Graphs” window User configurable graph of the captured network packets. You can define up to five differently colored graphs. -.The ``IO Graphs'' window +.The “IO Graphs” window image::wsug_graphics/ws-stats-iographs.png[{screenshot-attrs}] The user can configure the following things: @@ -362,19 +362,19 @@ different) compared to the following description. [[ChStatSRTDceRpc]] -==== The "Service Response Time DCE-RPC" window +==== The “Service Response Time DCE-RPC” window The service response time of DCE-RPC is the time between the request and the corresponding response. First of all, you have to select the DCE-RPC interface: -.The "Compute DCE-RPC statistics" window +.The “Compute DCE-RPC statistics” window image::wsug_graphics/ws-stats-srt-dcerpc-filter.png[{screenshot-attrs}] You can optionally set a display filter, to reduce the amount of packets. -.The "DCE-RPC Statistic for ..." window +.The “DCE-RPC Statistic for ...” window image::wsug_graphics/ws-stats-srt-dcerpc.png[{screenshot-attrs}] Each row corresponds to a method of the interface selected (so the EPM interface @@ -395,11 +395,11 @@ is found it is checked for: * IP header checksums -* Excessive delay (defined by the "Time variance" setting) +* Excessive delay (defined by the “Time variance” setting) * Packet order -.The "Compare" window +.The “Compare” window image::wsug_graphics/ws-stats-compare.png[{screenshot-attrs}] You can configure the following: @@ -435,7 +435,7 @@ Statistics of the captured WLAN traffic. This window will summarize the wireless network traffic found in the capture. Probe requests will be merged into an existing network if the SSID matches. -.The "WLAN Traffic Statistics" window +.The “WLAN Traffic Statistics” window image::wsug_graphics/ws-stats-wlan-traffic.png[{screenshot-attrs}] Each row in the list shows the statistical values for exactly one wireless |