This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 3 and 4
Revision 3 as of 2006-04-28 07:49:37
Size: 2194
Editor: no-dns-yet
Comment: Warn about not-yet-generated display filter page (could this be generated?)
Revision 4 as of 2006-06-05 03:19:13
Size: 2200
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
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. 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 Wireshark packet list with the DCT2000 decodes.
Line 6: Line 6:
== Ethereal == == Wireshark ==
Line 8: Line 8:
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. 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 Wireshark (and it may be quite some time before it is), but is available for download in recent [http://www.wireshark.org/distribution/buildbot-builds/ buildbot] builds.
Line 16: Line 16:
.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. .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 Wireshark you should obviously turn on logging for board ports.
Line 26: Line 26:
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] ('''NOTE: this page should be generated after the next developer release''') A complete list of DCT2000 display filter fields can be found in the [http://www.wireshark.org/docs/dfref/d/dct2000.html display filter reference] ('''NOTE: this page should be generated after the next developer release''')

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 Wireshark packet list with the DCT2000 decodes.

Wireshark

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 Wireshark (and it may be quite some time before it is), but is available for download in recent [http://www.wireshark.org/distribution/buildbot-builds/ buildbot] builds.

Preference Settings

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 Wireshark 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

  • attachment:SampleCaptures/dct2000_test.out

Display Filter

A complete list of DCT2000 display filter fields can be found in the [http://www.wireshark.org/docs/dfref/d/dct2000.html display filter reference] (NOTE: this page should be generated after the next developer release)

  • Show only the dct2000 based traffic:

     dct2000 

(Note that a capture file will either all be DCT2000 packets, or none at all, so the above filter is not very useful)

Capture Filter

There is no way to directly capture dct2000 packets - they will only be seen by opening DCT2000 .out files.

Discussion

DCT2000 (last edited 2012-05-13 22:03:13 by MartinMathieson)