aboutsummaryrefslogtreecommitdiffstats
path: root/help
diff options
context:
space:
mode:
authorulfl <ulfl@f5534014-38df-0310-8fa8-9805f1628bb7>2004-02-21 22:52:54 +0000
committerulfl <ulfl@f5534014-38df-0310-8fa8-9805f1628bb7>2004-02-21 22:52:54 +0000
commitbd484c77fa9c5b28b144301136e5fc05e0b0afe6 (patch)
treedf720b9b64121d51909049bc6ac2299f378c79c3 /help
parent43bcc6cce4f5246b6d65a41f31e11437ddf86907 (diff)
new somewhat improved layout of the capture options dialog
git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@10173 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'help')
-rw-r--r--help/capturing.txt14
1 files changed, 8 insertions, 6 deletions
diff --git a/help/capturing.txt b/help/capturing.txt
index 5a182cb220..9d0877ef22 100644
--- a/help/capturing.txt
+++ b/help/capturing.txt
@@ -21,15 +21,11 @@ Input options
Filtering options
-----------------
--Limit each packet to xy bytes: Will limit the maximum size to be captured of each packet, this includes the link-layer header and all subsequent headers. This can be useful when an error is known to be in the first 20 bytes of a packet, for example, as the size of the resulting capture file will be reduced.
-
-Capture packets in promiscuous mode: Usually a network card will only capture the traffic to its own network address. If you want to capture all traffic that the network card can "see", mark this option. See the FAQ for some more details of capturing packets from a switched network.
--Capture Filter: Use a capture filter to reduce the amount of packets to be captured. See "Capture Filters" in this help for further information how to use it.
+-Limit each packet to xy bytes: Will limit the maximum size to be captured of each packet, this includes the link-layer header and all subsequent headers. This can be useful when an error is known to be in the first 20 bytes of a packet, for example, as the size of the resulting capture file will be reduced.
-Stop condition options
-----------------------
-These three fields should be obvious; the capture process will be automatically stopped if one of the selected conditions is exceeded.
+-Capture Filter: Use a capture filter to reduce the amount of packets to be captured. See "Capture Filters" in this help for further information how to use it.
Storing options
---------------
@@ -38,6 +34,10 @@ Storing options
-Use ring buffer: Instead of using a single capture file, multiple files will be created. The generated filenames will contain a incrementing number and the start time of the capture. For example, if you choose "/foo.cap" in the "File" field, files like "/foo_00001_20040205110102.cap", "/foo_00002_20040205110102.cap", ... will be created.
This feature can be useful if you do long term capturing, as working with a single capture file of several GB usually isn't very fast.
+Stop condition options
+----------------------
+These three fields should be obvious; the capture process will be automatically stopped if one of the selected conditions is exceeded.
+
Display while capturing options
-------------------------------
-Update List of packets in real time: Using this will show the captured packets immediately on the main screen.
@@ -45,6 +45,8 @@ Please note: this will slow down capturing, so increased packet drops might appe
-Automatic scrolling in live capture: This will scroll the "Packet List" automatically to the latest captured packet, when the "Update List of packets in real time" option is used.
+-Name resolution: perform the corresponding name resolution while capturing
+
High performance capturing