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 5 and 6
Revision 5 as of 2005-02-22 17:34:23
Size: 3241
Editor: UlfLamping
Comment: add some basics
Revision 6 as of 2005-04-02 01:25:18
Size: 3293
Editor: GuyHarris
Comment: Canonicalize RFC display, give TCP capture filter.
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
   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.
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.
Line 27: 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 a
XML dictionary which is located in the Diameter folder, the XML library is out of date.
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.
Line 43: Line 36:
 Show only the DIAMETER based traffic: {{{  Show only DIAMETER traffic: {{{
Line 50: Line 43:
 Capture DIAMETER traffic over the default TCP port (3868): {{{
 tcp port 3868 }}}
Line 52: Line 48:
 * [http://www.ietf.org/rfc/rfc3588.txt?number=3588 Diameter Base Protocol RFC3588]  * [http://www.ietf.org/rfc/rfc3588.txt RFC 3588] ''Diameter Base Protocol''

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

Ethereal

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 http://www.zlatkovic.com/libxml.en.html

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 [http://www.ethereal.com/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:

Open source Diameter implementation:

Discussion

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