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 26 and 27
Revision 26 as of 2010-08-19 02:42:19
Size: 4283
Comment:
Revision 27 as of 2010-09-22 13:23:17
Size: 4394
Editor: BillMeier
Comment: Minor wording, formatting and spelling changes.
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. [''From RFC 3588''] "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 21: Line 22:
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 23: Line 23:
A known problem is 3GPP vendor specific AVP:s in the range 1 - 26 in TGPPGmb.xml and imscxdx.xml which is mutaly exlusive and depending on which 3GPP interface you are tracing they have to be commented out.    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]]).

A known problem is 3GPP vendor specific AVP:s in the range 1 - 26 in TGPPGmb.xml and imscxdx.xml which are mutually exclusive; depending on which 3GPP interface you are tracing one set will have to be commented out. (In the Wireshark distribution, the set in imscxdx.xml is commented out).

DIAMETER

[From RFC 3588] "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 (Bug1494).

A known problem is 3GPP vendor specific AVP:s in the range 1 - 26 in TGPPGmb.xml and imscxdx.xml which are mutually exclusive; depending on which 3GPP interface you are tracing one set will have to be commented out. (In the Wireshark distribution, the set in imscxdx.xml is commented out).

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

* Client SMTP Validation (CSV)

Open source Diameter implementation:

Discussion

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