Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

idl2wrs(1) [debian man page]

IDL2WRS(1)						  The Wireshark Network Analyzer						IDL2WRS(1)

NAME
idl2wrs - CORBA IDL to Wireshark Plugin Generator SYNOPSIS
idl2wrs filename DESCRIPTION
idl2wrs is a program that takes a user specified CORBA IDL file and generates "C" source code for a Wireshark "plugin". This resulting file can be compiled as a Wireshark plugin, and used to monitor GIOP/IIOP traffic that is using this IDL. idl2wrs is actually a shell script wrapper for two Python programs. These programs are: wireshark_be.py - Contains the main IDL Visitor Class wireshark_gen.py - Contains the Source Code Generator Class idl2wrs supports heuristic dissection of GIOP/IIOP traffic, and some experimental code for explicit dissection, based on Object Key <-> Repository Id mapping. However, code for heuristic based plugins is generated by default, and users should consider this the preferred method unless you have some namespace collisions. OPTIONS
Currently there are no options. idl2wrs can be invoked as follows. 1. To write the C code to stdout. idl2wrs <your_file.idl> eg: idl2wrs echo.idl 2. To write to a file, just redirect the output. idl2wrs echo.idl > packet-test.c ENVIRONMENT
idl2wrs will look for wireshark_be.py and wireshark_gen.py in $PYTHONPATH/site-packages/ and if not found, will try the current directory ./ The -p option passed to omniidl (inside idl2wrs) indicates where wireshark_be.py and wireshark_gen.py will be searched. This may need tweaking if you place these files somewhere else. If it complains about being unable to find some modules (eg tempfile.py), you may want to check if PYTHONPATH is set correctly. eg: PYTHONPATH=/usr/lib/python1.5/ SEE ALSO
wireshark(1), tshark(1) NOTES
idl2wrs (including wireshark_be.py and wireshark_gen.py) are part of the Wireshark distribution. The latest version of Wireshark can be found at <http://www.wireshark.org>. idl2wrs uses omniidl, an IDL parser, and can be found at <http://omniorb.sourceforge.net/> TODO
Some of the more important things to do are: o Improve Explicit dissection code. o Improve command line options. o Improve decode algorithm when we have operation name collision. AUTHORS
Original Author -------- ------ Frank Singleton <frank.singleton[AT]ericsson.com> Contributors ------------ 1.8.2 2012-06-05 IDL2WRS(1)

Check Out this Related Man Page

CAPINFOS(1)						  The Wireshark Network Analyzer					       CAPINFOS(1)

NAME
capinfos - Prints information about capture files SYNOPSIS
capinfos [ -t ] [ -E ] [ -c ] [ -s ] [ -d ] [ -u ] [ -a ] [ -e ] [ -y ] [ -i ] [ -z ] [ -x ] [ -h ] <infile> ... DESCRIPTION
Capinfos is a program that reads one or more capture files and returns some or all available statistics of each <infile>. The user specifies which statistics to report by specifying flags corresponding to the statistic. If no flags are specified, Capinfos will report all statistics available. Capinfos is able to detect and read 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 Capinfos handles this. OPTIONS
-t Displays the capture type of the capture file. -E Displays the per-file encapsulation of the capture file. -c Counts the number of packets in the capture file. -s Displays the size of the file, in bytes. This reports the size of the capture file itself. -d Displays the total length of all packets in the file, in bytes. This counts the size of the packets as they appeared in their original form, not as they appear in this file. For example, if a packet was originally 1514 bytes and only 256 of those bytes were saved to the capture file (if packets were captured with a snaplen or other slicing option), Capinfos will consider the packet to have been 1514 bytes. -u Displays the capture duration, in seconds. This is the difference in time between the earliest packet seen and latest packet seen. -a Displays the start time of the capture. Capinfos considers the earliest timestamp seen to be the start time, so the first packet in the capture is not necessarily the earliest - if packets exist "out-of-order", time-wise, in the capture, Capinfos detects this. -e Displays the end time of the capture. Capinfos considers the latest timestamp seen to be the end time, so the last packet in the capture is not necessarily the latest - if packets exist "out-of-order", time-wise, in the capture, Capinfos detects this. -y Displays the average data rate, in bytes/sec -i Displays the average data rate, in bits/sec -z displays the average packet size, in bytes -x displays the average packet rate, in packets/sec -h Prints the help listing and exits. SEE ALSO
tcpdump(8), pcap(3), wireshark(1), mergecap(1), editcap(1), tshark(1), dumpcap(1) NOTES
Capinfos 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 -------- ------ Ian Schorr <ian[AT]ianschorr.com> Contributors ------------ Gerald Combs <gerald[AT]wireshark.org> 1.2.8 2010-05-05 CAPINFOS(1)
Man Page