
Figure 8. EAP Frames Encapsulated in Ethernet and RADUIS
The authentication process involves three devices:
•
The device attempting to access the network is the
supplicant
. The supplicant is not allowed to communicate on the network
until the authenticator authorizes the port. It can only communicate with the authenticator in response to 802.1X requests.
•
The device with which the supplicant communicates is the
authenticator
. The authenticator is the gate keeper of the network.
It translates and forwards requests and responses between the authentication server and the supplicant. The authenticator also
changes the status of the port based on the results of the authentication process. The Dell Networking switch is the
authenticator.
•
The authentication-server selects the authentication method, verifies the information the supplicant provides, and grants it
network access privileges.
Ports can be in one of two states:
•
Ports are in an
unauthorized
state by default. In this state, non-802.1X traffic cannot be forwarded in or out of the port.
•
The authenticator changes the port state to authorized if the server can authenticate the supplicant. In this state, network
traffic can be forwarded normally.
NOTE: The Dell Networking switches place 802.1X-enabled ports in the unauthorized state by default.
Port-Authentication Process
The authentication process begins when the authenticator senses that a link status has changed from down to up:
1.
When the authenticator senses a link state change, it requests that the supplicant identify itself using an EAP Identity Request
frame.
2.
The supplicant responds with its identity in an EAP Response Identity frame.
3.
The authenticator decapsulates the EAP response from the EAPOL frame, encapsulates it in a RADIUS Access-Request frame
and forwards the frame to the authentication server.
4.
The authentication server replies with an Access-Challenge frame. The Access-Challenge frame requests the supplicant to
prove that it is who it claims to be, using a specified method (an EAP-Method). The challenge is translated and forwarded to
the supplicant by the authenticator.
5.
The supplicant can negotiate the authentication method, but if it is acceptable, the supplicant provides the Requested
Challenge information in an EAP response, which is translated and forwarded to the authentication server as another Access-
Request frame.
94
802.1X
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...