Next: , Previous: Invocation, Up: Invocation


1.1.1 Available options

-8
When comparing two packets, only compare IEEE 802.11 frames. Do not compare Prism or PCAP headers. This option is incompatible with traces of PCAP link type EN10MB.
-a
See Unique frames. Specify which attributes the program must use to identify unique frames. An attribute specifier must follow this option on the command line. To see a list of valid attribute specifiers, use the -h option.
-b
When comparing two packets, only compare packet bytes. Do not compare PCAP headers.
-c
Do not print column headers. This is the default when standard output is not a TTY.
-C
Do print column headers. This is the default when standard output is a TTY.
-d
When comparing two packets, compare everything: PCAP headers and packet bytes. This is the default.
-e
In table outputs, do not use a column to report error values. This is the default.
-E
In table outputs, do use a column to report error values.
-f
Dump an hexadecimal summary of 802.11 frames on a single line.
-F
Provide a full hexadecimal dump for each frame.
-g
Enable debugging output. As of now this only makes WiPal programs to display their options right after they parse the command line.
-h
Help. Print a short summary describing how one should invoke the program, which options it accepts, and possibly which attribute specifiers are accepted for option -a.
-i
In table outputs, do not print frame indices.
-I
In table outputs, do print frame indices. This is the default.
-m
Specify a MAC address mapping file.

Some WiPal programs need to map MAC addresses to other identifiers. For instance, wipal-extract-unique-frames with the ‘seq_bss_tmp’ attributes maps MAC addresses to 32-bit integers for performance reasons. wipal-anonymize maps real addresses to anonymous ones. Each program stores these mappings into a file so they can be reloaded and reused latter. This option allows users to control the name of this file.

When not specified, the MAC.map filename is used.

The file is just a plaintext file where each line contains a value and the corresponding MAC identifier.

A filename should follow this option. The file might not exist (in which case it will be created). If it exists, it might be extended, but will not be truncated.

-n
Consider Prism headers are little endian. This is the default when the corresponding PCAP file is little endian. Note that some broken traces are big endian yet have little endian Prism headers. Thus this option.
-N
Consider Prism headers are big endian. This is the default when the corresponding PCAP file is big endian.
-o
When comparing two traces with wipal-cmp, compare everything (PCAP headers and packet bytes, as with option -d) and count how many bytes differ. The count is printed on standard output. The exit status remains unchanged.
-p
In Prism headers, do not consider noise fields have a special meaning. This is the default.
-P
In Prism headers, consider non-null noise fields indicate a PHY error, and thus an invalid frame. Such frames will be ignored, e.g. with wipal-cat they will not appear in the output.

This option implicitly implies the input trace is composed of Prism headers (as PCAP link type).

-q
Quiet. Produce minimal output.
-r
Blacklist a given reference frame. The reference frame will then be ignored and will not be used during synchronization. See Synchronization.

A reference frame identifier must follow this option, e.g. 42-51 (indicating the reference frame composed of the unique frames 42 and 51).

You may use this option multiple times, e.g.

          wipal-simple-merge -r 42-51 -r 666-505 \
              input1.pcap input2.pcap output.pcap

will blacklist both references 42-51 and 666-505.

-s
Specify an ESSID mapping file.

This option works as -m but for files that map ESSIDs to other values. For instance, wipal-anonymize maps valid ESSIDs to anonymous ESSIDs.

See -m for details. The default mapping file is ESSID.map.

-t
When comparing two packets, only compare IEEE 802.11 frames, along with some timestamps (e.g. PCAP time, Prism MAC time, etc). Which timestamps are used depends on the traces' link types (and whether options -y or -Y are provided as well). Compare time values with a precision of 106 microseconds by default (that is, assume two values are equal when they are spaced by less than 107 microseconds). You can change the precision using option -x.
-u
In table outputs, do not print microsecond timestamps. This is the default.
-U
In table outputs, do print microsecond timestamps.
-v
Display the program's version (actually the version of the WiPal package the program come from).
-x
Change precision for timestamps comparisons (e.g. when using wipal-cmp with -t or when merging or synchronizing traces).

By default, when the duration between two timestamps is 106 microseconds or less, WiPal programs consider the timestamps are equal. The rationale for this behavior is 106 microseconds is half the shortest frame interarrival time between two IEEE 802.11 frames (in infrastructure mode). Thus, this is the largest value one can afford when synchronizing IEEE 802.11 traces.

Use -x to change this value. The new expected precision should be right after -x on the command line.

-y
Force the use of PCAP timestamps.

Some traces contain multiple timestamps for each frame. For instance, PCAP traces with link type PRISM_HEADER have the standard PCAP timestamps plus extra PHY-level timestamps provided by the network adapter. WiPal programs' policy is to use the most precise timestamps (that is, to ignore PCAP timestamps when something else is available). This option alters this behavior and forces programs to use PCAP timestamps.

-Y
Force the use of PHY-level timestamps when available. This is the default. See option -y for a more detailed explanation.