General Inter-ORB Protocol (GIOP)

GIOP is the protocol typically used by CORBA. See links below for more information.

History

TODO.

Protocol dependencies

Example traffic

TODO.

Ethereal

The GIOP dissector is fully functional. Certain CORBA interfaces can be dissected by Ethereal out of the box: CosEvents, CosNaming, Parlay, TANGO. These dissectors are generated by a pyton script [http://www.ethereal.com/docs/man-pages/idl2eth.1.html idl2eth] and IDLfiles.

Preference Settings

- Reassemble GIOP messages spanning multiple TCP segments: Switched on by default and you typically want this.

- Stringified IOR file name: If you have the interoperable object reference(s) of the observed object(s) communicating, you can put them in a file, one per line. Stringified IORs start with the letters "IOR:" and coninue with typically a few hundred hex characters [o-0a-fA-F] in ASCII encoding. See [http://www.omg.org/gettingstarted/orb_details.htm] for more information.

Example capture file

TODO.

Display Filter

A complete list of GIOP display filter fields can be found in the [http://www.ethereal.com/docs/dfref/g/giop.html display filter reference]

Capture Filter

You cannot directly filter GIOP protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.

Discussion

TODO.