forked from osmocom/wireshark
parent
fae0f7d74a
commit
86db02c22e
|
@ -54,7 +54,7 @@ to the report type and desired infos. If no options are specified,
|
|||
B<Capinfos> will report all statistics available in "long" format.
|
||||
|
||||
Options are processed from left to right order with later options
|
||||
superceeding or adding to earlier options.
|
||||
superseding or adding to earlier options.
|
||||
|
||||
B<Capinfos> is able to detect and read the same capture files that are
|
||||
supported by B<Wireshark>.
|
||||
|
|
|
@ -105,7 +105,7 @@ to standard out. This verbose output (specifically the MD5 hash strings)
|
|||
can be useful in scripts to identify duplicate packets across trace
|
||||
files.
|
||||
|
||||
The <dup window> is specifed as an integer value between 0 and 1000000 (inclusive).
|
||||
The <dup window> is specified as an integer value between 0 and 1000000 (inclusive).
|
||||
|
||||
NOTE: Specifying large <dup window> values with large tracefiles can
|
||||
result in very long processing times for B<editcap>.
|
||||
|
@ -119,7 +119,7 @@ and the packet length and MD5 hash of the current packet are the same then
|
|||
the packet to skipped. The duplicate comparison test stops when
|
||||
the current packet's relative arrival time is greater than <dup time window>.
|
||||
|
||||
The <dup time window> is specifed as I<seconds>[I<.fractional seconds>].
|
||||
The <dup time window> is specified as I<seconds>[I<.fractional seconds>].
|
||||
|
||||
The [.fractional seconds] component can be specified to nine (9) decimal
|
||||
places (billionths of a second) but most typical trace files have resolution
|
||||
|
@ -134,7 +134,7 @@ removal option may not identify some duplicates.
|
|||
|
||||
=item -E E<lt>error probabilityE<gt>
|
||||
|
||||
Sets the probabilty that bytes in the output file are randomly changed.
|
||||
Sets the probability that bytes in the output file are randomly changed.
|
||||
B<Editcap> uses that probability (between 0.0 and 1.0 inclusive)
|
||||
to apply errors to each data byte in the file. For instance, a
|
||||
probability of 0.02 means that each byte has a 2% chance of having an error.
|
||||
|
|
|
@ -178,8 +178,8 @@ packet, and prepend a dummy SCTP DATA chunk header with a payload
|
|||
protocol identifier if I<ppi>. Use this option if your dump is the SCTP
|
||||
payload of a packet but does not include any SCTP, IP or Ethernet
|
||||
headers. Note that appropriate Ethernet and IP headers are
|
||||
automatcally included with each packet. A CRC32C checksum will be put into the
|
||||
SCTP header.
|
||||
automatically included with each packet. A CRC32C checksum will be put
|
||||
into the SCTP header.
|
||||
|
||||
=item -t E<lt>timefmtE<gt>
|
||||
|
||||
|
|
|
@ -297,7 +297,7 @@ have the same number of bytes as the slice itself, as in:
|
|||
=head2 Logical expressions
|
||||
|
||||
Tests can be combined using logical expressions.
|
||||
These too are expressable in C-like syntax or with English-like
|
||||
These too are expressible in C-like syntax or with English-like
|
||||
abbreviations:
|
||||
|
||||
and, && Logical AND
|
||||
|
@ -366,7 +366,7 @@ packets as well, you can use one of the following two expressions:
|
|||
The first filter uses "not ip" to include all non-IP packets and then
|
||||
lets "ip.dst ne 224.1.2.3" filter out the unwanted IP packets. The
|
||||
second filter has already been explained above where filtering with
|
||||
multiply occuring fields was discussed.
|
||||
multiply occurring fields was discussed.
|
||||
|
||||
=head1 FILTER FIELD REFERENCE
|
||||
|
||||
|
|
Loading…
Reference in New Issue