Table of Contents
Advertisement
Configuring Port-Based and Client-Based Access Control (802.1X)
Configuring Switch Ports To Operate As Supplicants for 802.1X Connections to Other Switches
Port A1
Switch "A"
Port A1 Configured as an
802.1X Supplicant
Figure 9-7. Example of Supplicant Operation
9-46
Example
Suppose that you want to connect two switches, where:
■
Switch "A" has port A1 configured for 802.1X supplicant operation.
You want to connect port A1 on switch "A" to port B5 on switch "B".
■
1.
When port A1 on switch "A" is first connected to a port on switch "B", or
if the ports are already connected and either switch reboots, port A1
begins sending start packets to port B5 on switch "B".
•
If, after the supplicant port sends the configured number of start
packets, it does not receive a response, it assumes that switch "B" is
not 802.1X-aware, and transitions to the authenticated state. If switch
"B" is operating properly and is not 802.1X-aware, then the link should
begin functioning normally, but without 802.1X security.
•
If, after sending one or more start request packets, port A1 receives
a request packet from port B5, then switch "B" is operating as an
802.1X authenticator. The supplicant port then sends a response/ID
packet. If switch "B" is configured for RADIUS authentication, it
forwards this request to a RADIUS server. If switch "B" is configured
for Local 802.1X authentication, the authenticator compares the
switch "A" response to its local username and password.
2.
The RADIUS server then responds with an MD5 access challenge that
switch "B" forwards to port A1 on switch "A".
3.
Port A1 replies with an MD5 hash response based on its username and
password or other unique credentials. Switch "B" forwards this response
to the RADIUS server.
Switch "B"
Port B5
LAN Core
RADIUS Server
Advertisement
Table of Contents
