＋设为首页 ＋添加到收藏夹
understanding 802.1x port-based authentication
until the client is authenticated, 802.1x access control allows only extensible authentication protocol over lan (eapol) traffic through the port to which the client is connected. after authentication is successful, normal traffic can pass through the port. 【程序编程相关:实战破解交换机密码】 the authentication server authenticates each client connected to a switch port before making available any services offered by the switch or the lan. 【推荐阅读:Pix515防火墙配置策略实例分析】• device roles 【扩展信息:auto secure命令的使用】these sections describe 802.1x port-based authentication: • authentication initiation and message exchange • ports in authorized and unauthorized states • voice vlan ports • using 802.1x with port security • using 802.1x with per-user acls • using 802.1x with vlan assignment • supported topologies device roles with 802.1x port-based authentication, the devices in the network have specific roles as shown in figure 9-1. figure 9-1 802.1x device roles 560)this.style.width=560; onmousewheel = javascript:return big(this) id=wp1042452 height=172 hspace=0 src="http://www.net130.com/cms/files/uploadimages/74615.jpg" width=576 border=0>•client—the device (workstation) that requests access to the lan and switch services and responds to requests from the switch.the workstation must be running 802.1x-compliant client software such as that offered in the microsoft windows xp operating system. (the client is the supplicant in the ieee 802.1x specification.) note to resolve windows xp network connectivity and 802.1x authentication issues, read the microsoft knowledge base article at this url: http://support.microsoft.com/support/kb/articles/q303/5/97.asp •authentication server—performs the actual authentication of the client. the authentication server validates the identity of the client and notifies the switch whether or not the client is authorized to access the lan and switch services. because the switch acts as the proxy, the authentication service is transparent to the client. in this release, the remote authentication dial-in user service (radius) security system with extensible authentication protocol (eap) extensions is the only supported authentication server; it is available in cisco secure access control server version 3.0. radius operates in a client/server model in which secure authentication information is exchanged between the radius server and one or more radius clients. •switch (edge switch or wireless access point)—controls the physical access to the network based on the authentication status of the client. the switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client. the switch includes the radius client, which is responsible for encapsulating and decapsulating the eap frames and interacting with the authentication server. when the switch receives eapol frames and relays them to the authentication server, the ethernet header is stripped and the remaining eap frame is re-encapsulated in the radius format. the eap frames are not modified or examined during encapsulation, and the authentication server must support eap within the native frame format. when the switch receives frames from the authentication server, the servers frame header is removed, leaving the eap frame, which is then encapsulated for ethernet and sent to the client. the devices that can act as intermediaries include the catalyst 3550 multilayer switch, the catalyst 2950 switch, the catalyst 2955 switch, or a wireless access point. these devices must be running software that supports the radius client and 802.1x. authentication initiation and message exchange the switch or the client can initiate authentication. if you enable authentication on a port by using the dot1x port-control auto interface configuration command, the switch must initiate authentication when it determines that the port link state transitions from down to up. it then sends an eap-request/identity frame to the client to request its identity (typically, the switch sends an initial identity/request frame followed by one or more requests for authentication information). upon receipt of the frame, the client responds with an eap-response/identity frame. however, if during bootup, the client does not receive an eap-request/identity frame from the switch, the client can initiate authentication by sending an eapol-start frame, which prompts the switch to request the clients identity. note if 802.1x is not enabled or supported on the network access device, any eapol frames from the client are dropped. if the client does not receive an eap-request/identity frame after three attempts to start authentication, the client sends frames as if the port is in the authorized state. a port in the authorized state effectively means that the client has been successfully authenticated. for more information, see the "ports in authorized and unauthorized states" section. when the client supplies its identity, the switch begins its role as th... 下一页