parse::pidl::wireshark::conformance(3) [centos man page]
..::pidl::lib::Parse::Pidl::Wireshark::Conformance(3) Samba Documentation ..::pidl::lib::Parse::Pidl::Wireshark::Conformance(3)NAME
Parse::Pidl::Wireshark::Conformance - Conformance file parser for Wireshark
DESCRIPTION
This module supports parsing Wireshark conformance files (*.cnf).
FILE FORMAT
Pidl needs additional data for Wireshark output. This data is read from so-called conformance files. This section describes the format of
these files.
Conformance files are simple text files with a single command on each line. Empty lines and lines starting with a '#' character are
ignored. Arguments to commands are separated by spaces.
The following commands are currently supported:
TYPE name dissector ft_type base_type mask valsstring alignment
Register new data type with specified name, what dissector function to call and what properties to give header fields for elements of
this type.
NOEMIT type
Suppress emitting a dissect_type function for the specified type
PARAM_VALUE type param
Set parameter to specify to dissector function for given type.
HF_FIELD hf title filter ft_type base_type valsstring mask description
Generate a custom header field with specified properties.
HF_RENAME old_hf_name new_hf_name
Force the use of new_hf_name when the parser generator was going to use old_hf_name.
This can be used in conjunction with HF_FIELD in order to make more than one element use the same filter name.
ETT_FIELD ett
Register a custom ett field
STRIP_PREFIX prefix
Remove the specified prefix from all function names (if present).
PROTOCOL longname shortname filtername
Change the short-, long- and filter-name for the current interface in Wireshark.
FIELD_DESCRIPTION field desc
Change description for the specified header field. `field' is the hf name of the field.
IMPORT dissector code...
Code to insert when generating the specified dissector. @HF@ and @PARAM@ will be substituted.
INCLUDE filename
Include conformance data from the specified filename in the dissector.
TFS hf_name "true string" "false string"
Override the text shown when a bitmap boolean value is enabled or disabled.
MANUAL fn_name
Force pidl to not generate a particular function but allow the user to write a function manually. This can be used to remove the
function for only one level for a particular element rather than all the functions and ett/hf variables for a particular element as the
NOEMIT command does.
EXAMPLE
INFO_KEY OpenKey.Ke
perl v5.16.3 2013-06-13 ..::pidl::lib::Parse::Pidl::Wireshark::Conformance(3)
Check Out this Related Man Page
MERGECAP(1) The Wireshark Network Analyzer MERGECAP(1)NAME
mergecap - Merges two or more capture files into one
SYNOPSIS
mergecap [ -a ] [ -F <file format> ] [ -h ] [ -s <snaplen> ] [ -T <encapsulation type> ] [ -v ] -w <outfile>|- <infile> ...
DESCRIPTION
Mergecap is a program that combines multiple saved capture files into a single output file specified by the -w argument. Mergecap knows
how to read libpcap capture files, including those of tcpdump, Wireshark, and other tools that write captures in that format.
By default, Mergecap writes the capture file in libpcap format, and writes all of the packets from the input capture files to the output
file.
Mergecap is able to detect, read and write the same capture files that are supported by Wireshark. The input files don't need a specific
filename extension; the file format and an optional gzip compression will be automatically detected. Near the beginning of the DESCRIPTION
section of wireshark(1) or http://www.wireshark.org/docs/man-pages/wireshark.html <http://www.wireshark.org/docs/man-pages/wireshark.html>
is a detailed description of the way Wireshark handles this, which is the same way Mergecap handles this.
Mergecap can write the file in several output formats. The -F flag can be used to specify the format in which to write the capture file,
mergecap -F provides a list of the available output formats.
Packets from the input files are merged in chronological order based on each frame's timestamp, unless the -a flag is specified. Mergecap
assumes that frames within a single capture file are already stored in chronological order. When the -a flag is specified, packets are
copied directly from each input file to the output file, independent of each frame's timestamp.
The output file frame encapsulation type is set to the type of the input files if all input files have the same type. If not all of the
input files have the same frame encapsulation type, the output file type is set to WTAP_ENCAP_PER_PACKET. Note that some capture file
formats, most notably libpcap, do not currently support WTAP_ENCAP_PER_PACKET. This combination will cause the output file creation to
fail.
OPTIONS -a Causes the frame timestamps to be ignored, writing all packets from the first input file followed by all packets from the second input
file. By default, when -a is not specified, the contents of the input files are merged in chronological order based on each frame's
timestamp.
Note: when merging, mergecap assumes that packets within a capture file are already in chronological order.
-F <file format>
Sets the file format of the output capture file. Mergecap can write the file in several formats; mergecap -F provides a list of the
available output formats. The default is to use the file format of the first input file.
-h Prints the version and options and exits.
-s <snaplen>
Sets the snapshot length to use when writing the data. If the -s flag is used to specify a snapshot length, frames in the input file
with more captured data than the specified snapshot length will have only the amount of data specified by the snapshot length written
to the output file. This may be useful if the program that is to read the output file cannot handle packets larger than a certain size
(for example, the versions of snoop in Solaris 2.5.1 and Solaris 2.6 appear to reject Ethernet frames larger than the standard Ethernet
MTU, making them incapable of handling gigabit Ethernet captures if jumbo frames were used).
-v Causes mergecap to print a number of messages while it's working.
-w <outfile>|-
Sets the output filename. If the name is '-', stdout will be used. This setting is mandatory.
-T <encapsulation type>
Sets the packet encapsulation type of the output capture file. If the -T flag is used to specify a frame encapsulation type, the
encapsulation type of the output capture file will be forced to the specified type, rather than being the type appropriate to the
encapsulation type of the input capture files.
Note that this merely forces the encapsulation type of the output file to be the specified type; the packet headers of the packets will
not be translated from the encapsulation type of the input capture file to the specified encapsulation type (for example, it will not
translate an Ethernet capture to an FDDI capture if an Ethernet capture is read and '-T fddi' is specified).
SEE ALSO tcpdump(8), pcap(3), wireshark(1), tshark(1), dumpcap(1), editcap(1), text2pcap(1)NOTES
Mergecap is based heavily upon editcap by Richard Sharpe <sharpe[AT]ns.aus.com> and Guy Harris <guy[AT]alum.mit.edu>.
Mergecap is part of the Wireshark distribution. The latest version of Wireshark can be found at <http://www.wireshark.org>.
HTML versions of the Wireshark project man pages are available at: http://www.wireshark.org/docs/man-pages
<http://www.wireshark.org/docs/man-pages>.
AUTHORS
Original Author
-------- ------
Scott Renfro <scott[AT]renfro.org>
Contributors
------------
Bill Guyton <guyton[AT]bguyton.com>
1.2.8 2010-05-05 MERGECAP(1)