on 08-28-2013 11:32 PM
Introduction:
This document describes the process of configuring L2TP over IPSEC between Cisco IOS router and windows 8.
Prerequesites:
This document requires a basic understanding of IPSec protocol. To learn more about IPSec, please refer to An Introduction to IP Security (IPSec) Encryption.
Components Used:
Cisco IOS® Software Release 12.4
Cisco 2961 router
Windows 8 machine
Diagram:
Configuration on Cisco IOS router:
version 12.4
!
hostname L2TP
!
!
aaa new-model
!
!
aaa authentication ppp VPDN_AUTH local
!
!
vpdn enable
!
vpdn-group L2TP
! Default L2TP VPDN group
accept-dialin
protocol l2tp
virtual-template 1
no l2tp tunnel authentication
!
!
!
username cisco privilege 15 password 0 cisco
!
!
crypto isakmp policy 1
encr 3des
hash sha
authentication pre-share
group 2
lifetime 86400
!
!
crypto isakmp key cisco123 address 0.0.0.0 0.0.0.0
!
!
crypto ipsec transform-set L2TP-Set2 esp-3des esp-sha-hmac
mode transport
!
crypto dynamic-map dyn-map 10
set nat demux
set transform-set L2TP-Set2 L2TP-Set
!
!
crypto map outside_map 65535 ipsec-isakmp dynamic dyn-map
!
!
!
interface Loopback0
ip address 192.168.47.1 255.255.255.0
ip nat inside
ip virtual-reassembly
!
interface Loopback1
description loopback for IPsec-pool
ip address 1.1.1.11 255.255.255.255
!
interface FastEthernet0/0
ip address 47.47.47.2 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
crypto map outside_map
!
!
interface Virtual-Template1
ip unnumbered Loopback1
peer default ip address pool l2tp-pool
ppp authentication ms-chap-v2 VPDN_AUTH
!
!
!
ip local pool l2tp-pool 1.1.1.1 1.1.1.10
ip route 0.0.0.0 0.0.0.0 47.47.47.1
!
ip nat inside source list NAT interface FastEthernet0/0 overload
!
ip access-list extended NAT
deny ip 192.168.47.0 0.0.0.255 1.1.1.0 0.0.0.255
permit ip 192.167.47.0 0.0.0.255 any
!
!
!
End
Windows 8 Configuration:
1. Open control panel and select Network and Sharing Centre:
2. Select “Set up a new connection Entry”:
3. Select “Connect to a Workplace”:
4. Choose “Use my Internet Connection”:
5. Type in the IP address or FQDN of the router and name the connection and click on create:
6. Once that is done, go back to control panel and network and sharing center and select “Change adapter settings”:
7. Right click on the connection entry and click on properties:
8. Make sure the IP address or the FQDN is correct in the General tab:
9. In the Security tab, make sure type of VPN is “L2TP/IPSEC”. Then Click on advance settings and add pre-share key:
10. Then select “Allow these protocol” and make sure MS-CHAP v2 is selected:
11. To connect, left click on the network icon in the task bar:
12. You will see the following, type in your user name and password and click on OK:
13. If everything is good you will see the following screen:
Successful Debugs
Aug 26 02:45:42.559: ISAKMP (0:0): received packet from 57.57.57.2 dport 500 sport 500 Global (N) NEW SA
Aug 26 02:45:42.563: ISAKMP: Created a peer struct for 57.57.57.2, peer port 500
Aug 26 02:45:42.563: ISAKMP: New peer created peer = 0x65002704 peer_handle = 0x80000005
Aug 26 02:45:42.563: ISAKMP: Locking peer struct 0x65002704, refcount 1 for crypto_isakmp_process_block
Aug 26 02:45:42.567: ISAKMP: local port 500, remote port 500
Aug 26 02:45:42.567: insert sa successfully sa = 6797AE3C
Aug 26 02:45:42.571: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
Aug 26 02:45:42.571: ISAKMP:(0):Old State = IKE_READY New State = IKE_R_MM1
!--- Output supressed
Aug 26 02:45:42.587: ISAKMP:(0):Checking ISAKMP transform 1 against priority 1 policy
Aug 26 02:45:42.595: ISAKMP: encryption 3DES-CBC
Aug 26 02:45:42.595: ISAKMP: hash SHA
Aug 26 02:45:42.595: ISAKMP: default group 2
Aug 26 02:45:42.595: ISAKMP: auth pre-share
Aug 26 02:45:42.595: ISAKMP: life type in seconds
Aug 26 02:45:42.595: ISAKMP: life duration (VPI) of 0x0 0x0 0x70 0x80
Aug 26 02:45:42.595: ISAKMP:(0):atts are acceptable. Next payload is 0
Aug 26 02:45:42.595: ISAKMP:(0):Acceptable atts:actual life: 0
Aug 26 02:45:42.595: ISAKMP:(0):Acceptable atts:life: 0
Aug 26 02:45:42.595: ISAKMP:(0):Fill atts in sa vpi_length:4
Aug 26 02:45:42.595: ISAKMP:(0):Fill atts in sa life_in_seconds:28800
Aug 26 02:45:42.595: ISAKMP:(0):Returning Actual lifetime: 28800
Aug 26 02:45:42.595: ISAKMP:(0)::Started lifetime timer: 28800.
!--- Output supressed
Aug 26 02:45:42.595: ISAKMP:(0): constructed NAT-T vendor-rfc3947 ID
Aug 26 02:45:42.595: ISAKMP:(0): sending packet to 57.57.57.2 my_port 500 peer_port 500 (R) MM_SA_SETUP
Aug 26 02:45:42.595: ISAKMP:(0):Sending an IKE IPv4 Packet.
Aug 26 02:45:42.599: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
Aug 26 02:45:42.599: ISAKMP:(0):Old State = IKE_R_MM1 New State = IKE_R_MM2
Aug 26 02:45:42.651: ISAKMP (0:0): received packet from 57.57.57.2 dport 500 sport 500 Global (R) MM_SA_SETUP
Aug 26 02:45:42.655: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
Aug 26 02:45:42.655: ISAKMP:(0):Old State = IKE_R_MM2 New State = IKE_R_MM3
Aug 26 02:45:42.659: ISAKMP:(0): processing KE payload. message ID = 0
Aug 26 02:45:42.691: ISAKMP:(0): processing NONCE payload. message ID = 0
Aug 26 02:45:42.691: ISAKMP:(0):found peer pre-shared key matching 57.57.57.2
Aug 26 02:45:42.695: ISAKMP:received payload type 20
Aug 26 02:45:42.695: ISAKMP:received payload type 20
Aug 26 02:45:42.695: ISAKMP:(1004):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
Aug 26 02:45:42.699: ISAKMP:(1004):Old State = IKE_R_MM3 New State = IKE_R_MM3
Aug 26 02:45:42.703: ISAKMP:(1004): sending packet to 57.57.57.2 my_port 500 peer_port 500 (R) MM_KEY_EXCH
Aug 26 02:45:42.703: ISAKMP:(1004):Sending an IKE IPv4 Packet.
Aug 26 02:45:42.707: ISAKMP:(1004):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
Aug 26 02:45:42.707: ISAKMP:(1004):Old State = IKE_R_MM3 New State = IKE_R_MM4
Aug 26 02:45:42.735: ISAKMP (0:1004): received packet from 57.57.57.2 dport 500 sport 500 Global (R) MM_KEY_EXCH
Aug 26 02:45:42.739: ISAKMP:(1004):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
Aug 26 02:45:42.739: ISAKMP:(1004):Old State = IKE_R_MM4 New State = IKE_R_MM5
Aug 26 02:45:42.743: ISAKMP:(1004): processing ID payload. message ID = 0
Aug 26 02:45:42.743: ISAKMP (0:1004): ID payload
next-payload : 8
type : 1
address : 57.57.57.2
protocol : 0
port : 0
length : 12
Aug 26 02:45:42.747: ISAKMP:(0):: peer matches *none* of the profiles
Aug 26 02:45:42.747: ISAKMP:(1004): processing HASH payload. message ID = 0
Aug 26 02:45:42.751: ISAKMP:(1004):SA authentication status:
authenticated
Aug 26 02:45:42.751: ISAKMP:(1004):SA has been authenticated with 57.57.57.2
Aug 26 02:45:42.751: ISAKMP: Trying to insert a peer 47.47.47.2/57.57.57.2/500/, and inserted successfully 65002704.
Aug 26 02:45:42.751: ISAKMP:(1004):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
Aug 26 02:45:42.751: ISAKMP:(1004):Old State = IKE_R_MM5 New State = IKE_R_MM5
Aug 26 02:45:42.751: ISAKMP:(1004):SA is doing pre-shared key authentication using id type ID_IPV4_ADDR
Aug 26 02:45:42.751: ISAKMP (0:1004): ID payload
next-payload : 8
type : 1
address : 47.47.47.2
protocol : 17
port : 500
length : 12
Aug 26 02:45:42.751: ISAKMP:(1004):Total payload length: 12
Aug 26 02:45:42.751: ISAKMP:(1004): sending packet to 57.57.57.2 my_port 500 peer_port 500 (R) MM_KEY_EXCH
Aug 26 02:45:42.751: ISAKMP:(1004):Sending an IKE IPv4 Packet.
Aug 26 02:45:42.751: ISAKMP:(1004):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
Aug 26 02:45:42.751: ISAKMP:(1004):Old State = IKE_R_MM5 New State = IKE_P1_COMPLETE
Aug 26 02:45:42.751: ISAKMP:(1004):Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE
Aug 26 02:45:42.751: ISAKMP:(1004):Old State = IKE_P1_COMPLETE New State = IKE_P1_COMPLETE
Aug 26 02:45:42.775: ISAKMP (0:1004): received packet from 57.57.57.2 dport 500 sport 500 Global (R) QM_IDLE
Aug 26 02:45:42.779: ISAKMP: set new node 1 to QM_IDLE
Aug 26 02:45:42.783: ISAKMP:(1004): processing HASH payload. message ID = 1
Aug 26 02:45:42.787: ISAKMP:(1004): processing SA payload. message ID = 1
Aug 26 02:45:42.787: ISAKMP:(1004):Checking IPSec proposal 1
Aug 26 02:45:42.787: ISAKMP: transform 1, ESP_AES
Aug 26 02:45:42.787: ISAKMP: attributes in transform:
Aug 26 02:45:42.787: ISAKMP: encaps is 2 (Transport)
Aug 26 02:45:42.787: ISAKMP: key length is 128
Aug 26 02:45:42.791: ISAKMP: authenticator is HMAC-SHA
Aug 26 02:45:42.791: ISAKMP: SA life type in seconds
Aug 26 02:45:42.791: ISAKMP: SA life duration (VPI) of 0x0 0x0 0xE 0x10
Aug 26 02:45:42.791: ISAKMP: SA life type in kilobytes
Aug 26 02:45:42.795: ISAKMP: SA life duration (VPI) of 0x0 0x3 0xD0 0x90
Aug 26 02:45:42.795: ISAKMP:(1004):atts are acceptable.
Aug 26 02:45:42.795: IPSEC(validate_proposal_request): proposal part #1
Aug 26 02:45:42.799: IPSEC(validate_proposal_request): proposal part #1,
(key eng. msg.) INBOUND local= 47.47.47.2, remote= 57.57.57.2,
local_proxy= 47.47.47.2/255.255.255.255/17/1701 (type=1),
remote_proxy= 57.57.57.2/255.255.255.255/17/1701 (type=1),
protocol= ESP, transform= NONE (Transport),
lifedur= 0s and 0kb,
spi= 0x0(0), conn_id= 0, keysize= 128, flags= 0x0
Aug 26 02:45:42.799: IPSEC(ipsec_process_proposal): transform proposal not supported for identity:
{esp-aes esp-sha-hmac }
Aug 26 02:45:42.799: ISAKMP:(1004): IPSec policy invalidated proposal with error 256
Aug 26 02:45:42.799: ISAKMP:(1004):Checking IPSec proposal 2
Aug 26 02:45:42.799: ISAKMP: transform 1, ESP_3DES
Aug 26 02:45:42.799: ISAKMP: attributes in transform:
Aug 26 02:45:42.799: ISAKMP: encaps is 2 (Transport)
Aug 26 02:45:42.799: ISAKMP: authenticator is HMAC-SHA
Aug 26 02:45:42.799: ISAKMP: SA life type in seconds
Aug 26 02:45:42.799: ISAKMP: SA life duration (VPI) of 0x0 0x0 0xE 0x10
Aug 26 02:45:42.799: ISAKMP: SA life type in kilobytes
Aug 26 02:45:42.799: ISAKMP: SA life duration (VPI) of 0x0 0x3 0xD0 0x90
Aug 26 02:45:42.799: ISAKMP:(1004):atts are acceptable.
Aug 26 02:45:42.799: IPSEC(validate_proposal_request): proposal part #1
Aug 26 02:45:42.799: IPSEC(validate_proposal_request): proposal part #1,
(key eng. msg.) INBOUND local= 47.47.47.2, remote= 57.57.57.2,
local_proxy= 47.47.47.2/255.255.255.255/17/1701 (type=1),
remote_proxy= 57.57.57.2/255.255.255.255/17/1701 (type=1),
protocol= ESP, transform= NONE (Transport),
lifedur= 0s and 0kb,
spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0
Aug 26 02:45:42.799: ISAKMP:(1004): processing NONCE payload. message ID = 1
Aug 26 02:45:42.799: ISAKMP:(1004): processing ID payload. message ID = 1
Aug 26 02:45:42.799: ISAKMP:(1004): processing ID payload. message ID = 1
Aug 26 02:45:42.799: ISAKMP:(1004):QM Responder gets spi
Aug 26 02:45:42.799: ISAKMP:(1004):Node 1, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH
Aug 26 02:45:42.799: ISAKMP:(1004):Old State = IKE_QM_READY New State = IKE_QM_SPI_STARVE
Aug 26 02:45:42.799: ISAKMP:(1004): Creating IPSec SAs
Aug 26 02:45:42.799: inbound SA from 57.57.57.2 to 47.47.47.2 (f/i) 0/ 0
(proxy 57.57.57.2 to 47.47.47.2)
Aug 26 02:45:42.799: has spi 0x1310AE1E and conn_id 0
Aug 26 02:45:42.799: lifetime of 3600 seconds
Aug 26 02:45:42.799: lifetime of 250000 kilobytes
Aug 26 02:45:42.799: outbound SA from 47.47.47.2 to 57.57.57.2 (f/i) 0/0
(proxy 47.47.47.2 to 57.57.57.2)
Aug 26 02:45:42.799: has spi 0x139264F8 and conn_id 0
Aug 26 02:45:42.799: lifetime of 3600 seconds
Aug 26 02:45:42.799: lifetime of 250000 kilobytes
Aug 26 02:45:42.799: ISAKMP:(1004): sending packet to 57.57.57.2 my_port 500 peer_port 500 (R) QM_IDLE
Aug 26 02:45:42.799: ISAKMP:(1004):Sending an IKE IPv4 Packet.
Aug 26 02:45:42.799: ISAKMP:(1004):Node 1, Input = IKE_MESG_INTERNAL, IKE_GOT_SPI
Aug 26 02:45:42.799: ISAKMP:(1004):Old State = IKE_QM_SPI_STARVE New State = IKE_QM_R_QM2
Aug 26 02:45:42.799: IPSEC(key_engine): got a queue event with 1 KMI message(s)
Aug 26 02:45:42.799: IPSEC(policy_db_add_ident): src 47.47.47.2, dest 57.57.57.2, dest_port 1701
Aug 26 02:45:42.799: IPSEC(create_sa): sa created,
(sa) sa_dest= 47.47.47.2, sa_proto= 50,
sa_spi= 0x1310AE1E(319860254),
sa_trans= esp-3des esp-sha-hmac , sa_conn_id= 5
Aug 26 02:45:42.799: IPSEC(create_sa): sa created,
(sa) sa_dest= 57.57.57.2, sa_proto= 50,
sa_spi= 0x139264F8(328361208),
sa_trans= esp-3des esp-sha-hmac , sa_conn_id= 6
Aug 26 02:45:42.831: ISAKMP (0:1004): received packet from 57.57.57.2 dport 500 sport 500 Global (R) QM_IDLE
Aug 26 02:45:42.835: ISAKMP:(1004):deleting node 1 error FALSE reason "QM done (await)"
Aug 26 02:45:42.835: ISAKMP:(1004):Node 1, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH
Aug 26 02:45:42.839: ISAKMP:(1004):Old State = IKE_QM_R_QM2 New State = IKE_QM_PHASE2_COMPLETE
Aug 26 02:45:42.843: IPSEC(key_engine): got a queue event with 1 KMI message(s)
Aug 26 02:45:42.843: IPSEC(key_engine_enable_outbound): rec'd enable notify from ISAKMP
Aug 26 02:45:42.843: IPSEC(key_engine_enable_outbound): enable SA with spi 328361208/50
Aug 26 02:45:42.847: IPSEC(update_current_outbound_sa): updated peer 57.57.57.2 current outbound sa to SPI 139264F8
Aug 26 02:45:57.742: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
Aug 26 02:45:58.742: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
That looks good, but I think I need one other piece to connect from my Win 8.1 laptop to ProctorLabs. They have Group Authentication set with a username and password, which are each different strings. They have different L2TP authentication Groups for different Pods of Cisco equipment in their racks.I believe this example just relies upon pre-shared key for a single, Default L2TP connection. In addition, I also need to enter a CHAP username/password, whic this example does cover.
Unfortunately ProctorLabs relies upon the end of life Cisco VPN client, which I believe had only been updated up to Windows 7. I've tried other L2TP clients without success. It would seem natural to use the Windows L2TP mechanism, but I can't get past the Group Authentication username/password.
Thanks,
David
Hi,
I am having a different problem. I configured everything similar to the given configuration. But cant connect from my windows PC.
Here is my configuration:
!
vpdn enable
!
vpdn-group 2
! Default PPTP VPDN group
accept-dialin
protocol pptp
virtual-template 2
!
vpdn-group L2TP
! Default L2TP VPDN group
accept-dialin
protocol l2tp
virtual-template 1
no l2tp tunnel authentication
!
!
license udi pid CISCO2951/K9 sn FGL182711H0
hw-module ism 0
!
!
!
username root privilege 15 password 7 0200080B525756791C1F
!
redundancy
!
!
!
!
!
ip ssh version 2
!
!
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp key cisco1123 address 0.0.0.0
!
!
crypto ipsec transform-set L2TP-Set2 esp-3des esp-sha-hmac
mode transport
!
!
!
crypto dynamic-map dyn-map 10
set nat demux
set transform-set L2TP-Set2
crypto dynamic-map dyn-map 200
set nat demux
set transform-set L2TP-Set2
!
!
!
crypto map outside_map 65535 ipsec-isakmp dynamic dyn-map
!
!
!
!
!
interface Loopback2
description loopback for IPsec-pool
ip address 10.50.50.1 255.255.255.255
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 11.11.11.11 255.255.255.248
ip nat outside
ip virtual-reassembly in
duplex auto
speed auto
media-type rj45
crypto map outside_map
!
interface GigabitEthernet0/2
description LAN-P2P
ip address 172.20.2.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
duplex auto
speed auto
!
interface Virtual-Template1
ip unnumbered Loopback2
peer default ip address pool l2tp-pool
no keepalive
ppp encrypt mppe auto
ppp authentication ms-chap-v2 VPDN_AUTH
!
interface Virtual-Template2
ip unnumbered GigabitEthernet0/1
ip nat inside
ip virtual-reassembly in
peer default ip address pool BRANCH-VPDN
no keepalive
ppp encrypt mppe auto
ppp authentication chap ms-chap
!
!
router eigrp 10
network 10.13.13.0 0.0.0.255
network 172.20.2.0 0.0.0.3
redistribute static metric 1000 1 255 1 1500
passive-interface GigabitEthernet0/1
!
ip local pool BRANCH-VPDN 192.168.33.1 192.168.33.250
ip local pool l2tp-pool 10.50.50.10 10.50.50.20
ip forward-protocol nd
!
Please help me.
Hi Nikhil,
IOS (Cisco 887) doesn't permit these commands, are these for ASA?
And if so what split-tunnel configuration is required for IOS VPN?
what username and password to use while connecting vpn from windows ?
Thanks for your guidance, I tried to use your sample configuration, I can connected to my router (in office) and can reach my office LAN, but unfortunately I can't connect to the Internet through this VPN.
What should I do for this?
Because I'm road warrior user sometimes connect to public wifi and want to get secure link when sending/receiving email.
Thank you.
Hey did you radius or something for authentication?if not what username and password did you use while connecting?please tell me from the above configuration.
I'm creating
username uservpn privilage 15 password mypassword
and use the PSK: mynewsecret (cisco123 on the config above)
Additional info:
Check with my iPhone and Android Phone also Macbook OS X Yosemite this configuration work.
But cannot have internet connection. I can ping to local LAN and from local LAN can ping to VPN client.
okay thanks however my IKE phase 2 get completed and then the virtual interfaces dont come up. check this out
*Jun 24 19:09:36.026: ISAKMP:(1022):Old State = IKE_QM_R_QM2 New State = IKE_QM_PHASE2_COMPLETE
*Jun 24 19:10:10.090: ISAKMP (1022): received packet from 96.31.182.52 dport 4500 sport 4500 Global (R) QM_IDLE
*Jun 24 19:10:10.090: ISAKMP: set new node 963339295 to QM_IDLE
*Jun 24 19:10:10.090: ISAKMP:(1022): processing HASH payload. message ID = 963339295
*Jun 24 19:10:10.090: ISAKMP:(1022): processing DELETE payload. message ID = 963339295
*Jun 24 19:10:10.090: ISAKMP:(1022):peer does not do paranoid keepalives.
*Jun 24 19:10:10.090: ISAKMP:(1022):Enqueued KEY_MGR_DELETE_SAS for IPSEC SA (SPI:0x91BEBD16)
*Jun 24 19:10:10.090: ISAKMP:(1022):deleting node 963339295 error FALSE reason "Informational (in) state 1"
*Jun 24 19:10:10.090: ISAKMP: Failed to find peer index node to update peer_info_list
*Jun 24 19:10:10.094: ISAKMP (1022): received packet from 96.31.182.52 dport 4500 sport 4500 Global (R) QM_IDLE
*Jun 24 19:10:10.094: ISAKMP: set new node 406642821 to QM_IDLE
*Jun 24 19:10:10.094: ISAKMP:(1022): processing HASH payload. message ID = 406642821
*Jun 24 19:10:10.094: ISAKMP:(1022): processing DELETE payload. message ID = 406642821
*Jun 24 19:10:10.094: ISAKMP:(1022):peer does not do paranoid keepalives.
*Jun 24 19:10:10.094: ISAKMP:(1022):deleting SA reason "No reason" state (R) QM_IDLE (peer 96.31.182.52)
*Jun 24 19:10:10.094: ISAKMP:(1022):deleting node 406642821 error FALSE reason "Informational (in) state 1"
*Jun 24 19:10:10.094: ISAKMP: set new node 845537200 to QM_IDLE
*Jun 24 19:10:10.094: ISAKMP:(1022): sending packet to 96.31.182.52 my_port 4500 peer_port 4500 (R) QM_IDLE
*Jun 24 19:10:10.094: ISAKMP:(1022):Sending an IKE IPv4 Packet.
*Jun 24 19:10:10.094: ISAKMP:(1022):purging node 845537200
*Jun 24 19:10:10.094: ISAKMP:(1022):Input = IKE_MESG_INTERNAL, IKE_PHASE1_DEL
*Jun 24 19:10:10.094: ISAKMP:(1022):Old State = IKE_P1_COMPLETE New State = IKE_DEST_SA
*Jun 24 19:10:10.094: ISAKMP:(1022):deleting SA reason "No reason" state (R) QM_IDLE (peer 96.31.182.52)
*Jun 24 19:10:10.094: ISAKMP: Unlocking peer struct 0x3F8D6668 for isadb_mark_sa_deleted(), count 0
*Jun 24 19:10:10.094: ISAKMP:(1022):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Jun 24 19:10:10.094: ISAKMP:(1022):Old State = IKE_DEST_SA New State = IKE_DEST_SA
*Jun 24 19:10:10.094: ISAKMP: Deleting peer node by peer_reap for 96.31.182.52: 3F8D6668
CISCO2921#
hey my vpn is working but i am not able to access the internet through vpn. any solutions?
so i did split tunneling and it works.
Also what configuration you did on iphone and mac?because i am not able to connect
i am able to go on internet.
include ip nat inside into your virtual template interface.
and include that network into access-list
permit ip 1.1.1.0 0.0.0.255 any
it works
It's strange after got internet for few seconds (open web pages only 1-2 web page), then the internet connection stop again.
but the local LAN still reachable.
here is my ip access-list:
deny ip 192.168.0.0 0.0.0.255 192.168.0.64 0.0.0.31 (for my PPTP VPN)
ip access-list extended NAT
deny ip 192.168.0.0 0.0.0.255 192.168.0.64 0.0.0.31
deny ip 192.168.0.0 0.0.0.255 1.1.1.0 0.0.0.255
permit ip 192.168.0.0 0.0.0.255 any
permit ip 1.1.1.0 0.0.0.255 any
ip local pool L2TP-Pool 1.1.1.1 1.1.1.10
interface Loopback1
description loopback for L2TP-Pool
ip address 1.1.1.11 255.255.255.255
interface Virtual-Template2
description L2TP_VPN_Port
ip unnumbered Loopback1
ip nat inside
ip virtual-reassembly in
peer default ip address pool L2TP-Pool
no keepalive
ppp encrypt mppe 128
ppp authentication ms-chap-v2
Working just for a few seconds (open 2 webpages), then internet down again.
Thanks !!! Great tutorial !
works great with windows 7 but I cannot make it work with any windows 10 client
I may be misunderstanding some terminology, but...
When I read the software config guide for 15.5M, it states (I'm paraphrasing) that l2tp connectivity is supported on router to router connections; client to router is done with PPTP.
Why is that?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: