The Encapsulation Of Eap Attributes - Planet WGSW-52040 Configuration Manual

48-port 10/100/1000base-t + 4-port 100/1000x sfp managed switch
Hide thumbs Also See for WGSW-52040:
Table of Contents

Advertisement

Identifier: to assist matching the Request and Response messages.
Length: the length of the EAP packet, covering the domains of Code, Identifier, Length and
Data, in byte.
Data: the content of the EAP packet, depending on the Code type.

42.1.4 The Encapsulation of EAP Attributes

RADIUS
adds
two
Message-Authenticator. Please refer
"AAA-RADIUS-HWTACACS operation" to check the format of RADIUS messages.
1. EAP-Message
As illustrated in the next figure, this attribute is used to encapsulate EAP packet, the type code
is 79, String domain should be no longer than 253 bytes. If the data length in an EAP packet is
larger than 253 bytes, the packet can be divided into fragments, which then will be
encapsulated in several EAP-Messages attributes in their original order.
Figure 42-6: the Encapsulation of EAP-Message Attribute
2. Message-Authenticator
As illustrated in the next figure, this attribute is used in the process of using authentication
methods like EAP and CHAP to prevent the access request packets from being eavesdropped.
Message-Authenticator should be included in the packets containing the EAP-Message
attribute, or the packet will be dropped as an invalid one.
attribute
to
support
to
Figure 42-7: Message-Authenticator Attribute
42-140
EAP
authentication:
the
Introduction of
EAP-Message
and
RADIUS protocol
in

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents