Sec User 8021x 12 4 Book
Sec User 8021x 12 4 Book
1X Authentication Services
Configuration Guide Cisco IOS Release
12.4
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED
WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL
FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR
ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output,
network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content
is unintentional and coincidental.
Table 1 Maximum Number of Clients That Can be Configured on a Local Authentication Server
Note Users that are associated to the local authentication server might notice a drop in performance during
authentication of client devices. However, if your wireless LAN contains only one access point, you can
configure that device as both the 802.1X authenticator and the local authentication server.
You configure access points and routers to use the local authentication server when they cannot reach the
main servers or when a RADIUS server is not available.
The access points and wireless-aware routers stop using the local authentication server automatically when
the link to the main servers is restored.
If your local authentication server also serves client devices, you must enter the local authentication server
access point or router as a network access server (NAS). When a LEAP client associates to the local
authentication server access point, the access point uses itself to authenticate the client.
Caution The access point or wireless-aware router that you use as an authentication server contains detailed
authentication information about your wireless LAN, so you should secure it physically to protect its
configuration.
SUMMARY STEPS
1. Router> enable
2. Router# configure terminal
3. Router(config)# aaa new-model
4. Router(config)# radius-server local
5. Router(config-radsrv)# nas ip-address key shared-key
DETAILED STEPS
Example:
Router> enable
Example:
Example:
Step 4 Router(config)# radius-server local Enables the access point or router as a local authentication server and
enters configuration mode for the authentication server.
Example:
Step 5 Router(config-radsrv)# nas ip-address key Adds an access point or wireless domain services (WDS) device to the list
shared-key of units that use the local authentication server. Enter the IP address of the
access point or WDS device, and the shared key used to authenticate
communication between the local authentication server and other access
Example: points. You must enter this shared key on the WDS devices that use the
local authentication server. Each access point and candidate WDS that uses
Router(config)# nas 192.168.12.17 key the local authentication server is a network access server (NAS).
shared256
If an access point is the local authentication server that also serves client
devices, you must enter the local authentication server access point as a
Example: NAS.
Note Leading spaces in the key string are ignored, but spaces within and
at the end of the key are used. If you use spaces in your key, do not
enclose the key in quotation marks unless the quotation marks are
part of the key.
Repeat this step to add each access point and candidate WDS device that
uses the local authentication server.
Note If you do not wish to configure user groups on the local authentication server, skip this task and go to the
Creating the User List on the Local Authentication_Server module.
SUMMARY STEPS
DETAILED STEPS
Step 2 Router(config-radsrv-group)# (Optional) Specifies a VLAN to be used by members of the user group. The access point
vlan vlan moves group members into that VLAN, overriding other VLAN assignments. You can
assign only one VLAN to the group.
Step 3 Router(config-radsrv-group)# (Optional) Enters up to 20 service set identifiers (SSIDs) to limit members of the user
ssid ssid group to those SSIDs. The access point checks whether the client’s SSID matches an
SSID in the list. If the SSID does not match, the client is disassociated.
Step 4 Router(config-radsrv-group)# (Optional) Configures the number of seconds after which access points should
reauthentication time reauthenticate members of the group. The reauthentication provides users with a new
seconds encryption key. The default setting is 0, which means that group members are never
required to reauthenticate.
Step 5 Router(config-radsrv-group)# (Optional) To help protect against password-guessing attacks, you can lock out group
block countcounttime members for a length of time after a set number of incorrect passwords.
{seconds | infinite}
• Count--The number of failed passwords that triggers a lockout of the username.
• Time--The number of seconds that the lockout should last. If you enter infinite, an
administrator must manually unblock the locked username. For more information,
see the Unblocking Usernames module.
Unblocking Usernames
You can unblock usernames before the lockout time expires or when the lockout time is set to infinite. To
unblock a locked username, enter the following command in privileged EXEC mode on the local
authentication server.
Note If you do not wish to configure users on the local authentication server, skip this task and go to the Saving
the Configuration on the Local Authentication Server module.
You must enter a username and password for each user. If you know only the NT hash value of the
password, which you can often find in the authentication server database, you can enter the NT hash as a
string of hexadecimal digits.
To add the user to a user group, enter the group name. If you do not specify a group, the user is not
assigned to a specific VLAN and is never forced to reauthenticate.
Beginning in local RADIUS server configuration mode, enter the user command for each username:
Router(config-radsrv)# user
username {password
| nthash
} password [group
group-name]
SUMMARY STEPS
1. Router(config-radsrv)# end
2. Router# copy running-config startup-config
DETAILED STEPS
Step 2 Router# copy running-config startup-config Saves your entries in the configuration file.
Note If your local authentication server access point also serves client devices, you must configure the local
authentication server to use itself to authenticate client devices.
On the wireless devices that use the local authentication server, use the radius-server host command in
privileged EXEC mode to enter the local authentication server as a RADIUS server. The order in which the
devices attempt to use the servers matches the order in which you enter the servers in the device
configuration. If you are configuring the device to use a RADIUS server for the first time, enter the main
RADIUS servers first, and enter the local authentication server last.
Note You must enter 1812 as the authentication port and 1813 as the accounting port. The local authentication
server listens on User Datagram Protocol (UDP) port 1813 for RADIUS accounting packets. It discards the
accounting packets but sends acknowledge packets back to the RADIUS clients to prevent the clients from
reacting as though the server is down.
Use the radius-server deadtime command in global configuration mode to set an interval during which the
access point or router does not attempt to use servers that do not respond, thus avoiding the wait for a
request to time out before trying the next configured server. A server marked as dead is skipped by
additional requests for the duration of minutes that you specify, up to 1440 (24 hours).
To remove the local authentication server from the access point or router configuration, use the no radius-
server host command in global configuration mode.
SUMMARY STEPS
1. Router> enable
2. Router# configure terminal
3. Router(config)# aaa new-model
4. Router(config)# radius-server host {hostname | ip-address } [auth-portport-number ] [acct-portport-
number ] [timeoutseconds ] [retransmitretries ] [keystring ]
5. aaa group server {radius | tacacs+} group-name
6. Router(config-sg-radius)# server ip-address auth-port 1812 acct-port 1813
7. Router(config)# aaa authentication loginnamed-authentication-list
8. Router(config)# end
9. Router# show running-config
10. Router# copy running-config startup-config
DETAILED STEPS
Step 3 Router(config)# aaa new-model Enables authentication, authorization, and accounting (AAA). This step must
be configured before the rest of the AAA configuration steps.
Step 4 Router(config)# radius-server host Specifies the IP address or hostname of the remote RADIUS server host.
{hostname | ip-address } [auth-portport-
• (Optional) For auth-port port-number, specify the UDP destination port
number ] [acct-portport-number ]
for authentication requests.
[timeoutseconds ] [retransmitretries ]
[keystring ] • (Optional) For acct-port port-number, specify the UDP destination port
for accounting requests.
• (Optional) For timeoutseconds , specify the time interval that the access
point waits for the RADIUS server to reply before retransmitting. The
range is 1 to 1000. This setting overrides the setting made using the
radius-server timeout command in global configuration mode. If no
timeout is set with the radius-server host command, the setting made
using the radius-server timeout command is used.
• (Optional) For retransmitretries , specify the number of times that a
RADIUS request is re-sent to a server if that server is not responding or
is responding slowly. The range is 1 to 1000. If no retransmit value is set
using the radius-server host command, the setting made using the
radius-server retransmit command in global configuration command
mode is used.
• (Optional) For keystring , specify the authentication and encryption key
used between the access point and the RADIUS daemon running on the
RADIUS server.
Note The key is a text string that must match the encryption key used on the
RADIUS server. Always configure the key as the last item in the
radius-server hostcommand. Leading spaces are ignored, but spaces
within and at the end of the key are used. If you use spaces in your key,
do not enclose the key in quotation marks unless the quotation marks
are part of the key.
To configure the access point to recognize more than one host entry
associated with a single IP address, enter this command as many times as
necessary, making sure to use a different UDP port number for each host. The
access point software searches for hosts in the order in which you specify
them. Set the timeout, retransmit, and encryption key values to use with the
specific RADIUS host.
Step 5 aaa group server {radius | tacacs+} Defines the AAA server-group with a group name.
group-name
Step 6 Router(config-sg-radius)# server ip- Defines the AAA server IP address, authentication port, and accounting port.
address auth-port 1812 acct-port 1813
Step 9 Router# show running-config Displays the current configuration for your verification.
Step 10 Router# copy running-config startup- (Optional) Saves your entries in the configuration file.
config
SUMMARY STEPS
1. Router> enable
2. Router# show running-config
DETAILED STEPS
Step 2 Router# show running-config Displays the current access point operating configuration
To reset local authentication server statistics to zero, enter the following command in privileged EXEC
mode:
• Setting Up Two Main Servers and a Local Authentication Server Example, page 10
• Displaying Local Authentication Server Configuration Example, page 11
• Displaying Local Authentication Server Statistics Example, page 12
In this example, if the WAN link to the main servers fails, the access point or wireless-aware router
completes these steps when a LEAP-enabled client device associates:
1 It tries the first server, times out multiple times, and marks the first server as dead.
2 It tries the second server, times out multiple times, and marks the second server as dead.
3 It tries and succeeds using the local authentication server.
If another client device needs to authenticate during the 10-minute deadtime interval, the access point skips
the first two servers and tries the local authentication server first. After the deadtime interval, the access
point tries to use the main servers for authentication. When setting a deadtime, you must balance the need
to skip dead servers with the need to check the WAN link and begin using the main servers again as soon as
possible.
Each time an access point or wireless-aware router tries to use the main servers while they are down, the
client device that is trying to authenticate might report an authentication timeout. The client device retries
and succeeds when the main servers time out and the access point or wireless-aware router tries the local
authentication server. You can extend the timeout value on Cisco client devices to accommodate expected
server timeouts.
!
interface FastEthernet1/1
switchport mode trunk
no ip address
!
interface FastEthernet1/2
no ip address
shutdown
!
interface FastEthernet1/3
no ip address
shutdown
!
interface FastEthernet1/4
no ip address
shutdown
!
interface FastEthernet1/5
no ip address
!
!
interface GigabitEthernet1/0
no ip address
shutdown
!
interface Vlan1
ip address 10.0.0.1 255.0.0.0
!
ip classless
!
ip http server
no ip http secure-server
!
!
!
radius-server local
nas 10.0.0.1 key 0 cisco
user ap-1 nthash 7 101B2A415547345A5F25790801706510064152425325720D7D04075D523D4F780A
user ap-5 nthash 7 144231535C540C7A77096016074B51332753030D0877705A264F450A09720A7307
user user1 nthash 7 1350344A5B5C227B78057B10107A452232515402097C77002B544B45087D0E7200
!
radius-server host 10.0.0.1 auth-port 1812 acct-port 1813
radius-server key cisco
!
wlccp authentication-server infrastructure AUTH_LEAP
wlccp authentication-server client leap AUTH_LEAP
wlccp wds priority 255 interface Vlan1
!
line con 0
line aux 0
line vty 0 4
!
!
!
end
The first section shows cumulative statistics from the local authentication server. The second section shows
statistics for each access point (NAS) that is authorized to use the local authentication server. The third
section shows statistics for individual users. If a user is blocked and the lockout time is set to infinite,
Blocked appears at the end of the line of statistics for that user. If the lockout time is not set to infinite,
Unblocked in x seconds appears at the end of the statistics line for that user.
Additional References
Related Documents
MIBs
Technical Assistance
Description Link
The Cisco Support and Documentation website http://www.cisco.com/cisco/web/support/
provides online resources to download index.html
documentation, software, and tools. Use these
resources to install and configure the software and
to troubleshoot and resolve technical issues with
Cisco products and technologies. Access to most
tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and
password.
Table 2 Feature Information for Remote Site IEEE 802.1X Local Authentication Service
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned are the property of their respective owners. The use of the word partner
does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be
actual addresses and phone numbers. Any examples, command display output, network topology diagrams,
and other figures included in the document are shown for illustrative purposes only. Any use of actual IP
addresses or phone numbers in illustrative content is unintentional and coincidental.
• The PCs connecting behind the router should have 802.1X clients running on them.
• You should know how to configure authentication, authorization, and accounting (AAA) and
RADIUS.
• You should be familiar with IP Security (IPSec).
• You should be familiar with Dynamic Host Configuration Protocol (DHCP).
• You should know how to configure user lists on a Cisco access control server (ACS).
On the router, the receipt of the EAPOL-Start message will result in the source MAC address being
“remembered,” and an EAPOL-request or identity PDU being sent to the host. The router will send all host-
addressed PDUs to the individual MAC address of the host rather than to the multicast address.
• 802.1X Authentication Sample Topology and Configuration, page 19
• Converged 802.1X Authenticator Support, page 19
• 802.1X Supplicant Support, page 19
• Converged 802.1X Supplicant Support, page 20
In the figure above, all the PCs are 802.1X capable hosts, and the Cisco router is an authenticator. All the
PCs are connected to the built-in hub or to an external hub. If a PC does not support 802.1X authentication,
MAC-based authentication is supported on the Cisco router. You can have any kind of connectivity or
network beyond the Cisco router WAN.
Note If there is a switch located between the router and the supplicant (client PC), the EAPOL frames will not
reach the router because the switch discards them.
• A supplicant is an entity at one end of a point-to-point LAN segment that is being authenticated by an
authenticator that is attached to the other end of that link.
network device be able to authenticate itself against another network device. The 802.1X supplicant
support functionality provides the following solutions for this requirement:
• An Extensible Authentication Protocol (EAP) framework has been included so that the supplicant has
the ability to “understand” and “respond” to EAP requests. EAP-Message Digest 5 (EAP-MD5) is
currently supported.
• Two network devices that are connected through an Ethernet link can act as a supplicant and as an
authenticator simultaneously, thus providing mutual authentication capability.
• A network device that is acting as a supplicant can authenticate itself with more than one authenticator
(that is, a single port on a supplicant can be connected to multiple authenticators).
The following illustration is an example of 802.1X supplicant support. The illustration shows that a single
supplicant port has been connected to multiple authenticators. Router A is acting as an authenticator to
devices that are sitting behind it on the LAN while those devices are acting as supplicants. At the same
time, Router B is an authenticator to Router A (which is acting as a supplicant). The RADIUS server is
located in the enterprise network.
When Router A tries to authenticate devices on the LAN, it needs to “talk” to the RADIUS server, but
before it can allow access to any of the devices that are sitting behind it, it has to prove its identity to
Router B. Router B checks the credential of Router A and gives access.
SUMMARY STEPS
1. Configure entries for the network access server and associated shared secrets.
2. Add the username and configure the password of the user.
3. Configure a global or per-user authentication scheme.
DETAILED STEPS
Step 1 Configure entries for the network access server and associated shared secrets.
Note The AAA server can be FreeRADIUS or Cisco Secure ACS or any other similar product with 802.1X support.
Step 2 Add the username and configure the password of the user.
Step 3 Configure a global or per-user authentication scheme.
Configuring a Router
• Enabling 802.1X Authentication, page 22
• Configuring Router and RADIUS Communication, page 24
• Configuring 802.1X Parameters Retransmissions and Timeouts, page 25
• Configuring the Identity Profile, page 28
• Configuring the Identity Profile, page 30
• Configuring the DHCP Private Pool, page 31
• Configuring the DHCP Public Pool, page 32
• Configuring the Interface, page 33
• Configuring an Interface Without Assigning an Explicit IP Address to the Interface, page 34
• Configuring the Necessary Access Control Policies, page 36
SUMMARY STEPS
1. enable
2. configure terminal
3. aaa new-model
4. aaa authentication dot1x {default | listname} method1 [method2...]
5. dot1x system-auth-control
6. identity profile default
7. interface type slot / port
8. dot1x port-control auto
DETAILED STEPS
Router> enable
Example:
Example:
Step 4 aaa authentication dot1x {default | listname} method1 Creates a series of authentication methods that are
[method2...] used to determine user previlege to access the
privileged command level.
Example:
Example:
Step 6 identity profile default Creates an identity profile and enters dot1x profile
configuration mode.
Example:
Step 7 interface type slot / port Enters interface configuration mode and specifies the
interface to be enabled for 802.1X port-based
authentication.
Example:
Example:
Examples
The following example shows that 802.1X authentication has been configured on a router:
TxPeriod = 60
RateLimitPeriod = 60
SUMMARY STEPS
1. enable
2. configure terminal
3. ip radius source-interface interface-name
4. radius-server host {hostname | ip-address}
5. radius-server key string
DETAILED STEPS
Router> enable
Example:
Step 3 ip radius source-interface interface-name Forces RADIUS to use the IP address of a specified interface for all
outgoing RADIUS packets.
Example:
Step 4 radius-server host {hostname | ip-address} Configures the RADIUS server host name or IP address of the router.
• To use multiple RADIUS servers, reenter this command for
each server.
Example:
Example
The following example shows that RADIUS server parameters have been configured on the router:
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot / port
4. dot1x max-req number-of-retries
5. dot1x port-control [auto| force-authorized| force-unauthorized]
6. dot1x control-direction {both | in}
7. dot1x reauthentication
8. dot1x timeout tx-period seconds
9. dot1x timeout server-timeout seconds
10. dot1x timeout reauth-period seconds
11. dot1x timeout quiet-period seconds
12. dot1x timeout ratelimit-period seconds
DETAILED STEPS
Router> enable
Example:
Step 3 interface type slot / port Enters interface configuration mode and specifies the interface to be
enabled for 802.1X port-based authentication.
Example:
Step 4 dot1x max-req number-of-retries Sets the maximum number of times that the router sends an EAP request/
identity frame (assuming that no response is received) to the supplicant
before concluding that the supplicant does not support 802.1X.
Example:
Step 5 dot1x port-control [auto| force-authorized| Sets the port control value.
force-unauthorized]
• auto (optional) --Authentication status of the supplicant will be
determined by the authentication process.
Example: • force-authorized (optional) --All the supplicants on the interface
will be authorized. The force-authorized keyword is the default.
Router (config-if)# dot1x port- • force-unauthorized (optional) --All the supplicants on the interface
control auto
will be unauthorized.
Step 6 dot1x control-direction {both | in} Changes the port control to unidirectional or bidirectional.
Example:
Step 7 dot1x reauthentication Enables periodic reauthentication of the supplicants on the interface.
• The reauthentication period can be set using the dot1x timeout
command.
Example:
Step 9 dot1x timeout server-timeout seconds Sets the timeout for RADIUS retries.
• If an 802.1X packet is sent to the server, and the server does not send
a response, the packet will be sent again after the time that was set
Example:
using the seconds argument.
Router (config-if)# dot1x timeout • The value is from 1 to 65535 seconds. The default is 30 seconds.
server-timeout 60
Step 10 dot1x timeout reauth-period seconds Sets the time after which an automatic reauthentication should be
initiated.
• The value is from 1 to 65535 seconds. The default is 3600 seconds.
Example:
Step 11 dot1x timeout quiet-period seconds The time after which authentication is restarted after the authentication
has failed.
• The value is from 1 to 65535 seconds. The default is 120 seconds.
Example:
Step 12 dot1x timeout ratelimit-period seconds The rate limit period throttles the EAP-START packets from
misbehaving supplicants.
• The value is from 1 to 65535 seconds.
Example:
Examples
The following configuration example shows that various retransmission and timeout parameters have been
configured:
SUMMARY STEPS
1. enable
2. configure terminal
3. identity profile default
4. description line-of-description
5. template virtual-template
6. device [authorize | not-authorize] mac-address mac-address
7. device authorize type device-type
DETAILED STEPS
Router> enable
Example:
Step 3 identity profile default Creates an identity profile and enters identity profile
configuration mode.
Example:
Example:
Step 5 template virtual-template Specifies the virtual template interface that will serve as
the configuration clone source for the virtual interface
that is dynamically created for authenticated users.
Example:
Step 6 device [authorize | not-authorize] mac-address mac-address Statically authorizes or unauthorizes a supplicant (by
giving its MAC address) if the supplicant does not
“understand” 802.1X.
Example:
Step 7 device authorize type device-type Statically authorizes or unauthorizes a device type.
Example:
Examples
The following example shows that Cisco IP phones and a specific MAC address have been statically
authorized:
SUMMARY STEPS
1. enable
2. configure terminal
3. identity profile default
4. description description-string
5. template virtual-template
6. exit
DETAILED STEPS
Router> enable
Example:
Example:
Example:
Step 5 template virtual-template Specifies the virtual template interface that will
serve as the configuration clone source for the
virtual interface that is dynamically created for
Example: authenticated users.
Example:
SUMMARY STEPS
DETAILED STEPS
Example:
Step 2 network network-number [mask] Configures the subnet number and mask for a DHCP
private address pool on a Cisco IOS DHCP server.
Example:
Step 3 default-router address Specifies the default router list for a DHCP client.
Example:
SUMMARY STEPS
DETAILED STEPS
Example:
Example:
Step 3 default-router address Specifies the default router list for a DHCP client.
Example:
Example:
SUMMARY STEPS
1. configure terminal
2. interface type slot / port
3. ip address ip-address mask [secondary]
4. interface virtual-template number
5. ip address ip-address mask [secondary]
6. exit
DETAILED STEPS
Example:
Example:
Step 3 ip address ip-address mask [secondary] Sets the private IP address for the interface.
Example:
Step 4 interface virtual-template number Creates a virtual template interface that can be
configured and applied dynamically in creating
virtual access interfaces.
Example:
Step 5 ip address ip-address mask [secondary] Sets the public IP address for the interface.
Example:
Example:
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot / port
4. ip unnumbered type number
DETAILED STEPS
Router# enable
Example:
Step 3 interface type slot / port Enters interface configuration mode and specifies the interface to
be enabled.
Example:
Step 4 ip unnumbered type number Enables IP processing on an interface without assigning an explicit
IP address to the interface.
Example:
Example
The following example shows that the identity profile associates virtual-template1 with unauthenticated
supplicants. Virtual-template1 gets its IP address from interface loopback 0, and unauthenticated
supplicants are associated with a public pool. Authenticated users are associated with a private pool.
SUMMARY STEPS
DETAILED STEPS
SUMMARY STEPS
1. Make sure that the PC has at least Service Pack 3.
2. Reboot your PC after installing the client.
3. Go to the Microsoft Windows registry and add or install the following entry:
4. Reboot your PC.
DETAILED STEPS
SUMMARY STEPS
1. Go to the Microsoft Windows registry and install the following entry there:
2. Reboot your PC.
DETAILED STEPS
Step 1 Go to the Microsoft Windows registry and install the following entry there:
“HKLM\Software\Microsoft\EAPOL\Parameters\General\Global\SupplicantMode REG_DWORD 3”
Step 2 Reboot your PC.
SUMMARY STEPS
1. Open the Network and Dial-up Connections window on your computer.
2. Right-click the Ethernet interface (Local Area Connection) to open the properties window. It should
have a tab called “Authentication.”
DETAILED STEPS
Step 1 Open the Network and Dial-up Connections window on your computer.
Step 2 Right-click the Ethernet interface (Local Area Connection) to open the properties window. It should have a tab called
“Authentication.”
Click the Authentication tab. Select the check box titled “Enable network access control using IEEE 802.1X.”
In a short period of time you should see a dialog box (for Windows 2000) or a floating window asking you to select it.
Select it, and when the next window appears, enter the username and password in this dialog box. See the figure
below.
SUMMARY STEPS
1. enable
2. configure terminal
3. aaa authentication dot1x {default | listname} method1 [method2...]
4. dot1x credentials name
5. username name
6. password [0 | 7] password
7. exit
8. interface type number
9. dot1x pae supplicant
10. dot1x credentials name
11. end
DETAILED STEPS
Router> enable
Example:
Step 3 aaa authentication dot1x {default | listname} method1 Specifies one or more authentication, authorization,
[method2...] and accounting (AAA) methods for use on interfaces
running IEEE 802.1X.
Example:
Step 4 dot1x credentials name Specifies the 802.1X credential profile to use when
configuring a supplicant.
Example:
Example:
Example:
Example:
Router(config-dot1x-creden)# exit
Example:
Step 9 dot1x pae supplicant Sets the Port Access Entity (PAE) type as supplicant.
Example:
Step 10 dot1x credentials name Specifies the 802.1X credential profile to use when
configuring a supplicant.
Example:
Example:
Router(config-if)# end
Troubleshooting Tips
Use the debug commands in the Monitoring VPN Access Control Using 802.1X Authentication section to
debug the supplicant.
SUMMARY STEPS
1. enable
2. clear dot1x {all | interface}
3. clear eap sessions [credentials credentials-name | interface interface-name | method method-name |
transporttransport-name]]
4. debug dot1x [ all | errors | events | feature | packets | redundancy | registry | state-machine ]
5. debug eap [all | method] [authenticator | peer] {all | errors | events | packets | sm}
6. dot1x initialize [interface interface-name]
7. dot1x re-authenticate interface-type interface-number
DETAILED STEPS
Router> enable
Example:
Step 3 clear eap sessions [credentials credentials-name | interface Clears EAP information on a switch or for a specified
interface-name | method method-name | transporttransport- port.
name]]
Example:
Step 5 debug eap [all | method] [authenticator | peer] {all | errors | Displays information about EAP.
events | packets | sm}
Example:
Example:
Step 7 dot1x re-authenticate interface-type interface-number Reauthenticates all the authenticated devices that are
attached to the specified interface.
Example:
SUMMARY STEPS
1. enable
2. show dot1x [interface interface-name[details]]
3. show eap registrations [method | transport]
4. show eap sessions [credentials credentials-name | interfaceinterface-name | method method-name |
transport transport-name]
DETAILED STEPS
Router> enable
Step 2 show dot1x [interface interface-name[details]] Shows details for an identity profile.
Example:
Step 3 show eap registrations [method | transport] Displays EAP registration information.
Example:
Step 4 show eap sessions [credentials credentials-name | interfaceinterface-name | Displays active EAP session
method method-name | transport transport-name] information.
Example:
Router
template Virtual-Template1
!
!
!
!
!
archive
log config
hidekeys
!
!
!
!
!
interface Loopback0
ip address 209.165.200.227 255.255.255.224
!
interface FastEthernet0
!
interface FastEthernet1
dot1x pae authenticator
dot1x port-control auto
dot1x timeout quiet-period 600
dot1x timeout server-timeout 60
dot1x timeout reauth-period 1800
dot1x timeout tx-period 60
dot1x timeout ratelimit-period 60
dot1x max-req 3
dot1x reauthentication
!
interface FastEthernet2
!
interface FastEthernet3
!
interface FastEthernet4
no ip address
shutdown
duplex auto
speed auto
!
interface Virtual-Template1
ip unnumbered Loopback0
!
interface Dot11Radio0
no ip address
shutdown
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0
station-role root
no cdp enable
!
interface Vlan1
ip address 209.165.200.228 255.255.255.224
!
ip default-gateway 192.0.2.10
ip default-network 192.0.2.11
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 192.0.2.11
ip route 209.165.200.229 255.255.255.224 192.0.2.12
no ip http server
no ip http secure-server
!
!
ip radius source-interface FastEthernet1
!
!
!
radius-server host 192.0.2.9 auth-port 1645 acct-port 1646
radius-server key radiuskey
!
control-plane
!
!
line con 0
exec-timeout 30 0
logging synchronous
no modem enable
line aux 0
line vty 0 4
privilege level 15
password lab
!
scheduler max-task-time 5000
end
!
interface ATM1/0
ip address 209.165.200.233 255.255.255.224
no atm ilmi-keepalive
pvc 1/43
protocol ip 192.0.2.6 broadcast
encapsulation aal5snap
!
!
interface FastEthernet2/0
no ip address
speed auto
full-duplex
!
interface FastEthernet2/1
no ip address
shutdown
duplex auto
speed auto
!
interface Virtual-Template1
ip address 209.165.200.234 255.255.255.224
ip mtu 1492
crypto map test
!
!
router rip
network 192.0.2.5
network 192.0.2.4
network 192.0.2.3
network 192.0.2.2
network 192.0.2.1
!
ip http server
no ip http secure-server
ip classless
!
access-list 101 permit ip 10.5.0.0 0.0.0.255 10.0.0.1 0.0.0.255
no cdp log mismatch duplex
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
login
!
!
end
Additional References
Related Documents
User lists on a Cisco ACS User Guide for Cisco Secure ACS for Windows
Server Version 3.2.
Standards
Standard Title
IEEE 802.1X protocol --
MIBs
RFCs
RFC Title
RFC-2284 RFC 2284 (PPP Extensible Authentication Protocol
[EAP]) document from The Internet Requests for
Comments (RFC) document series
Technical Assistance
Description Link
The Cisco Support and Documentation website http://www.cisco.com/cisco/web/support/
provides online resources to download index.html
documentation, software, and tools. Use these
resources to install and configure the software and
to troubleshoot and resolve technical issues with
Cisco products and technologies. Access to most
tools on the Cisco Support and Documentation
website requires a Cisco.com user ID and
password.
Table 3 Feature Information for VPN Access Control Using 802.1X Authentication
VPN Access Control Using 12.3(4)T This feature was integrated into
802.1X Authentication Cisco IOS Release 12.3(4)T, and
the following platform support
was added: Cisco 1751, Cisco
2610XM - Cisco 2611XM, Cisco
2620XM - Cisco 2621XM, Cisco
2650XM - Cisco 2651XM, Cisco
2691, Cisco 3640, Cisco 3640A,
and Cisco 3660.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S.
and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks.
Third-party trademarks mentioned are the property of their respective owners. The use of the word partner
does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be
actual addresses and phone numbers. Any examples, command display output, network topology diagrams,
and other figures included in the document are shown for illustrative purposes only. Any use of actual IP
addresses or phone numbers in illustrative content is unintentional and coincidental.