![FoxGate S6424-S2C2 series Скачать руководство пользователя страница 162](http://html1.mh-extra.com/html/foxgate/s6424-s2c2-series/s6424-s2c2-series_configuration-manual_2325481162.webp)
Configuring 802.1X
162
supplicant or just the traffic from the supplicant
。
22.1.2 Rule of 802.1x
The 802.1x authentication system employs the Extensible Authentication Protocol (EAP)
to exchange authentication information between the supplicant PAE, authenticator PAE, and
authentication server.
At present, the EAP relay mode supports four authentication methods: EAP-MD5,
EAP-TLS (Transport Layer Security), EAP-TTLS (Tunneled Transport Layer Security), and
PEAP (Protected Extensible Authentication Protocol).
1) When a user launches the 802.1x client software and enters the registered username
and password, the 802.1x client software generates an EAPOL-Start frame and sends it to the
authenticator to initiate an authentication process.
2) Upon receiving the EAPOL-Start frame, the authenticator responds with an
EAP-Request/Identity packet for the username of the supplicant.
3) When the supplicant receives the EAP-Request/Identity packet, it encapsulates the
username in an EAP-Response/Identity packet and sends the packet to the authenticator.
4) Upon receiving the EAP-Response/Identity packet, the authenticator relays the packet
in a RADIUS Access-Request packet to the authentication server.
5) When receiving the RADIUS Access-Request packet, the RADIUS server compares the
identify information against its user information table to obtain the corresponding password
information. Then, it encrypts the password information using a randomly generated
challenge, and sends the challenge information through a RADIUS Access-Challenge packet
to the authenticator.
6) After receiving the RADIUS Access-Challenge packet, the authenticator relays the
contained EAP-Request/MD5 Challenge packet to the supplicant.
7) When receiving the EAP-Request/MD5 Challenge packet, the supplicant uses the
offered challenge to encrypt the password part (this process is not reversible), creates an
EAP-Response/MD5 Challenge packet, and then sends the packet to the authenticator.
8) After receiving the EAP-Response/MD5 Challenge packet, the authenticator relays the
packet in a RADIUS Access-Request packet to the authentication server.
9) When receiving the RADIUS Access-Request packet, the RADIUS server compares the
password information encapsulated in the packet with that generated by itself. If the two are
identical, the authentication server considers the user valid and sends to the authenticator a
RADIUS Access-Accept packet.
10) Upon receiving the RADIUS Access-Accept packet, the authenticator opens the port to