25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3. The authentication server sends an EAP-Request/Authentication packet to<br />

the authenticator over RADIUS <strong>and</strong> forwards this to the supplicant over<br />

EAPoL. This packet requests the supplicant to prove its credentials using the<br />

authentication type supported on the authentication server.<br />

4. If the supplicant does not support the authentication type mentioned in the<br />

EAP-Request/Authentication packet, it responds with an EAP-Nak message,<br />

which indicates that the authentication type is not supported. The packet can<br />

also include the desired type of authentication that the supplicant supports. If<br />

the supplicant supports the authentication type, it responds with the<br />

EAP-Response/Authentication packet to the authenticator, which forwards<br />

this packet to the authentication server. The number of request <strong>and</strong> response<br />

authentication messages exchanged depends on the authentication type in<br />

use.<br />

5. With a series of EAP-Request <strong>and</strong> -Response authentication packet<br />

exchanges, the authentication server verifies the supplicant's credentials. If<br />

credentials are proper, the authentication server sends an EAP-Success<br />

packet to the authenticator, which is then forwarded to the supplicant. The<br />

supplicant receives an EAP-Failure packet if it is not able to prove its<br />

credentials. If the authentication is successful, the authenticator moves the<br />

controlled port to the “authorized” state, allowing the supplicant to access the<br />

network <strong>and</strong> Internet.<br />

6. If the type of authentication is successful, the supplicant receives an<br />

EAPOL-Key packet from the authenticator. IEEE 802.1x provides a way of<br />

exchanging information related to the encryption key between the supplicant<br />

<strong>and</strong> authenticator with the EAPOL-Key packet, helping in sharing a common<br />

encryption key for that particular session. If you use PEAP, TLS, or TTLS<br />

over EAP to provide authentication, the authentication server first sends<br />

information related to encryption key to the authenticator. The authenticator<br />

forwards this information as an EAPOL-Key packet to the supplicant.<br />

7. If the supplicant wants to disconnect from the network after successful<br />

authentication, it sends an EAPOL-Logoff packet to the authenticator. The<br />

authenticator immediately moves the controlled port to the unauthorized state<br />

disabling the supplicant from accessing the network.<br />

Chapter 23. Port based network access control 897

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!