The home access router provides connectivity to the corporate network through a Virtual Private Network (VPN) tunnel through the Internet. In the home LAN, apart from the employee, other members of the household may also be using the same access router. The VPN Access Control Using 802.1X Authentication feature allows enterprise employees to access their enterprise networks from home while allowing other household members to access only the Internet. The feature uses the IEEE 802.1X protocol framework to achieve the VPN access control. The authenticated employee has access to the VPN tunnel and others (unauthenticated users on the same LAN) have access only to the Internet.
An authentication manager has been added to allow more flexible authentication between different authentication methods like, dot1x, MAC address bypass, and web authentication. See the 802.1X Flexible Authentication feature for more information.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for VPN Access Control Using 802.1X Authentication
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).
Restrictions for VPN Access Control Using 802.1X Authentication
Easy VPN is not supported.
VLAN interfaces are currently not supported.
If there is a switch located between the router and the supplicant (client PC), the Extensible Authentication Protocol over LAN (EAPOL) frames will not reach the router because the switch discards them.
Information About VPN Access Control Using 802.1X Authentication
The home access router provides connectivity to the corporate network through a VPN tunnel through the Internet. In the home LAN, both authenticated (employee) and unauthenticated (other household members) users exist, and both have access to the corporate VPN tunnel. Currently there is no existing mechanism to prevent the unauthenticated user from accessing the VPN tunnel.
To distinguish between the users, the VPN Access Control Using 802.1X Authentication feature uses the IEEE 802.1X protocol that allows end hosts to send user credentials on Layer 2 of the network operating system. Unauthenticated traffic users will be allowed to pass through the Internet but will be blocked from accessing the corporate VPN tunnel. The VPN Access Control Using 802.1X feature expands the scope of the 802.1X standard to authenticate devices rather than ports, meaning that multiple devices can be independently authenticated for any given port. This feature separates traffic from authenticated and unauthenticated users so that separate access policies can be applied.
When an 802.1X-capable host starts up, it will initiate the authentication phase by sending the EAPOL-Start 802.1X protocol data unit (PDU) to the reserved IEEE multicast MAC address (01-80-C2-00-00-03) with the Ethernet type or length set to 0x888E.
All 802.1X PDUs will be identified as such by the Ethernet driver and will be enqueued to be handled by an 802.1X process. On some platforms, Ethernet drivers have to program the interface address filter so that EAPOL packets can be accepted.
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
The figure below illustrates a typical scenario in which VPN access control using 802.1X authentication is in place.
Figure 1
Typical 802.1X Authentication Setup
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.
Converged 802.1X Authenticator Support
The Cisco IOS commands in Cisco IOS Release 12.4(6)T for 802.1X authenticators have been standardized to work the same way on various Cisco IOS platforms.
802.1X Supplicant Support
There are deployment scenarios in which a network device (a router
acting as an 802.1X authenticator) is placed in an unsecured location and
cannot be trusted as an authenticator. This scenario requires that a 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.
Figure 2
Multiple Instances of Supplicant Support
Converged 802.1X Supplicant Support
The Cisco IOS commands in Cisco IOS Release 12.4(6)T for 802.1X supplicants have been standardized to work the same way on various Cisco IOS platforms. See the Configuring a Router As an 802.1X Supplicant module.
Authentication Using Passwords and MD5
For information about using passwords and Message Digest 5 (MD5), see the following document on Cisco.com:
Improving Security on Cisco Routers
How to Configure VPN Access Control Using 802.1X Authentication
To enable 802.1X port-based authentication, you should configure the router so that it can communicate with the AAA server, enable 802.1X globally, and enable 802.1X on the interface. To enable 802.1X port-based authentication, perform the following steps.
Configuring 802.1X Parameters Retransmissions and Timeouts
Various 802.1X retransmission and timeout parameters can be configured. Because all of these parameters have default values, configuring them is optional. To configure the retransmission and timeout parameters, perform the following steps.
Enters interface configuration mode and specifies the interface to be enabled for 802.1X port-based authentication.
Step 4
dot1xmax-reqnumber-of-retries
Example:
Router (config-if)# dot1x max-req 3
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.
auto(optional)--Authentication status of the supplicant will be determined by the authentication process.
force-authorized(optional)--All the supplicants on the interface will be authorized. The
force-authorized keyword is the default.
force-unauthorized(optional)--All the supplicants on the interface will be unauthorized.
Step 6
dot1xcontrol-direction {both |
in}
Example:
Router (config-if)# dot1x control-direction both
Changes the port control to unidirectional or bidirectional.
Step 7
dot1xreauthentication
Example:
Router (config-if)# dot1x reauthentication
Enables periodic reauthentication of the supplicants on the interface.
The reauthentication period can be set using thedot1xtimeout command.
Step 8
dot1xtimeouttx-periodseconds
Example:
Router (config-if)# dot1x timeout tx-period 60
Sets the timeout for supplicant retries.
If an 802.1X packet is sent to the supplicant and the supplicant does not send a response, the packet will be sent again after the time that was set using the seconds
argument.
The value is 1 through 65535 seconds. The default is 30 seconds.
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 using the
seconds argument.
The value is from 1 to 65535 seconds. The default is 30 seconds.
The rate limit period throttles the EAP-START packets from misbehaving supplicants.
The value is from 1 to 65535 seconds.
Examples
The following configuration example shows that various retransmission and timeout parameters have been configured:
Router# configureterminal
Router(config)# interfaceFastEthernet1
Router(config-if)# dot1xport-controlauto
Router(config-if)#dot1xreauthentication
Router(config-if)# dot1xtimeoutreauth-period1800
Router(config-if)# dot1xtimeoutquiet-period600
Router(config-if)# dot1xtimeoutsupp-timeout60
Router(config-if)# dot1xtimeoutserver-timeout60
Configuring the Identity Profile
The
identityprofiledefaultcommand allows you to configure the static MAC addresses of the client that do not support 802.1X and to authorize or unauthorize them statically. The VPN Access Control Using 802.1X Authentication feature allows authenticated and unauthenticated users to be mapped to different interfaces. Under the
dot1xprofile configuration mode, you can specify the virtual template interface that should be used to create the virtual-access interface to which unauthenticated supplicants will be mapped. To specify which virtual template interface should be used to create the virtual access interface, perform the following steps.
Specifies the virtual template interface that will serve as the configuration clone source for the virtual interface that is dynamically created for authenticated users.
Specifies the virtual template interface that will serve as the
configuration clone source for the virtual interface that is dynamically
created for authenticated users.
Step 6
exit
Example:
Router (config-template)# exit
Exits identity profile configuration mode.
Configuring the DHCP Private Pool
The VPN Access Control Using 802.1X Authentication feature can be
configured with one DHCP pool or two. If there are two pools, the
unauthenticated and authenticated devices will get their addresses from
separate DHCP pools. For example, the public pool can have an address block
that has only local significance, and the private pool can have an address that
is routable over the VPN tunnel.
SUMMARY STEPS
1.ipdhcppoolname
2.networknetwork-number
[mask]
3.default-routeraddress
DETAILED STEPS
Command or Action
Purpose
Step 1
ipdhcppoolname
Example:
Router (config)# ip dhcp pool private
Configures a DHCP private address pool on a Cisco IOS DHCP server
and enters DHCP pool configuration mode.
Configures the subnet number and mask for a DHCP private address
pool on a Cisco IOS DHCP server.
Step 3
default-routeraddress
Example:
Router (dhcp-config)# default-router 192.0.2.2
Specifies the default router list for a DHCP client.
Configuring the DHCP Public Pool
The VPN Access Control Using 802.1X Authentication feature can be
configured with one DHCP pool or two. If there are two pools, the
unauthenticated and authenticated devices will get their addresses from
separate DHCP pools. For example, the public pool can have an address block
that has only local significance, and the private pool can have an address that
is routable over the VPN tunnel.
SUMMARY STEPS
1.ipdhcppoolname
2.networknetwork-number [mask]
3.default-routeraddress
4.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
ipdhcppoolname
Example:
Router (config-dhcp)# ip dhcp pool public
Configures the DHCP public address pool on a Cisco IOS DHCP
server.
Configures the subnet number and mask for a DHCP public address
pool on a Cisco IOS DHCP server.
Step 3
default-routeraddress
Example:
Router (config-dhcp)# default-router 192.0.2.3
Specifies the default router list for a DHCP client.
Step 4
exit
Example:
Router (config-dhcp)# exit
Exits DHCP pool configuration mode.
Configuring the Interface
SUMMARY STEPS
1.configureterminal
2.interfacetypeslot/port
3.ipaddressip-addressmask [secondary]
4.interfacevirtual-templatenumber
5.ipaddressip-addressmask [secondary]
6.exit
DETAILED STEPS
Command or Action
Purpose
Step 1
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 2
interfacetypeslot/port
Example:
Router (config)# interface loopback 0/1
Enters interface configuration mode and specifies the interface
to be enabled.
Step 3
ipaddressip-addressmask [secondary]
Example:
Router (config-if)# ip address 209.165.200.227 255.255.255.224
Sets the private IP address for the interface.
Step 4
interfacevirtual-templatenumber
Example:
Router (config-if)# interface virtual-template 1
Creates a virtual template interface that can be configured and
applied dynamically in creating virtual access interfaces.
Step 5
ipaddressip-addressmask [secondary]
Example:
Router (config-if)# ip address 209.165.200.227 255.255.255.224
Sets the public IP address for the interface.
Step 6
exit
Example:
Router (config-if)# exit
Exits interface configuration mode.
Configuring an Interface Without Assigning an Explicit IP Address to the Interface
SUMMARY STEPS
1.enable
2.configureterminal
3.interfacetypeslot/port
4.ipunnumberedtypenumber
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router# enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
interfacetypeslot/port
Example:
Router (config)# interface virtual-template 1
Enters interface configuration mode and specifies the interface to be enabled.
Step 4
ipunnumberedtypenumber
Example:
Router (config-if)# ip unnumbered loopback 0
Enables IP processing on an interface without assigning an explicit IP address to the interface.
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.
Router(config)# identity profile default
Router(config-identity-prof)# description put the description here
Router(config-identity-prof)# template virtual-template1
Router(config-identity-prof)# exit
Router(config)# ip dhcp pool private
Router(dhcp-config)# default-router 192.0.2.0
Router(dhcp-config)# exit
Router(config)#ip dhcp pool public
Router(dhcp-config)# default-router 192.0.2.1
Router(dhcp-config)# exit
Router(config)# interface
Router(dhcp-config)# network 209.165.200.225 255.255.255.224
Router(dhcp-config)# default-router 192.0.2.1
Router(dhcp-config)# exit
Router(config)# interface loopback0
Router(config-if)# interface ethernet0
Router(config-if)# ip address 209.165.200.226 255.255.255.224
Router(config-if)# exit
Router(config)# interface virtual-template1
Router(config-if)# ip unnumbered loopback 0
Configuring the Necessary Access Control Policies
802.1X authentication separates traffic from authenticated and unauthenticated devices. Traffic from authenticated devices transit through the physical interface, and unauthenticated traffic transits through the Virtual-Template1. Therefore, different policies can be applied on each interface. The configuration will also depend on whether two DHCP pools or a single DHCP pool is being used. If a single DHCP pool is being used, access control can be configured on Virtual-Template1, which will block any traffic from going to the networks to which unauthenticated devices should not have access. These networks (to which unauthenticated devices should not have access) could be the corporate subnetworks protected by the VPN or encapsulated by generic routing encapsulation (GRE). There can also be access control that restricts the access between authenticated and unauthenticated devices.
If two pools are configured, the traffic from a non-trusted pool is routed to the Internet using Network Address Translation (NAT), whereas trusted pool traffic is forwarded through a VPN tunnel. The routing can be achieved by configuring ACLs used by NAT and VPN accordingly.
For an example of an access control policy configuration, see the Access Control Policies Example section.
Configuring a PC for VPN Access Control Using 802.1X Authentication
To configure your PC for VPN Access Control Using 802.1X Authentication, perform the following steps.
SUMMARY STEPS
1.
Enable 802.1X for MD5.
2.
Enable DHCP.
DETAILED STEPS
Step 1
Enable 802.1X for MD5.
Step 2
Enable DHCP.
Enabling 802.1X Authentication on a Windows 2000 XP PC
802.1X implementation on a Windows 2000/XP PC is unstable. A more stable 802.1X client, AEGIS (beta) for Microsoft Windows, is available at the Meetinghouse Data Communications website at www.mtghouse.com.
Enabling 802.1X Authentication on a Windows 2000 PC
To enable 802.1X authentication on your Windows 2000 PC, perform the following 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
Step 1
Make sure that the PC has at least Service Pack 3.
Go to the page "Microsoft 802.1x Authentication Client" on the Microsoft Windows 2000 website at the following URL:
At the above site, download and install 802.1X client for Windows 2000.
If the above site is unavailable, search for the "Q313664: Recommended Update" page on the Microsoft Windows 2000 website at the following URL: http://www.microsoft.com/windows2000/downloads/recommended/q313664/default.asp
Step 2
Reboot your PC after installing the client.
Step 3
Go to the Microsoft Windows registry and add or install the following entry:
("SupplicantMode" key entry is not there by default under Global option in the registry. So add a new entry named "SupplicantMode" as REG_DOWORD and then set its value to 3.)
Step 4
Reboot your PC.
Enabling 802.1X Authentication on a Windows XP PC
To enable 802.1X authentication on a Windows XP PC, perform the following 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:
Enabling 802.1X Authentication on Windows 2000 and Windows XP PCs
To enable 802.1X authentication on Windows 2000 and Windows XP PCs, that is, if you are operating both at the same time, perform the following steps.
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.
What to Do Next
Figure 3
Local Area Connection Properties Window
Configuring a Router As an 802.1X Supplicant
To configure a router as an 802.1X supplicant, perform the following steps.
Use the debug commands in the Monitoring VPN Access Control Using 802.1X Authentication section to debug the supplicant.
Monitoring VPN Access Control Using 802.1X Authentication
To monitor VPN Access Control Using 802.1X Authentication, perform the following steps. The commands shown in the steps may be used one at a time and in no particular order.
Typical VPN Access Control Using 802.1X Configuration Example
The following sample output shows that VPN access control using 802.1X authentication has been configured. Output is shown for the router and for the gateway.
Router
Router# show running-config
Building configuration...
Current configuration : 2457 bytes
!
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname 871-1
!
boot-start-marker
boot-end-marker
!
logging message-counter syslog
!
aaa new-model
!
!
aaa authentication dot1x default group radius group radius
!
!
aaa session-id common
!
!
dot11 syslog
ip source-route
!
ip dhcp pool private
network 209.165.200.225 255.255.255.224
default-router 192.0.2.18
!
ip dhcp pool public
network 209.165.200.226 255.255.255.224
default-router 192.0.2.17
!
ip dhcp pool name
default-router 192.0.2.16
!
!
ip cef
no ip domain lookup
ip host sjc-tftp02 192.0.2.15
ip host sjc-tftp01 192.0.2.14
ip host dirt 192.0.2.13
!
!
!
template virtualtemplate1
!
dot1x system-auth-control
dot1x credentials basic-user
description This credentials profile should be used for most configured ports
username router1
password 0 secret
!
identity profile default
description description 1
device authorize mac-address 0001.024b.b4e7
device authorize mac-address 0001.0001.0001
device authorize type cisco ip phone
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
Peer Router As Gateway
Router# show running-config
Building configuration...
Current configuration: 1828 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname c3725
!
!
no aaa new-model
ip subnet-zero
!
vpdn enable
!
vpdn-group 1
accept-dialin
protocol pppoe
virtual-template 1
!
mpls ldp logging neighbor-changes
!
crypto isakmp policy 1
authentication pre-share
crypto isakmp key 0 test address 192.0.2.8
!
!
crypto ipsec transform-set t1 ah-md5-hmac esp-des
crypto mib ipsec flowmib history tunnel size 2
crypto mib ipsec flowmib history failure size 2
!
crypto map test 1 ipsec-isakmp
set peer 192.0.2.7
set transform-set t1
match address 101
!
no voice hpi capture buffer
no voice hpi capture destination
!
interface Loopback0
description corporate
ip address 209.165.200.230 255.255.255.224
!
interface Loopback1
description internet
ip address 209.165.200.231 255.255.255.224
!
interface FastEthernet0/0
ip address 209.165.200.232 255.255.255.224
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
speed auto
half-duplex
pppoe enable
!
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
Access Control Policies Example
The following output example shows that access control policies have been configured.
Single DHCP pool
ip dhcp pool private
network 209.165.200.236 255.255.255.224
default-router 20.0.0.1
exit
crypto isakmp policy 1
authentication pre-share
!
crypto isakmp key test address address
crypto ipsec transform-set t1 esp-3des esp-sha-hmac
mode tunnel
crypto map test 1 ipsec-isakmp
set peer address
set transform-set t1
match address 101
access-list 101 permit ip 10.0.0.0 0.0.0.255 50.0.0.0 0.0.0.255
access-list 102 deny ip 10.0.0.0 0.0.0.255 50.0.0.0 0.0.0.255
access-list 102 permit ip any any
!
interface Ethernet0
! inside interface
! dot1x configs
!
interface Virtual-Template1
! Deny traffic from going to VPN
ip access-group 102 in
!
Interface Ethernet1
! outside interface
crypto map test
Two DHCP Pools
ip dhcp pool private
network 209.165.200.237 255.255.255.224
default-router 192.0.2.1
exit
!
ip dhcp pool public
network 209.165.200.238 255.255.255.224
default-router 192.0.2.0
exit
!
crypto isakmp policy 1
authentication pre-share
!
crypto isakmp key test address address
crypto ipsec transform-set t1 esp-3des esp-sha-hmac
mode tunnel
crypto map test 1 ipsec-isakmp
set peer address
set transform-set t1
match address 101
access-list 101 permit ip 10.0.0.0 0.0.0.255 10.10.0.0 0.0.0.255
access-list 102 permit ip 10.0.0.1 0.0.0.255 any
!
interface Ethernet0
!inside interface
! dot1x configs
!
interface Loopback0
ip address 209.165.200.239 255.255.255.224
!
interface Virtual-Template1
ip unnumbered Loopback0
ip nat inside
!
Interface Ethernet1
! outside interface
crypto map test
ip nat outside
!
ip nat inside source list 102 interface Ethernet1 overload
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 provides online resources to download 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.
Feature Information for VPN Access Control Using 802.1X Authentication
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1
Feature Information for VPN Access Control Using 802.1X Authentication
Feature Name
Releases
Feature Information
VPN Access Control Using 802.1X Authentication
12.3(2)XA
The VPN Access Control Using 802.1X Authentication feature was introduced. This feature allows enterprise employees to access their enterprise networks from home while allowing other household members to access only the Internet.
VPN Access Control Using 802.1X Authentication
12.3(4)T
This feature was integrated into 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.
802.1X Supplicant Support
12.3(11)T
802.1X supplicant support was added.
Converged 802.1X Authenticator and Converged 802.1X Supplicant Support
12.4(6)T
Converged 802.1X authenticator and converged 802.1X supplicant support was added. (This update is a standardization of Cisco IOS 802.1X commands for various Cisco IOS platforms. This is no change in 802.1X features.)
Affected commands include the following:
cleareap,debugdot1x,debugeap,description(dot1xcredentials),dot1xcontrol-direction,dot1xcredentials,dot1xdefault,dot1xhost-mode,dot1xmax-reauth-req,dot1xmax-start,dot1xmultiple-hosts,dot1xtimeout,eap,identityprofile,password(dot1xcredentials),showeapregistrations,showeapsessions, and
username
VPN Access Control Using 802.1X Authentication
12.4(4)XC
Various 802.1X commands were integrated into Cisco IOS Release 12.4(4)XC for Cisco 870 Integrated Services Routers (ISRs) only.
Affected commands include the following:
dot1xcontrol-direction,dot1xdefault,dot1xguest-vlan,dot1xhost-mode,dot1xmax-reauth-req,dot1xmax-req,dot1xmax-start,dot1xpae,dot1xport-control,dot1xre-authenticate(privilegedEXEC),dot1xreauthentication,dot1xsystem-auth-control,dot1xtimeout,macroglobal,macroname, and
showipigmpsnooping
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.