No results found
We couldn't find anything using that term, please try searching for something else.
Introduction Layer 2 Tunneling Protocol (L2TP) over IPSec provides the capability to deploy and administer an L2TP VPN solution alongside the IPSec V
Layer 2 Tunneling Protocol (L2TP) over IPSec provides the capability to deploy and administer an L2TP VPN solution alongside the IPSec VPN and firewall services in a single platform. The primary benefit of the configuration of L2TP over IPSec in a remote access scenario is that remote users can access a VPN over a public IP network without a gateway or a dedicated line, which enables remote access from virtually any place with plain old telephone service (POTS). An additional benefit is that the only client requirement for VPN access is the use of Windows with Microsoft Dial-Up Networking (DUN). No additional client software, such as the Cisco VPN client software, is required.
This document provides a sample configuration for the native L2TP/IPSec Android client. It takes you through all the necessary commands required on a Cisco Adaptive Security Appliance (ASA), as well as the steps to be taken on the Android device itself.
There are no specific requirement for this document .
The information in this document is based on the following software and hardware versions:
The information in this document was create from device in a specific lab environment . All is started of the device used in this document start with a clear ( default ) configuration . If your network is live , make sure that you understand the potential impact of any command .
This section describes the information one would need in order to configure the features described in this document.
This procedure describes how to configure the L2TP/IPSec connection on the Android:
These is are are the require ASA Internet Key Exchange Version 1 ( ikev1 ) ( Internet Security Association and Key Management Protocol [ ISAKMP ] ) policy setting that allow native VPN client , integrate with the operating system on an endpoint , to make a VPN connection to the ASA when L2TP over ipsec protocol is used :
Note: The ASA supports only the PPP authentications PAP and MS-CHAP (versions 1 and 2) on the local database. The Extensible Authentication Protocol (EAP) and CHAP are performed by proxy authentication servers. Therefore, if a remote user belongs to a tunnel group configured with the authentication eap-proxy or authentication chap commands and if the ASA is configured to use the local database, that user will be unable to connect.
Furthermore, Android does not support PAP and, because Lightweight Directory Access Protocol (LDAP) does not support MS-CHAP, LDAP is not a viable authentication mechanism. The only workaround is to use RADIUS. See Cisco Bug ID CSCtw58945, “L2TP over IPSec connections fail with ldap authorization and mschapv2,” for further details on issues with MS-CHAP and LDAP.
This procedure describes how to configure the L2TP/IPSec connection on the ASA:
note : use the Command Lookup Tool ( register customer only ) in order to obtain more information on the command used in this section .
This example shows the configuration file commands that ensure ASA compatibility with a native VPN client on any operating system.
Username <name> password <passwd> mschap
ip local pool l2tp-ipsec_address 192.168.1.1-192.168.1.10
group - policy l2tp - ipsec_policy internal
group-policy l2tp-ipsec_policy attributes
dns-server value <dns_server>
vpn-tunnel-protocol l2tp-ipsec
tunnel - group DefaultRAGroup general - attribute
default - group - policy l2tp - ipsec_policy
address-pool l2tp-ipsec_address
tunnel-group DefaultRAGroup ipsec-attributes
pre-shared-key *
tunnel-group DefaultRAGroup ppp-attributes
no authentication pap
authentication chap
authentication ms-chap-v1
authentication ms-chap-v2
crypto ipsec transform-set trans esp-3des esp-sha-hmac
crypto ipsec transform-set trans mode transport
crypto dynamic - map dyno 10 set transform - set set trans
crypto map vpn 65535 ipsec-isakmp dynamic dyno
crypto map vpn interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
Username <name> password <passwd> mschap
ip local pool l2tp-ipsec_address 192.168.1.1-192.168.1.10
group - policy l2tp - ipsec_policy internal
group-policy l2tp-ipsec_policy attributes
dns-server value <dns_server>
vpn-tunnel-protocol l2tp-ipsec
tunnel - group DefaultRAGroup general - attribute
default - group - policy l2tp - ipsec_policy
address-pool l2tp-ipsec_addresses
tunnel-group DefaultRAGroup ipsec-attributes
pre-shared-key *
tunnel-group DefaultRAGroup ppp-attributes
no authentication pap
authentication chap
authentication ms-chap-v1
authentication ms-chap-v2
crypto ipsec ikev1 transform-set my-transform-set-ikev1 esp-3des esp-sha-hmac
crypto ipsec ikev1 transform-set my-transform-set-ikev1 mode transport
crypto dynamic - map dyno 10 set ikev1 transform - set my - transform - set - ikev1
crypto map vpn 20 ipsec-isakmp dynamic dyno
crypto map vpn interface outside
crypto is enable ikev1 enable outside
crypto ikev1 policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
Use this section to confirm that your configuration works properly.
This procedure is describes describe how to set up the connection :
This procedure is describes describe how to disconnect :
Use these commands in order to confirm that your connection works properly.
Note: The Output Interpreter Tool (registered customers only) supports certain show commands. Use the Output Interpreter Tool in order to view an analysis of show command output.