Publication date:Oct., 2012
Revision A2
171
The overview of operation flow for the Fig. 3-53 is quite simple. When
Supplicant PAE issues a request to Authenticator PAE, Authenticator and
Supplicant exchanges authentication message. Then, Authenticator
passes the request to RADIUS server to verify. Finally, RADIUS server
replies if the request is granted or denied.
While in the authentication process, the message packets, encapsulated
by Extensible Authentication Protocol over LAN (EAPOL), are exchanged
between an authenticator PAE and a supplicant PAE. The Authenticator
exchanges the message to authentication server using EAP
encapsulation. Before successfully authenticating, the supplicant can
only touch the authenticator to perform authentication message
exchange or access the network from the uncontrolled port.
Fig. 3-53
In the Fig. 3-54, this is the typical configuration, a single supplicant, an
authenticator and an authentication server. B and C is in the internal network, D is
Authentication server running RADIUS, switch at the central location acts
Authenticator connecting to PC A and A is a PC outside the controlled port, running
Supplicant PAE. In this case, PC A wants to access the services on device B and C,
first, it must exchange the authentication message with the authenticator on the port
it connected via EAPOL packet. The authenticator transfers the supplicant’s
credentials to Authentication server for verification. If success, the authentication
server will notice the authenticator the grant. PC A, then, is allowed to access B and
C via the switch. If there are two switches directly connected together instead of
single one, for the link connecting two switches, it may have to act two port roles at
the end of the link: authenticator and supplicant, because the traffic is bi-directional.
Fig. 3-54
Summary of Contents for 065-7851
Page 1: ......
Page 2: ......
Page 62: ...Publication date Oct 2012 Revision A2 60 Fig 3 12 ...
Page 101: ...Publication date Oct 2012 Revision A2 99 Fig 3 34 ...
Page 104: ...Publication date Oct 2012 Revision A2 102 Fig 3 37 Fig 3 38 Fig 3 39 ...
Page 105: ...Publication date Oct 2012 Revision A2 103 Fig 3 40 Fig 3 41 ...
Page 106: ...Publication date Oct 2012 Revision A2 104 Fig 3 42 ...
Page 121: ...Publication date Oct 2012 Revision A2 119 Fig 3 61 Set up VLAN Tag Priority Mapping ...
Page 122: ...Publication date March 2011 Revision A1 120 Fig 3 62 Set up VLAN Tag Priority Mapping Finish ...
Page 136: ...Publication date Oct 2012 Revision A2 134 Fig 3 69 Frame Type Fig 3 70 ...
Page 137: ...Publication date Oct 2012 Revision A2 135 Fig 3 71 Fig 3 72 Fig 3 73 ARP ...
Page 138: ...Publication date Oct 2012 Revision A2 136 Fig 3 74 ARP Fig 3 75 ARP Fig 3 76 ARP Fig 3 77 ARP ...
Page 139: ...Publication date Oct 2012 Revision A2 137 Fig 3 79 ARP Fig 3 80 ARP Fig 3 81 ARP ...
Page 141: ...Publication date Oct 2012 Revision A2 139 Fig 3 87 ARP Fig 3 88 IPv4 ...
Page 145: ...Publication date Oct 2012 Revision A2 143 Fig 3 103 IPv4 Fig 3 104 IPv4 Fig 3 105 IPv4 ...
Page 146: ...Publication date Oct 2012 Revision A2 144 Fig 3 106 IPv4 Fig 3 107 IPv4 Fig 3 108 IPv4 ...
Page 147: ...Publication date Oct 2012 Revision A2 145 Fig 3 109 IPv4 Fig 3 110 IPv4 Fig 3 111 IPv4 ...
Page 148: ...Publication date Oct 2012 Revision A2 146 Fig 3 112 IPv4 Fig 3 113 IPv4 Fig 3 114 IPv4 ...
Page 149: ...Publication date Oct 2012 Revision A2 147 Fig 3 115 IPv4 Fig 3 116 IPv4 Fig 3 117 IPv4 ...
Page 150: ...Publication date Oct 2012 Revision A2 148 Fig 3 118 Action Fig 3 119 Rate Limiter ...
Page 151: ...Publication date Oct 2012 Revision A2 149 Fig 3 120 Port Copy Fig 3 121 DMAC Filter ...
Page 250: ...Publication date Oct 2012 Revision A2 248 Fig 4 1 Fig 4 2 ...