Introduction
This document how to allow remote access VPN connections to the ASA from the Cisco AnyConnect 2.0 client.
Prerequisites
Requirements
Ensure that you meet these requirements before you attempt this configuration:
*
Basic ASA configuration that runs software version 8.0
*
ASDM 6.0(2)
Components Used
The information in this document is based on these software and hardware versions:
* Cisco ASA 8.0(2), ASDM 6.0 (2)
* Cisco AnyConnect 2.0
Background Information
The Cisco AnyConnect 2.0 client is an SSL-based VPN client. The AnyConnect client can be utilized and installed on a variety of operating systems, such as Windows 2000, XP, Vista, Linux (Multiple Distros) and MAC OS X. The AnyConnect client can be installed manually on the remote PC by the system administrator. It can also be loaded onto the security appliance and made ready for download to remote users. After the application is downloaded, it can automatically uninstall itself after the connection terminates, or it can remain on the remote PC for future SSL VPN connections. This example makes the AnyConnect client ready to download upon successful browser-based SSL authentication.
For more information on the AnyConnect 2.0 client, refer to AnyConnect 2.0 Release Notes.
Note: MS Terminal Services is not supported in conjunction with the AnyConnect client. You cannot RDP to a computer and then initiate an AnyConnect session. You cannot RDP to a client that is connected via AnyConnect.
Note: The first installation of AnyConnect requires the user to have admin rights (whether you use the standalone AnyConnect msi package or push the pkg file from the ASA). If the user does not have admin rights, a dialog box appears that states this requirement. Subsequent upgrades will not require the user that installed AnyConnect previously to have admin rights.
Configure
Step 1. Configure a Self-Issued Certificate
By default, the security appliance has a self-signed certificate that is regenerated every time the device is rebooted. You can purchase your own certificate from vendors, such as Verisign or EnTrust, or you can configure the ASA to issue an identity certificate to itself. This certificate remains the same even when the device is rebooted. Complete this step in order to generate a self-issued certificate that persists when the device is rebooted.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Certificate Management, and then choose Identity Certificates.
3.
Click Add, and then click the Add a new identity certificate radio button.
4.
Click New.
5.
In the Add Key Pair dialog box, click the Enter new key pair name radio button.
6.
Enter a name to identify the keypair.
This example uses sslvpnkeypair.
7.
Click Generate Now.
8.
In the Add Identity Certificate dialog box, ensure the newly created key pair is selected.
9.
For Certificate Subject DN, enter the fully qualified domain name (FQDN) that will be used to connect to the VPN terminating interface.
CN=sslvpn.cisco.com
10.
Click Advanced, and enter the FQDN used for the Certificate Subject DN field.
For example, FQDN: sslvpn.cisco.com
11.
Click OK.
12.
Check the Generate Self Signed Certificate check box, and click Add Certificate.
13.
Click OK.
14.
Click Configuration, and then click Remote Access VPN.
15.
Expand Advanced, and choose SSL Settings.
16.
In the Certificates area, choose the interface that will be used to terminate the SSL VPN (outside), and click Edit.
17.
In the Certificate drop-down list, choose the self-signed certificate that you generated earlier.
18.
Click OK, and then click Apply.
Step 2. Upload and Identify the SSL VPN Client Image
This document uses the AnyConnect SSL 2.0 client. You can obtain this client at the Cisco Software Download Website. A separate Anyconnect image is required for each operating system that remote users plan to use. For more information, refer to Cisco AnyConnect 2.0 Release Notes.
Once you obtain the AnyConnect client, complete these steps:
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Network (Client) Access, and then expand Advanced.
3.
Expand SSL VPN, and choose Client Settings.
4.
In the SSL VPN Client Images area, click Add, and then click Upload.
5.
Browse to the location where you downloaded the AnyConnect client.
6.
Select the file, and click Upload File.
Once the client uploads, you receive a message that states the file was uploaded to flash successully.
7.
Click OK.
A dialog box appears to confirm that you want to use the newly uploaded image as the current SSL VPN client image.
8.
Click OK.
9.
Click OK, and then click Apply.
10.
Repeat the steps in this section for each operating system-specific Anyconnect package that you want to use.
Step 3. Enable Anyconnect Access
In order to allow the AnyConnect client to connect to the ASA, you must enable access on the interface that terminates SSL VPN connections. This example uses the outside interface in order to terminate Anyconnect connections.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Network (Client) Access, and then choose SSL VPN Connection Profiles.
3.
Check the Enable Cisco AnyConnect VPN Client check box.
4.
Check the Allow Access check box for the outside interface, and click Apply.
Step 4. Create a new Group Policy
A group policy specifies the configuration parameters that should be applied to clients when they connect. This example creates a group policy named SSLClientPolicy.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Network (Client) Access, and choose Group Policies.
3.
Click Add.
4.
Choose General, and enter SSLClientPolicy in the Name field.
5.
Uncheck the Address Pools Inherit check box.
6.
Click Select, and then click Add.
The Add IP Pool dialog box appears.
7.
Configure the address pool from an IP range that is not currently in use on your network.
This example uses these values:
*
Name: SSLClientPool
*
Starting IP Address: 192.168.25.1
*
Ending IP Address: 192.168.25.50
*
Subnet Mask: 255.255.255.0
8.
Click OK.
9.
Choose the newly created pool, and click Assign.
10.
Click OK, and then click More Options.
11.
Uncheck the Tunneling Protocols Inherit check box.
12.
Check SSL VPN Client.
13.
In the left pane, choose Servers.
14.
Uncheck the DNS Servers Inherit check box, and enter the IP address of the internal DNS server that the AnyConnect clients will use.
This example uses 192.168.50.5.
15.
Click More Options.
16.
Uncheck the Default Domain Inherit check box.
17.
Enter the domain used by your internal network. For example, tsweb.local .
18.
Click OK, and then click Apply.
Configure Access List Bypass for VPN Connections
When you enable this option, you allow the SSL/IPsec clients to bypass the interface access list.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Network (Client) Access, and then expand Advanced.
3.
Expand SSL VPN, and choose Bypass Interface Access List.
4.
Ensure the Enable inbound SSL VPN and IPSEC Sessions to bypass interface access lists check box is checked, and click Apply.
Step 6. Create a Connection Profile and Tunnel Group for the AnyConnect Client Connections
When VPN clients connect to the ASA, they connect to a connection profile or tunnel group. The tunnel group is used to define connection parameters for specific types of VPN connections, such as IPsec L2L, IPsec remote access, clientless SSL, and client SSL.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand Network (Client) Access, and then expand SSL VPN.
3.
Choose Connection Profiles, and click Add.
4.
Choose Basic, and enter these values:
*
Name: SSLClientProfile
*
Authentication: LOCAL
*
Default Group Policy: SSLClientPolicy
5.
Ensure the SSL VPN Client Protocol check box is checked.
6.
In the left pane, expand Advanced, and choose SSL VPN.
7.
Under Connection Aliases, click Add, and enter a name to which users can associate their VPN connections. For example, SSLVPNClient.
8.
Click OK, and then click OK again.
9.
At the bottom of the ASDM window, check the Allow user to select connection, identified by alias in the table above at login page check box, and click Apply.
Step 7. Configure NAT Exemption for AnyConnect Clients
NAT exemption should be configured for any IP addresses or ranges you want to allow the SSL VPN clients to access. In this example, the SSL VPN clients need access to the internal IP 192.168.50.5 only.
Note: If NAT-control is not enabled, this step is not required. Use the show run nat-control command to verify. In order to verify through ASDM, click Configuration, click Firewall, and choose Nat Rules. If the Enable traffic through the firewall without address translation check box is checked, you can skip this step.
ASDM Procedure
1.
Click Configuration, and then click Firewall.
2.
Choose Nat Rules, and click Add.
3.
Choose Add NAT Exempt Rule, and enter these values:
*
Action: Exempt
*
Interface: inside
*
Source: 192.168.50.5
*
Destination: 192.168.25.0/24
*
NAT Exempt Direction: NAT Exempt outbound traffic from interface ‘inside’ to lower security interfaces (Default)
4.
Click OK, and then click Apply.
Step 8. Add Users to the Local Database
If you use local authentication (the default), you must define user names and passwords in the local database for user authentication.
ASDM Procedure
1.
Click Configuration, and then click Remote Access VPN.
2.
Expand AAA Setup, and choose Local Users.
3.
Click Add, and enter these values:
*
Username: matthewp
*
Password: p@ssw0rd
*
Confirm Password: p@ssw0rd
4.
Select the No ASDM, SSH, Telnet or Console Access radio button.
5.
Click OK, and then click Apply.
6.
Repeat this step for additional users, and then click Save.
Verify SSL VPN Client Connections
Use the show vpn-sessiondb svc command in order to verify connected SSL VPN clients.
ciscoasa(config-group-policy)#show vpn-sessiondb svc
Session Type: SVC
Username : matthewp Index : 6
Assigned IP : 192.168.25.1 Public IP : 172.18.12.111
Protocol : Clientless SSL-Tunnel DTLS-Tunnel
Encryption : RC4 AES128 Hashing : SHA1
Bytes Tx : 35466 Bytes Rx : 27543
Group Policy : SSLClientPolicy Tunnel Group : SSLClientProfile
Login Time : 20:06:59 UTC Tue Oct 16 2007
Duration : 0h:00m:12s
NAC Result : Unknown
VLAN Mapping : N/A VLAN : none
ciscoasa(config-group-policy)#
The vpn-sessiondb logoff name username command logs off users by user name. An Administrator Reset message is sent to the user when disconnected.
ciscoasa(config)#vpn-sessiondb logoff name matthewp
Do you want to logoff the VPN session(s)? [confirm]
INFO: Number of sessions with name “matthewp” logged off : 1
ciscoasa(config)#
