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 15 and 17 (spanning 2 versions)
Revision 15 as of 2010-10-10 16:20:00
Size: 2655
Comment: added the well-known port number (716) and RFC 5191
Revision 17 as of 2010-10-12 16:55:02
Size: 2784
Comment: added the screenshot at the Example traffic section.
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
XXX - Add example decoded traffic for this protocol here (as plain text or Wireshark screenshot). {{attachment:Wireshark_1.5.0_SVN_Rev_34447_from_trunk-pana-rfc5191_cap.png}}

The depicted trace is available here: [[attachment:SampleCaptures/pana-rfc5191.cap]]
Line 28: Line 30:
 * [[attachment:SampleCaptures/pana.cap]]  * [[attachment:SampleCaptures/pana-rfc5191.cap]] PANA authentication and re-authentication sequences.

Protocol for carrying Authentication for Network Access (PANA)

PANA is a protocol used to authenticate users before granting network access. PANA is an IP based protocol and it enables the client to interact with a back-end AAA server, deployed in the network provide's domain. It enables the client to authenticate against the AAA server without using link-layer specific mechanisms or knowing the specific AAA protocol. PANA can be used on both multi-access and point-to-point links and it supports various authentication methods, dynamic network provider selection, and roaming clients. PANA does not define any new authentication mechanism but uses EAP to transfer authentication related data. Any authentication method on top of EAP can be used in PANA.

History

XXX - add a brief description of PANA history

Protocol dependencies

  • UDP: PANA uses UDP as its transport protocol. The well known UDP port for PANA traffic is 716.

Example traffic

Wireshark_1.5.0_SVN_Rev_34447_from_trunk-pana-rfc5191_cap.png

The depicted trace is available here: SampleCaptures/pana-rfc5191.cap

Wireshark

The PANA dissector is fully functional.

Preference Settings

There are no PANA related preference settings.

Example capture file

Display Filter

A complete list of PANA display filter fields can be found in the display filter reference

  • Show only the PANA based traffic:

     pana 

Capture Filter

XXX

IETF PANA Working Group

Current RFCs

  • RFC5191 Protocol for Carrying Authentication for Network Access (PANA)

  • RFC4016 Protocol for Carrying Authentication and Network Access (PANA) - Threat Analysis and Security Requirements

  • RFC4058 Protocol for Carrying Authentication for Network Access (PANA) - Requirements

Discussion

Q:I don't think a capture filter named "pana" will work. - UlfLamping

R:It will work if packets are decoded as pana.

R:As display filter yes, but not as capture filter. - JaapKeuter

Q:In the pana_draft_17 the pana header contains a session identifier. Wireshark dont take car of it. is it a interpretation error?

R:pana.sid is used for session ID. If there is an error please file a bug report with a capture file showing it. - JaapKeuter

PANA (last edited 2010-10-12 16:55:02 by YasuyukiTanaka)