This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 19 and 20
Revision 19 as of 2007-02-09 07:19:55
Size: 3964
Editor: h141n1fls34o887
Revision 20 as of 2007-04-21 01:34:14
Size: 4062
Editor: c-68-40-200-71
Deletions are marked like this. Additions are marked like this.
Line 65: Line 65:
 * [ Introduction to 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.


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).


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 Unpack the libxml2.dll and place it in the Wireshark directory ( Program files/Wireshark ).

Preference Settings

  • 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.
  • SCTP port. SCTP packets on this port will be dissected as Diameter.
  • Diameter XML library. Path to the XML library
  • Atempt to use the XML libary. If XML should be used or not Default on.
  • Reassemble Diameter messages spanning multiple TCP segments. Default on.
  • Allow 0 as valid aplication ID. Default on.
  • Suppress console output for unknown AVP:s Flags etc. Default off.

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 [ display filter reference]

  • Show only DIAMETER traffic:


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 


* [ Client SMTP Validation (CSV)]

Open source Diameter implementation:


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