This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 10 and 11
Revision 10 as of 2005-10-03 12:34:11
Size: 4179
Editor: charybdis
Comment: Update on Diameter RFCs.
Revision 11 as of 2005-10-03 17:46:04
Size: 3345
Editor: GuyHarris
Comment: Resolve edit conflicts (no real conflicts were present).
Deletions are marked like this. Additions are marked like this.
Line 49: Line 49:

---- /!\ '''Edit conflict - other version:''' ----
Line 56: Line 54:

---- /!\ '''Edit conflict - your version:''' ----
 * [ RFC 3589] ''Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5''
 * [ RFC 4006] ''Diameter Credit-control Application''
 * [ RFC 4004] ''Diameter Mobile IPv4 Application''
 * [ RFC 4005] ''Diameter Network Access Server Application''
 * [ RFC 4072] ''Diameter Extensible Authentication Protocol (EAP) Application''

---- /!\ '''End of edit conflict''' ----
Line 72: Line 59:
---- /!\ '''Edit conflict - other version:''' ----

---- /!\ '''Edit conflict - your version:''' ----

---- /!\ '''End of edit conflict''' ----


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 Ethereal 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, the XML library is out of date.

A Windows port of Libxml can be found at

Preference Settings

(XXX add links to preference settings affecting how PROTO is dissected).

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


Open source Diameter implementation:


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