 Feedback
|
Table Of Contents
Release Notes for Cisco AnyConnect Secure Mobility Client, Release 2.5
Downloading the Latest Version
Important AnyConnect, CSD, and Host Scan Interoperability Information
Changes in AnyConnect 2.5.6005
Changes in AnyConnect 2.5.3055
Changes in AnyConnect 2.5.3054
Changes in AnyConnect 2.5.3051
Compatibility with Global Site Selector Devices
Changes in AnyConnect 2.5.3046
Changes in AnyConnect 2.5.3041
Changes in AnyConnect 2.5.2019
Changes in AnyConnect 2.5.2018
Changes in AnyConnect 2.5.2017
Changes in AnyConnect 2.5.2014
Changes in AnyConnect 2.5.2011
Changes in AnyConnect 2.5.2010
Changes in AnyConnect 2.5.2006
Changes in AnyConnect 2.5.2001
Changes Introduced in AnyConnect 2.5.1025
Local Proxy Connection Support
Pause and Resume Support for the Trusted Network Policy
Authentication Timeout Control
Microsoft Internet Explorer Proxy Lockdown Control
Changes Introduced in AnyConnect 2.5.0217
Captive Portal Hotspot Detection
Client Firewall with Local Printer and Tethered Device Support
Preventing Other Devices in a LAN from Displaying Hostnames
Messages in the Localization File Can Span More than One Line
Change to AnyConnect Pop-Up Messages
MTU Adjustment on Group Policy May Be Required
AnyConnect for Mac OS Performance when Behind Certain Routers
Preventing Windows Users from Circumventing Always-on
Guidelines from Previous Releases Still in Effect
Responding to a TUN/TAP Error Message with Mac OS X 10.5
64-bit Internet Explorer Not Supported
AnyConnect Requires That the ASA Be Configured to Accept TLSv1 Traffic
Flexibility in the Sequence and Method Used to Install Start Before Logon and DART Components
Security Appliance Software Requirements
Caveats Resolved by AnyConnect 2.5.6005
Caveats Resolved by AnyConnect 2.5.3055
Open Caveats in Release 2.5.3055
Caveats Resolved by AnyConnect 2.5.3054
Open Caveats in Release 2.5.3054
Caveats Resolved by AnyConnect 2.5.3051
Open Caveats in Release 2.5.3051
Caveats Resolved by AnyConnect 2.5.3046
Open Caveats in AnyConnect 2.5.3041 and 2.5.3046
Caveats Resolved by AnyConnect 2.5.3041
Caveat Resolved by AnyConnect 2.5.2019
Open Caveats in AnyConnect 2.5.2014-2.5.2019
Caveat Resolved by AnyConnect 2.5.2017
Caveat Resolved by AnyConnect 2.5.2014
Caveat Resolved by AnyConnect 2.5.2011
Open Caveats in AnyConnect 2.5.2001-2.5.2011
Caveats Resolved by AnyConnect 2.5.2010
Caveats Resolved by AnyConnect 2.5.2006
Caveats Resolved by AnyConnect 2.5.2001
Caveats Resolved by AnyConnect 2.5.1025
Open Caveats in AnyConnect 2.5.1025
Caveats Resolved by AnyConnect 2.5.0217
Open Caveats in AnyConnect 2.5.0217
Release Notes for Cisco AnyConnect Secure Mobility Client, Release 2.5
Updated: August 10, 2012This document includes the following sections:
•
Downloading the Latest Version
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Introduction
These release notes are for all Cisco AnyConnect Secure Mobility Client, Release 2.5 versions.
Note
We changed the name of the Cisco AnyConnect VPN Client to the Cisco AnyConnect Secure Mobility Client; the product name change is in transition, and may not be complete in all places.
The Cisco AnyConnect Secure Mobility client provides remote users with secure VPN connections to the Cisco ASA 5500 Series Adaptive Security Appliance using the Secure Socket Layer (SSL) protocol and the Datagram TLS (DTLS) protocol.
AnyConnect provides remote end users with the benefits of a Cisco SSL VPN client, and supports applications and functions unavailable to a clientless, browser-based SSL VPN connection. It runs on Microsoft Windows, Windows Mobile, Linux, and Mac OS X, and supports connections to IPv6 resources over an IPv4 network tunnel. You can upload the client to the ASA to automatically download to remote users when they log in, or you can download and install it on the endpoint. You can configure the ASA to uninstall AnyConnect from the endpoint after the connection terminates, or it can remain on the remote PC for future SSL VPN connections.
In addition to the Cisco Adaptive Security Appliance 5500 Series, Cisco IOS Release 15.1(2)T supports the AnyConnect Secure Mobility client. For more information, see the Cisco IOS SSL VPN Data Sheet.
Downloading the Latest Version
To download the latest version of AnyConnect, you must be a registered user of Cisco.com.
Step 1
http://www.cisco.com/en/US/products/ps10884/tsd_products_support_series_home.html
Step 2
Step 3
Step 4
Step 5
•
•
Step 6
Step 7
What to do Next
See, Chapter 2, Configuring the Security Appliance to Deploy AnyConnect in Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5 to install the packages onto an ASA or to deploy AnyConnect using your enterprise software management system.
Important AnyConnect, CSD, and Host Scan Interoperability Information
AnyConnect 2.5.6005 is compatible with Host Scan 3.0.08057 or later versions and CSD 3.6.6020 or later versions. AnyConnect 2.5.6005 is not compatible with earlier versions of Host Scan or CSD.
Caution
Caution
Changes in AnyConnect 2.5.6005
AnyConnect 2.5.6005 specifies new compatibility requirements between AnyConnect, Host Scan, and CSD as described in Important AnyConnect, CSD, and Host Scan Interoperability Information on page page 3 and resolves the caveats in Table 1.
Changes in AnyConnect 2.5.3055
AnyConnect Release 2.5.3055 is a maintenance release that resolves the caveats in Table 2.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.3054
AnyConnect Release 2.5.3054 is a maintenance release that resolves the caveat in Table 4.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.3051
Compatibility with Global Site Selector Devices
The AnyConnect VPN client is now compatible with Global Site Selector (GSS) devices. No client-side configuration is required to take advantage of this capability. When you point the client at the fully qualified domain name (FQDN) answered to the GSS, the devices provide DNS performance improvements through load balancing mechanisms. For GSS support, server certificate verifications must occur at the outset of authentication, including SSL handshakes performed in API, downloader, and agent.
LZS Compression
Cisco now supports compression for DTLS and TLS on AnyConnect 3.0.3047 or later. Each tunneling method configures compression separately, and the preferred configuration is to have both SSL and DTLS compression as LZS. You enable compression in the webvpn submode of the group policy and username configuration modes. This feature enhances migration from the legacy VPN clients.
You must have ASA release 8.4.2.x or later for support of the LZS compression feature.
Using data compression on high speed remote access connections passing highly compressible data requires significant processing power on the ASA. With other activity and traffic on the ASA, the number of sessions that can be supported on the platform is reduced.
Lion Support
AnyConnect 2.5.3051 provides support for Lion OS X 10.7.Without the appropriate JAVA and Web applet, OS X users may experience CSCtq62860 or CSCto09628. You must install JAVA and enable the appropriate Applet plug-in and web start applications using these steps:
Step 1
Step 2
Step 3
Changes in AnyConnect 2.5.3046
AnyConnect Release 2.5.3046 is a maintenance release that resolves the caveat in Table 8. The fix resolves a certificate-based installation issue on Mac OS X and Linux only.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.3041
Network Location Awareness for Windows
With Network Location Awareness enabled on the AnyConnect virtual adapter (VA), Windows 7 now applies the proper firewall profile containing a collection of network and security settings to the network connection associated with the VA. The Cisco AnyConnect Secure Mobility Client connection now appears in the Windows Control Panel, Network and Sharing Center.
Changes in AnyConnect 2.5.2019
AnyConnect Release 2.5.2019 is a maintenance release that resolves the caveat in Table 11.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2018
AnyConnect Release 2.5.2018 is a maintenance release for Cisco I.T. use only.
Changes in AnyConnect 2.5.2017
AnyConnect Release 2.5.2017 is a maintenance release that resolves the caveat in Table 13.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2014
AnyConnect Release 2.5.2014 is a maintenance release that resolves the caveat in Table 14.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2011
AnyConnect Release 2.5.2010 is a maintenance release that resolves the caveat in Table 15.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2010
AnyConnect Release 2.5.2010 is a maintenance release that resolves the caveats in Table 17.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2006
AnyConnect Release 2.5.2006 is a maintenance release that resolves the caveats in Table 18.
No new features have been introduced with this release.
Changes in AnyConnect 2.5.2001
AnyConnect Release 2.5.2001 is a maintenance release that resolves the caveats in Table 19.
No new features have been introduced with this release.
Changes Introduced in AnyConnect 2.5.1025
AnyConnect Release 2.5.1025 supports the following new features.
Local Proxy Connection Support
By default, AnyConnect now lets users establish a VPN session through a transparent or non-transparent proxy on the local PC.
Some examples of elements that provide a transparent proxy service include:
•
•
AnyConnect supports this feature on the following Microsoft OSs:
•
•
•
Support for this feature requires either an AnyConnect Essentials or an AnyConnect Premium SSL VPN Edition license.
To use the ASDM AnyConnect Profile Editor to disable this feature, open the Preferences (cont) window and uncheck Allow Local Proxy Connections near the top of the panel.
Alternatively, you can use a text editor to insert the XML tag
<AllowLocalProxyConnections>into the AnyConnect profile. The options are true and false. For example:<ClientInitialization><AllowLocalProxyConnections>false</AllowLocalProxyConnections></ClientInitialization>Pause and Resume Support for the Trusted Network Policy
If you set the trusted network policy to pause, and a user then establishes a VPN session outside the network, then enters a network configured as trusted, AnyConnect suspends the VPN session instead of disconnecting it. When the user goes outside the trusted network again, AnyConnect resumes the session. This feature is for the user's convenience because it eliminates the need to establish a new VPN session after leaving a trusted network.
The ASA idle timer starts when the user's session becomes inactive as a result of leaving the untrusted network and stops when the session resumes in the untrusted network. Before configuring this feature, adjust both the Maximum Connect Time and Idle Timeout values on the ASDM Group Policy General panel.
AnyConnect supports this feature on the following OSs:
•
•
•
•
Support for this feature requires either an AnyConnect Essentials or an AnyConnect Premium SSL VPN Edition license.
To use the Profile Editor to set the trusted network policy to pause, open the Preferences (cont) window and choose Pause next to the Trusted Network Policy parameter.
Alternatively, you can use a text editor to change value of the XML tag
<TrustedNetworkPolicy>in the AnyConnect profile. The following example shows a complete trusted network policy configuration:<ClientInitialization><AutomaticVPNPolicy>true<TrustedDNSDomains>*.cisco.com</TrustedDNSDomains><TrustedDNSServers>161.44.124.*,64.102.6.247</TrustedDNSServers><TrustedNetworkPolicy>Pause</TrustedNetworkPolicy><UntrustedNetworkPolicy>Connect</UntrustedNetworkPolicy></AutomaticVPNPolicy></ClientInitialization>Authentication Timeout Control
By default, AnyConnect waits up to 12 seconds for an authentication from the secure gateway before terminating the connection attempt. AnyConnect then displays a message indicating the authentication timed out.
The AnyConnect profile now lets you specify the authentication timeout value. Specify the number of seconds in the range 10-120.
AnyConnect supports this feature on all OSs supported by AnyConnect.
Support for this feature requires either an AnyConnect Essentials or an AnyConnect Premium SSL VPN Edition license.
To use the Profile Editor to change the authentication timer, open the Preferences (cont) window and enter the number of seconds into the Authentication Timeout Values field.
Alternatively, you can use a text editor to add the XML tag
<AuthenticationTimeout>to the AnyConnect profile. The following example sets the authentication timeout to 20 seconds:<ClientInitialization><AuthenticationTimeout>20</AuthenticationTimeout></ClientInitialization>Microsoft Internet Explorer Proxy Lockdown Control
By default, AnyConnect hides the Connections tab in Microsoft Internet Explorer for the duration of the AnyConnect VPN session. AnyConnect 2.5.1 supports the ASA group policy configuration of the Microsoft Internet Explorer Proxy Lockdown Control feature introduced in ASA Releases 8.2.3, 8.3.2, and later. This feature lets you disable the default behavior.
Using the default behavior prevents users from specifying a proxy service and changing LAN settings. Preventing user access to these settings enhances endpoint security during the AnyConnect session.
Disabling the default behavior lets users specify the proxy service to use and change LAN settings during the AnyConnect session.
AnyConnect supports this feature on the following Microsoft OSs:
•
•
•
Support for this feature requires either an AnyConnect Essentials or an AnyConnect Premium SSL VPN Edition license.
To prevent AnyConnect from hiding the Connections tab, use the ASA msie-proxy lockdown disable command in group-policy configuration mode. The following example does not hide the Connections tab:
hostname(config)# group-policy FirstGroup attributeshostname(config-group-policy)# msie-proxy lockdown disableThe following example hides the Connections tab for the duration of the AnyConnect session:
hostname(config-group-policy)# msie-proxy lockdown enableChanges Introduced in AnyConnect 2.5.0217
AnyConnect Release 2.5.0217 supports the following new features on Windows 7, Vista, and XP; and Mac OS X 10.5 and 10.6.x:
•
•
Post Log-in Always-on VPN
As an administrator, you can configure AnyConnect to establish a VPN session automatically after the user logs in to a computer. The VPN session remains open until the user logs out of the computer. If the physical connection is lost, the session remains open, and AnyConnect continually attempts to reestablish the physical connection with the ASA to resume the VPN session.
(Post log-in) always-on VPN enforces corporate policies to protect the computer from security threats by preventing access to Internet resources when it is not in a trusted network.
Always-on VPN requires a valid server certificate configured on the ASA; otherwise, it fails and logs an event indicating the certificate is invalid.
Caution
With always-on enabled, the client does not support connecting through a proxy.
The ASA lets you configure dynamic access policies, group policies, or both to exempt certain individuals from an always-on VPN setting.
If an AnyConnect policy enables always-on VPN and a dynamic access policy or group policy disables it, the client retains the disable setting for the current and future VPN sessions as long as its criteria match the dynamic access policy or group policy on the establishment of each new session.
AnyConnect supports a Disconnect button for always-on VPN sessions. If you enable it, AnyConnect displays a Disconnect button upon the establishment of a VPN session. Users of always-on VPN sessions may want to click Disconnect so they can choose an alternative secure gateway for reasons such as the following:
•
•
Caution
Do not attempt to configure always-on VPN until you have read all of the instructions and understand its requirements and implications, as detailed in the following sections in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5. When using always on, the integrity of your network must be well defined. As such, CRL Distribution Points for the secure gateway's server certificate must be available for verification by a client on a public network.
•
Connect Failure Policy
The connect failure policy determines whether the computer can access the Internet if always-on VPN is enabled and AnyConnect cannot establish a VPN session (for example, when a secure gateway is unreachable). The fail-close policy disables network connectivity-except for VPN access. The fail-open policy permits network connectivity. Regardless of the connect failure policy, AnyConnect continues to try to establish the VPN connection. The following table explains the fail open and fail close policies:
Caution
If you deploy a closed connection policy, we highly recommend that you follow a phased approach. For example, first deploy always-on VPN with a connect failure open policy and survey users for the frequency with which AnyConnect does not connect seamlessly. Then deploy a small pilot deployment of a connect failure closed policy among early-adopter users and solicit their feedback. Expand the pilot program gradually while continuing to solicit feedback before considering a full deployment. As you deploy a connect failure closed policy, be sure to educate the VPN users about the network access limitation as well as the advantages of a connect failure closed policy.
Do not attempt to configure a connect failure policy until you have read all of the instructions and understand the requirements and implications, as detailed in Connect Failure Policy for Always-on VPN in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5.
Captive Portal Hotspot Detection
Many facilities that offer Wi-Fi and wired access, such as airports, coffee shops, and hotels, require the user to pay before obtaining access, agree to abide by an acceptable use policy, or both. These facilities use a technique called captive portal to prevent applications from connecting until the user opens a browser and accepts the conditions for access.
AnyConnect displays the
Unable to contact VPN servermessage on the GUI if it cannot connect, regardless of the cause. If a captive portal is not present, AnyConnect continues to attempt to connect to the VPN and updates the status message accordingly.If always-on VPN is enabled, the connect failure policy is closed, captive portal remediation is disabled, and AnyConnect detects the presence of a captive portal, the AnyConnect GUI displays the following message once per connection and once per reconnect:
The service provider in your current location is restricting access to the Internet. The AnyConnect protection settings must be lowered for you to log on with the service provider. Your current enterprise security policy does not allow this.If AnyConnect detects the presence of a captive portal and the AnyConnect configuration differs from that described above, the AnyConnect GUI displays the following message once per connection and once per reconnect:
The service provider in your current location is restricting access to the Internet. You need to log on with the service provider before you can establish a VPN session. You can try this by visiting any website with your browser.Captive Portal Remediation
Captive portal remediation is the process of satisfying the requirements of a captive portal hotspot to obtain network access. By default, the connect failure policy prevents captive portal remediation because it restricts network access. You can configure AnyConnect to lift restricted access to let the user satisfy the captive portal requirements. You can also specify the duration for which AnyConnect lifts restricted access. For instructions, see Captive Portal Remediation in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5.
Client Firewall with Local Printer and Tethered Device Support
When users connect to the ASA, all traffic is tunneled through the connection and users cannot access resources on their local network. This includes printers, cameras, and Windows Mobile devices (tethered devices) that sync with the local computer. Enabling Local LAN Access in the client profile resolves this problem, however it can introduce a security or policy concern for some enterprises as a result of unrestricted access to the local network. You can use the ASA to deploy endpoint OS firewall capabilities to restrict access to particular types of local resources, such as printers and tethered devices.
To do so, enable client firewall rules for specific ports for printing. The client distinguishes between inbound and outbound rules. For printing capabilities, the client opens ports required for outbound connections, but blocks all incoming traffic. The client firewall is independent of the always-on feature.
Note
If you configure the client firewall, and the user authenticates to an Active Directory (AD) server, the client still applies the firewall policies from the ASA. However, the rules defined in the AD group policy take precedence over the rules of the client firewall.
Note
Differences in Firewall Behavior between Mac and Windows
For Windows computers, deny rules take precedence over allow rules in Windows Firewall. If the ASA pushes down an allow rule to the AnyConnect client, but the user has created a custom deny rule, the AnyConnect rule is not enforced.
On Mac computers, the AnyConnect client applies rules sequentially in the same order the ASA applies them. Global rules should always be last.
Windows users whose firewall service must be started by the AnyConnect client (not started automatically by the system) may experience a noticeable increase in the time it takes to establish a VPN connection.
Due to limitations of the OS, the client firewall policy on computers running Windows XP is enforced for inbound traffic only. Outbound rules and bidirectional rules are ignored. This would include firewall rules such as permit ip any any.
For instructions on how to use the firewall to support local printers and tethered devices, see Client Firewall with Local Printer and Tethered Device Support in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5
Optimal Gateway Selection
Using the Optimal Gateway Selection (OGS) feature, you can minimize latency for Internet traffic without user intervention. With OGS, the AnyConnect client identifies and selects which secure gateway is best for connection or reconnection.
OGS begins upon first connection or upon a reconnection at least four hours after the previous disconnection. Users who travel to distant locations connect to a secure gateway nearer to the new location for better performance. Your home and office will get similar results from the same gateway, so no switch of secure gateways will typically occur in this instance. Connection to another secure gateway occurs rarely and only occurs if the performance improvement is at least 20%.
Note
OGS is not a security feature, and it performs no load balancing between secure gateway clusters or within clusters. You can optionally give the end user the ability to enable or disable the feature.
The minimum round trip time (RTT) solution selects the secure gateway with the fastest RTT between the client and all other gateways. The client always reconnects to the last secure gateway if the time elapsed has been less than four hours. Factors such as load and temporary fluctuations of the network connection may affect the selection process, as well as the latency for Internet traffic.
OGS supports computers running:
•
•
You use the second Preferences menu option of the Profile Editor to control the activation and deactivation of the OGS and to specify whether end users may control the feature themselves.
If OGS is enabled when the AnyConnect client GUI is started, Automatic Selection displays in the Connect To drop-down menu on the Cisco AnyConnect Connection tab. You cannot change this selection. OGS automatically chooses the optimal secure gateway and displays the selected gateway on the status bar. You may need to click Select to start the connection process.
It contacts only the primary servers to determine the optimal one. Once determined, the connection algorithm is as follows:
1.
2.
3.
If you made the feature user controllable, the user can manually override the selected secure gateway with the following steps:
Step 1
Step 2
Step 3
Note
For more information about OGS, see Optimal Gateway Selection in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5.
Quarantine
Through the use of quarantine, you can restrict a particular client who already has an established tunnel through a VPN. The ASA applies restricted ACLs to a session to form a restricted group, based on the selected dynamic access policy. When an endpoint is not compliant with an administratively defined policy, the user can still access services for remediation (such as updating the antivirus and so on), but restrictions are placed upon the session. After the remediation occurs, the user can reconnect, which invokes a new posture assessment. If this assessment passes, the user connects.
Note
Quarantine requires an Advanced Endpoint Assessment license specified in the adaptive security license configuration. The advanced endpoint assessment remediates endpoints that do not comply with dynamic policy requirements for antivirus, antispyware, and firewall applications; and any associated application definition file requirements. Advanced endpoint assessment is a Cisco Secure Desktop Host Scan feature, so AnyConnect supports quarantine on the OSs that the version of Cisco Secure Desktop supports. Go to Supported VPN Platforms and refer to the "Cisco Secure Desktop" section that identifies the release you are using. The table identifies the OSs that Host Scan supports.
ASA Release 8.3(1) or later features dynamic access policies and group policies that support a user message to display on the AnyConnect UI for the duration of the quarantine state. Quarantine does not require the ASA upgrade; only the user message requires it. If you upgrade the ASA to 8.3(1), we recommend that you also upgrade ASDM to Release 6.3(1) or later so that you can use it to configure the new features.
For instructions, see Using Quarantine to Restrict Non-Compliant Clients in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5.
AnyConnect Profile Editor
The AnyConnect profile editor is a convenient GUI-based configuration tool you can use to configure the AnyConnect client profile—an XML file containing settings that control client features. Previously, you could only change profile settings manually by editing the XML tags in the profile.
The AnyConnect client software package for each operating system, version 2.5 and later, contains the profile editor. You can launch the profile editor from ASDM (version 6.3(1) or later) if the client software package is loaded on the ASA as an SSL VPN client image.
Note
If you load multiple client packages, ASDM loads the profile editor from the newest client package. This approach ensures the editor displays the features for the newest client loaded, as well as the older clients.
The Profile Editor supports only Java SE 1.6 on the client computer.
To activate the profile editor in ASDM, load the AnyConnect client software package as an SSL VPN image and go to Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Client Profile.
For more information about using the profile editor, see the sections beginning with Introduction to the AnyConnect Profile Configuration in the Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5.
AnyConnect 2.5 Guidelines
The following sections provide guidelines that are new in AnyConnect 2.5 and guidelines noted in earlier releases that are still in effect.
New Guidelines
The following guidelines are new in AnyConnect 2.5:
•
•
•
•
•
•
Preventing Other Devices in a LAN from Displaying Hostnames
After one uses AnyConnect to establish a VPN session with Windows 7 on a remote LAN, the network browsers on the other devices in the user's LAN can display the names of hosts on the protected remote network. However, the other devices cannot access these hosts.
To ensure the AnyConnect host prevents the hostname leak between subnets, including the name of the AnyConnect endpoint host, configure that endpoint to never become the master or backup browser. To do so,
Step 1
Step 2
Step 3
The Edit String window opens.
Step 4
Step 5
Step 6
Messages in the Localization File Can Span More than One Line
If you try to search for messages in the localization file, please note that they can span more than one line, as shown in the example below:
msgid """The service provider in your current location is restricting access to the ""Secure Gateway. "IOS Support
Cisco supports Anyconnect 2.5 VPN access to IOS Release 15.1(2)T functioning as the secure gateway; however, you cannot use the features introduced in AnyConnect 2.5 with IOS.
The new AnyConnect 2.5 features that do not support are IOS are:
•
•
•
•
•
•
•
Refer to http://www.cisco.com/go/fn for additional IOS feature support information.
Change to AnyConnect Pop-Up Messages
For release 2.5, we created this new message displayed to AnyConnect users:
AnyConnect cannot confirm it is connected to your secure gateway. The local network may not be trustworthy. Please try another network.Users receive the new message when the client cannot validate the certificate from the ASA for either of these reasons:
•
•
The new message replaces and consolidates the following messages displayed by releases 2.4 and earlier:
•
The service provider in your current location is restricting access to the Internet. The AnyConnect protection settings must be lowered for you to log on with the service provider. Your current enterprise security policy does not allow this.•
The service provider in your current location is restricting access to the Internet. You need to log on with the service provider before you can establish a VPN session. You can try this by visiting any website with your browser.Revocation Message
An AnyConnect GUI revocation warning popup window opens after authentication if AnyConnect attempts to verify a server certificate that specifies the distribution point of an LDAP certificate revocation list (CRL) and the distribution point is only internally accessible.
If you want to avoid the display of this popup window, do one of the following:
•
•
Caution
MTU Adjustment on Group Policy May Be Required
AnyConnect sometimes receives and drops packet fragments with some routers. This can result in a failure of some web traffic to pass.
To avoid this, lower the value of the MTU. To access the MTU with ASDM, choose Configuration > Network (Client) Access > Group Policies > Add or Edit > Advanced > SSL VPN Client.
AnyConnect for Mac OS Performance when Behind Certain Routers
When the AnyConnect client for Mac OS connects to the ASA from behind certain types of routers, such as the Cisco Virtual Office (CVO) router, some web traffic may pass through the connection while other traffic drops. This could happen because AnyConnect may calculate the MTU incorrectly. To work around this problem, set the MTU for the AnyConnect adaptor to a lower value using the following command from the OS X command line:
sudo ipconfig cscotun0 mtu 1200 (For Mac OS10.5 or earlier)
sudo ipconfig utun0 mtu 1200 (For Mac OS10.6 and later)
Preventing Windows Users from Circumventing Always-on
On Windows computers, users with limited or standard privileges may sometimes have write access to their program data folders. This could allow them to delete the AnyConnect profile file and thereby circumvent the always-on feature. To prevent this, configure the computer to restrict access to the following folders (or at least the Cisco sub-folder):
•
•
Guidelines from Previous Releases Still in Effect
The Cisco AnyConnect Secure Mobility Client Administrator Guide, Release 2.5, incorporates most of the guidelines reported in previous releases that remain in effect. The following sections address the remaining guidelines.
AnyConnect Smart Card Support
AnyConnect supports smart cards in the following environments:
•
•
AnyConnect does not support:
•
•
Responding to a TUN/TAP Error Message with Mac OS X 10.5
During the installation of AnyConnect on Mac OS X 10.5 and earlier versions, the following error message sometimes appears:
A version of the TUN virtual network driver is already installed on this system that is incompatible with the AnyConnect client. This is a known issue with OS X version 10.5 and prior, and has been resolved in 10.6. Please uninstall any VPN client, speak with your System Administrator, or reference the AnyConnect Release Notes for assistance in resolving this issue.Mac OS X 10.6 resolves this issue because it provides the version of the TUN/TAP virtual network driver AnyConnect requires.
Versions of Mac OS X earlier than 10.6 do not include a TUN/TAP virtual network driver, so AnyConnect installs its own on these operating systems. However, some software such as Parallels, software that manages data cards, and some VPN applications install their own TUN/TAP driver. The AnyConnect installation software displays the error message above because the driver is already present, but its version is incompatible with AnyConnect.
To install AnyConnect, you must remove the TUN/TAP virtual network driver.
Note
To remove the TUN/TAP virtual network driver, open the console application and enter the following commands:
sudo rm -rf /Library/Extensions/tap.kext
sudo rm -rf /Library/Extensions/tun.kext
sudo rm -rf /Library/StartupItems/tap
sudo rm -rf /Library/StartupItems/tun
sudo rm -rf /System/Library/Extensions/tun.kext
sudo rm -rf /System/Library/Extensions/tap.kext
sudo rm -rf /System/Library/StartupItems/tap
sudo rm -rf /System/Library/StartupItems/tun
After entering these commands, restart Mac OS, then re-install AnyConnect.
64-bit Internet Explorer Not Supported
AnyConnect installation via WebLaunch does not support 64-bit versions of Internet Explorer. Please instruct users of x64 (64-bit) Windows versions supported by AnyConnect to use the 32-bit version of Internet Explorer or Firefox to install WebLaunch. (At this time, Firefox is available only in a 32-bit version.)
Avoid Wireless-Hosted-Network
Using the Windows 7 Wireless Hosted Network feature can make AnyConnect unstable. When using AnyConnect, we do not recommend enabling this feature or running front-end applications that enable it (e.g., Connectify or Virtual Router).
AnyConnect Requires That the ASA Be Configured to Accept TLSv1 Traffic
The AnyConnect client cannot establish a connection with the following ASA settings for "ssl server-version":
•
•
Flexibility in the Sequence and Method Used to Install Start Before Logon and DART Components
Previously, in order to use the Start Before Logon components for Windows, the same installation method was required for both AnyConnect and the Start Before Logon components. Both needed to be pre-deployed or both needed to be web-deployed. AnyConnect Release 2.4 eliminates this requirement. This allows the client to be deployed by one method and, perhaps at a later time, the Start Before Logon components to be installed by the same or another method. The Start Before Logon component still has the requirement that AnyConnect be installed first.
Another new behavior for AnyConnect Release 2.4 is that if SBL or DART is manually uninstalled from an endpoint that then connects, these components will be re-installed. This behavior will only occur if the head-end configuration specifies that these components be installed and the preferences (set on the endpoint) permit upgrades. Previously these components would not be re-installed in this scenario without uninstalling and re-installing AnyConnect.
System Requirements
This section identifies the general management and endpoint requirements for this release. For endpoint OS support and license requirements for each feature, see AnyConnect Secure Mobility Client Features, Licenses, and OSs, Release 2.5.
AnyConnect 2.5 installations can coexist with other VPN clients, including IPsec clients, on all supported endpoints; however, we do not support running AnyConnect while other VPN clients are running.
The following sections identify the minimum management and endpoint requirements:
•
Security Appliance Software Requirements
For the latest fixes, the ASAs must be running the following:
•
•
•
AnyConnect 2.5 requires the following:
•
•
The minimum supported version of Cisco Secure Desktop is 3.2.2 or later.
We also recommend upgrading to ASDM 6.3(1) or later so that you can use the AnyConnect profile editor to configure many of the AnyConnect features. You can use ASDM 6.3(1) in combination with ASA 8.0(2) or later. If you choose not to upgrade ASDM, you must use an editor to add the XML tags to the AnyConnect profile if you want to deploy the new AnyConnect features.
You must upgrade to ASA 8.3(1) if you want to do the following:
•
•
•
•
Microsoft Windows
For WebLaunch, use Internet Explorer 6.0 or later or Firefox 3.0+, and enable ActiveX or install Sun JRE 1.4+.
Windows Versions
•
AnyConnect requires a clean install if you upgrade from Windows XP to Windows 7.
If you upgrade from Windows Vista to Windows 7, manually uninstall AnyConnect first, then after the upgrade, reinstall it manually or by establishing a web-based connection to a security appliance configured to install it. Uninstalling before the upgrade and reinstalling AnyConnect afterwards is necessary because the upgrade does not preserve the Cisco AnyConnect Virtual Adapter.
AnyConnect is compatible with 3G data cards which interface with Windows 7 via a WWAN adapter.
•
AnyConnect requires a clean install if you upgrade from Windows XP to Windows Vista.
•
Note
Windows Requirements
•
•
•
•
–
–
–
•
Linux
The following sections show the supported Linux distributions and requirements.
Linux Distributions
•
•
We do not validate other Linux distributions. We will consider requests to validate other Linux distributions for which you experience issues, and provide fixes at our discretion.
Linux Requirements
•
•
•
•
•
•
•
•
•
•
•
•
gdk 2.0.0,
libpango 1.0.•
•
Note
Mac OS X
AnyConnect 2.5 supports the following versions of Mac OS:
•
•
•
AnyConnect requires 50MB of hard disk space.
If you upgrade from one major Mac OS X release to another (for example 10.5 to 10.6), manually uninstall AnyConnect first, then after the upgrade, reinstall it manually or by establishing a web-based connection to a security appliance configured to install it.
Windows Mobile
Note
Refer to the End-of-Life Announcement for the Cisco AnyConnect Secure Mobility Client on Windows Mobile for support and availability details.
Although the devices listed below were originally qualified with AnyConnect for Windows Mobile 2.5.02517, these releases were removed from customer availability due to a security vulnerability. Please contact your authorized support representative for further details.
AnyConnect 2.5 is compatible with Windows Mobile 6.5, 6.1, 6.0 and 5.0 Professional and Classic for touch-screen devices only. Users have reported success with most touch-screen devices running these versions of Windows Mobile. However, to ensure interoperability, we guarantee compatibility only with the devices we test, as follows:
•
•
•
•
•
•
•
•
AnyConnect Support Policy
We support all AnyConnect software versions available on the Cisco AnyConnect VPN Software Download site; however, we provide fixes and enhancements only in maintenance or feature releases based on the most recently released version.
Caveats
Caveats describe unexpected behavior or defects in Cisco software releases.
Note
The following sections lists the Severities 2 and 3 caveats:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Caveats Resolved by AnyConnect 2.5.6005
Caveats Resolved by AnyConnect 2.5.3055
Table 2 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.3055 resolves.
Open Caveats in Release 2.5.3055
Table 3 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility Client Releases 2.5.3055.
Caveats Resolved by AnyConnect 2.5.3054
Table 4 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.3054 resolves.
Open Caveats in Release 2.5.3054
Table 5 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility Client Releases 2.5.3054.
Caveats Resolved by AnyConnect 2.5.3051
Table 6 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.3051 resolves.
Open Caveats in Release 2.5.3051
Table 7 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility Client Releases 2.5.3051.
Caveats Resolved by AnyConnect 2.5.3046
Table 8 shows the caveat that AnyConnect Secure Mobility Client Release 2.5.3046 resolves.
Table 8 Caveat Resolved by Cisco AnyConnect Secure Mobility Client Release 2.5.3046
CSCtq84525
Anyconnect 2.5.3041 CertPathValidatorException: timestamp check failed
Open Caveats in AnyConnect 2.5.3041 and 2.5.3046
Table 9 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility Client Releases 2.5.3041 and 2.5.3046.
Caveats Resolved by AnyConnect 2.5.3041
Table 10 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.3041 resolves.
Caveat Resolved by AnyConnect 2.5.2019
Table 11 shows the caveat that AnyConnect Secure Mobility Client Release 2.5.2019 resolves.
Table 11 Caveat Resolved by Cisco AnyConnect Secure Mobility Client Release 2.5.2019
CSCtn21228
AnyConnect Profile Editor enabling all Extended Key Usages causes error
Open Caveats in AnyConnect 2.5.2014-2.5.2019
Table 12 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility client Releases 2.5.2019, 2.5.2019, 2.5.2017, and 2.5.2014.
Caveat Resolved by AnyConnect 2.5.2017
Table 13 shows the caveat that AnyConnect Secure Mobility Client Release 2.5.2017 resolves.
Table 13 Caveat Resolved by Cisco AnyConnect Secure Mobility Client Release 2.5.2017
CSCtj79104
Multicast traffic should not be tunneled with split-include tunneling config
Caveat Resolved by AnyConnect 2.5.2014
Table 14 shows the caveat that AnyConnect Secure Mobility Client Release 2.5.2014 resolves.
Table 14 Caveat Resolved by Cisco AnyConnect Secure Mobility Client Release 2.5.2014
CSCte46102
AnyConnect unable to browse websites when connected
Caveat Resolved by AnyConnect 2.5.2011
Table 15 shows the caveat that AnyConnect Secure Mobility Client Release 2.5.2011 resolves.
Table 15 Caveat Resolved by Cisco AnyConnect Secure Mobility Client Release 2.5.2011
CSCtk85347
Invalid certs result in connection breakage
Open Caveats in AnyConnect 2.5.2001-2.5.2011
Table 16 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility client Releases 2.5.2011, 2.5.2010, 2.5.2006, and 2.5.2001.
Caveats Resolved by AnyConnect 2.5.2010
Table 17 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.2010 resolves.
Caveats Resolved by AnyConnect 2.5.2006
Table 18 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.2006 resolves.
Caveats Resolved by AnyConnect 2.5.2001
Table 19 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.2001 resolves.
Caveats Resolved by AnyConnect 2.5.1025
Table 20 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.1025 resolves.
Open Caveats in AnyConnect 2.5.1025
Table 21 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility client in AnyConnect Release 2.5.1025.
Caveats Resolved by AnyConnect 2.5.0217
Table 22 shows the caveats that AnyConnect Secure Mobility Client Release 2.5.0217 resolves.
Open Caveats in AnyConnect 2.5.0217
Table 23 lists the caveats that are unresolved in Cisco AnyConnect Secure Mobility client in AnyConnect Release 2.5.0217.
Notices/Licensing
See the following sections for Cisco AnyConnect Secure Mobility client license information.
License Options
For brief descriptions and example product numbers (SKUs) of the AnyConnect user license options, see Cisco Secure Remote Access: VPN Licensing Overview.
For the latest detailed information about the AnyConnect user license options, see Managing Feature Licenses in the Cisco ASA 5500 Series Configuration Guide using the CLI, 8.2.
End-User License Agreement
For the end-user license agreement, go to: http://www.cisco.com/univercd/cc/td/doc/es_inpck/eu1jen__.pdf
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
For Open Source License information for this product, please see the following link: http://www.cisco.com/en/US/docs/security/asa/asa80/license/opensrce.html#wp50053.
Related Documentation
For more information, see the following documents:
•
•
•
•
•
•
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.
© 2004-2012 Cisco Systems, Inc. All rights reserved.
