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 20 and 21
Revision 20 as of 2007-04-21 01:34:14
Size: 4062
Editor: c-68-40-200-71
Comment:
Revision 21 as of 2008-01-28 19:15:19
Size: 3918
Editor: 90-227-134-108-no52
Comment:
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
The DIAMETER dissector is fully functional. DIAMETER uses internal value strings to display AVP names etc., or, if Libxml is present
on the system, it reads a XML dictionary which is located in the Diameter folder.
A Windows port of Libxml can be found at http://www.zlatkovic.com/libxml.en.html. Unpack the libxml2.dll and place it in the
Wireshark directory ( Program files/Wireshark ).
The DIAMETER dissector is fully functional. The dissection of AVP:s is specified in .xml files in the diameter directory. Wireshark 0.99.7 or later reads these files without any extra libraries. You can add AVP dissection of vendor specific or missing AVP:s by editing those files. If you add publicly available AVP:s please send us the updates.
Currently there is a problem with application Id, if two AVP:s have the same vendor Id but different Application ID WS can't distinguish between them [http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1494 Bug1494].
Line 27: Line 25:
 * Diameter version. If Diameter should be dissected according to RFC or earlier drafts.
* TCP Port. TCP packets on this port will be dissected as Diameter.
 * TCP Port(s)/range. TCP packets on this port(s)/range will be dissected as Diameter.
Line 30: Line 27:
 * Diameter XML library. Path to the XML library
 * Atempt to use the XML libary. If XML should be used or not Default on.
Line 33: Line 28:
 * Allow 0 as valid aplication ID. Default on.
 * Suppress console output for unknown AVP:s Flags etc. Default off.

DIAMETER

The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations.

History

This is the successor of the ["RADIUS"] protocol.

Protocol dependencies

  • ["TCP"]: Typically, DIAMETER uses ["TCP"] as its transport protocol. The well known TCP port for DIAMETER traffic is 3868.
  • ["SCTP"]: Typically, DIAMETER uses ["SCTP"] as its transport protocol. The well known SCTP port for DIAMETER traffic is 3868.

Example traffic

XXX - Add example traffic here (as plain text or Wireshark screenshot).

Wireshark

The DIAMETER dissector is fully functional. The dissection of AVP:s is specified in .xml files in the diameter directory. Wireshark 0.99.7 or later reads these files without any extra libraries. You can add AVP dissection of vendor specific or missing AVP:s by editing those files. If you add publicly available AVP:s please send us the updates. Currently there is a problem with application Id, if two AVP:s have the same vendor Id but different Application ID WS can't distinguish between them [http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1494 Bug1494].

Preference Settings

  • TCP Port(s)/range. TCP packets on this port(s)/range will be dissected as Diameter.
  • SCTP port. SCTP packets on this port will be dissected as Diameter.
  • Reassemble Diameter messages spanning multiple TCP segments. Default on.

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of DIAMETER display filter fields can be found in the [http://www.wireshark.org/docs/dfref/d/diameter.html display filter reference]

  • Show only DIAMETER traffic:

     diameter 

Capture Filter

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

  • Capture DIAMETER traffic over the default TCP port (3868):

     tcp port 3868 

Internet-drafts:

* [http://www.ietf.org/internet-drafts/draft-ietf-marid-csv-intro-02.txt Client SMTP Validation (CSV)]

Open source Diameter implementation:

Discussion

DIAMETER (last edited 2014-04-16 20:07:46 by JeffMorriss)