Revision 1 as of 2006-04-21 20:39:53
DCT2000 page should be here instead...
Add link to sample capture file for this file type
|Deletions are marked like this.||Additions are marked like this.|
|Line 20:||Line 20:|
|XXX - Add a simple example capture file to the SampleCaptures page and link from here (see below). Keep this file short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.||Here is a short example file of this format, that has examples of packets using most supported link types|
|Line 22:||Line 22:|
|* attachment:SampleCaptures/PROTO.pcap|| * attachment:SampleCaptures/dct2000_test.out
|Line 34:||Line 35:|
|There is no support for directly capturing dct2000 packets - they will only be seen by opening DCT2000 .out files.||There is no way to directly capture dct2000 packets - they will only be seen by opening DCT2000 .out files.|
Catapult DCT2000 .out file packet header
This protocol / header format consists of some information associated with a packet read from a Catapult DCT2000 .out file. The fields that comprise this protocol (context, direction, original timing information) should be useful for filtering, and also make it easy to correlate entries in the Ethereal packet list with the DCT2000 decodes.
The DCT2000 dissector shows the fields of this protocol before handing off to the appropriate link-type dissector (ip, ethernet, atm, sscop, lapd, ppp, frame relay or mtp2). Support for this file support/protocol is not yet in any officially released version of Ethereal (and it may be quite some time before it is), but is available for download in recent [http://www.ethereal.com/distribution/buildbot-builds/ buildbot] builds.
There is a single preference setting.
* Only show known 'board-port' protocols. Default OFF (i.e. show all messages)
.out files can contain non-standard messages sent between contexts running on the same card, so by setting this to ON, you can tell the wiretap module not to load these messages. When creating .out files for use by Ethereal you should obviously turn on logging for board ports.
Example capture file
Here is a short example file of this format, that has examples of packets using most supported link types
A complete list of DCT2000 display filter fields can be found in the [http://www.ethereal.com/docs/dfref/d/dct2000.html display filter reference]
Show only the dct2000 based traffic:
(Note that a capture file will either all be DCT2000 packets, or none at all, so the above filter is not very useful)
There is no way to directly capture dct2000 packets - they will only be seen by opening DCT2000 .out files.
See the [http://www.catapult.com Catapult Communications] website for DCT2000 product information.