IKEv1 Remote Access VPN on Cisco ASA for Legacy VPN Client

Even after the release of Cisco AnyConnect Secure Mobility Client which supports SSL VPN in addition to IKEv2 remote-access IPSec VPN, still out there are number of people who use legacy Cisco VPN client to connect IKEv1 remote-access IPSec VPN.
In the present scenario, we have to configure IKEv1 remote access VPN for Sales department and Engineering department of a company. Engineering users will have to be provided with access to web server as well as FTP server, while sales users may only have access to the web server.


ASA# 
ip local pool RA_VPN_POOL 10.10.10.1-10.10.10.255 mask 255.255.255.0
!
!
access-list IKE1_RA_VPN_SplitTunnelACL standard permit 192.168.100.0 255.255.255.0
!
access-list SALES_VPN_ACL extended permit tcp any host 192.168.100.10 eq www
access-list SALES_VPN_ACL extended permit udp any host 192.168.100.10 eq domain
access-list ENGR_VPN_ACL extended permit tcp any host 192.168.100.10 eq www
access-list ENGR_VPN_ACL extended permit tcp any host 192.168.100.10 eq ftp
access-list ENGR_VPN_ACL extended permit udp any host 192.168.100.10 eq domain
!
!
tunnel-group IKE1_RA_VPN type remote-access
tunnel-group IKE1_RA_VPN general-attributes
 address-pool RA_VPN_POOL
tunnel-group IKE1_RA_VPN ipsec-attributes
 ikev1 pre-shared-key *****
!
!
crypto ipsec ikev1 transform-set ESP_AES_SHA esp-aes esp-sha-hmac
crypto dynamic-map IKE1_RA_VPN_DYNMAP 500 set pfs
crypto dynamic-map IKE1_RA_VPN_DYNMAP 500 set ikev1 transform-set ESP_AES_SHA
crypto map IKE1_RA_MAP 200 ipsec-isakmp dynamic IKE1_RA_VPN_DYNMAP
crypto map IKE1_RA_MAP interface OUTSIDE
crypto ikev1 enable OUTSIDE
crypto ikev1 policy 20
 authentication pre-share
 encryption aes
 hash sha
 group 2
 lifetime 86400
!
!
group-policy SALES_RA_IKE1_VPN_GRP_POLICY internal
group-policy SALES_RA_IKE1_VPN_GRP_POLICY attributes
 dns-server value 192.168.100.10
 vpn-filter value SALES_VPN_ACL
 vpn-tunnel-protocol ikev1
 split-tunnel-policy tunnelspecified
 split-tunnel-network-list value IKE1_RA_VPN_SplitTunnelACL
 default-domain value pacificgroup.co.in
!
group-policy ENGR_RA_IKE1_VPN_GRP_POLICY internal
group-policy ENGR_RA_IKE1_VPN_GRP_POLICY attributes
 dns-server value 192.168.100.10
 vpn-filter value ENGR_VPN_ACL
 vpn-tunnel-protocol ikev1
 split-tunnel-policy tunnelspecified
 split-tunnel-network-list value IKE1_RA_VPN_SplitTunnelACL
 default-domain value pacificgroup.co.in
!
!
username salesuser password uXUrGApVTzN8lH14 encrypted
username salesuser attributes
 vpn-group-policy SALES_RA_IKE1_VPN_GRP_POLICY
 service-type remote-access
!
username engruser password osgMkcb3N.VlT8/u encrypted
username engruser attributes
 vpn-group-policy ENGR_RA_IKE1_VPN_GRP_POLICY
 service-type remote-access
!
!
object network VPN_USERS
 subnet 10.10.10.0 255.255.255.0
object network INSIDE_NETWORK
 subnet 192.168.100.0 255.255.255.0
!
nat (INSIDE,OUTSIDE) source static INSIDE_NETWORK INSIDE_NETWORK destination static VPN_USERS VPN_USERS



To Verify the connected users, use the following command.
ASA# sh vpn-sessiondb ra-ikev1-ipsec

Session Type: IKEv1 IPsec

Username     : engruser       Index        : 2
Assigned IP  : 10.10.10.1     Public IP    : 172.31.10.2
Protocol     : IKEv1 IPsec   
License      : Other VPN
Encryption   : AES128         Hashing      : SHA1
Bytes Tx     : 3775           Bytes Rx     : 10230
Group Policy : ENGR_RA_IKE1_VPN_GRP_POLICY
Tunnel Group : IKE1_RA_VPN
Login Time   : 18:15:43 UTC Thu Jul 11 2013
Duration     : 0h:02m:52s
Inactivity   : 0h:00m:00s
NAC Result   : Unknown
VLAN Mapping : N/A             VLAN         : none



To manually disconnect remote access VPN users, following command can be used.
ASA# vpn-sessiondb logoff ra-ikev1-ipsec

ASA# vpn-sessiondb logoff index 4    
Do you want to logoff the VPN session(s)? [confirm]
INFO: Session with Index = 4 has been logged off

Jul 12 00:30:30 [IKEv1]Group = IKE1_RA_VPN, Username = engruser, IP = 172.31.10.2, Session is being torn down. Reason: Administrator Reset

Comments

Post a Comment

Popular posts from this blog

Ansible-Playbook to display output of multiple show commands (using stdout_lines with Loop)

 In this playbook, we we'll see how we can get display of multiple show commands in stdout_lines format. We can make use of loops (or with_items) for submitting multiple commands, but debug output with stdout_lines does not gives the formatted result as it would give for single command. So in case of multiple commands, we can debug the output of each command separately in stdout_lines format.
Read more

Filtering Routes in BGP using Route-maps and Prefix-list

Image
Order of preference of attributes in BGP The order of preference varies based on whether the attributes are applied for inbound updates or outbound updates. For inbound updates the order of preference is:     route-map     filter-list     prefix-list, distribute-list For outbound updates the order of preference is:     prefix-list, distribute-list     filter-list     route-map NOTE: The attributes prefix-list and distribute-list are mutually exclusive, and only one command (neighbor distribute-list or neighbor prefix-list) can be applied to each inbound or outbound direction for a particular neighbor. Scenario: We own the AS500 and advertising a network block of 192.0.2.0/24 and 180.179.179.0/16 to two different ISPs. Objectives: Configure router R1 to establish eBGP neighbor relationship with ISP1. Configure router R1 to establish eBGP neighbor relationship with ISP2. Advertise  192.0.2.0/24 network to ISP1 only. Advertise 180.179.179.0/16 network to ISP2 only. Receive routes having n
Read more

Ansible-playbook for backing up running config of Cisco IOS

This ansible-playbook can be used to backup running configuration from Cisco IOS devices. You can refer to my earlier post Getting Started with your first ansible-playbook for Network Automation  to know about the parameters used in this playbook. Inventory file # Inventory file for Ansible [XE] ios-xe-mgmt.cisco.com:8181 ios-xe-mgmt-latest.cisco.com:8181 [XR] sbx-iosxr-mgmt.cisco.com:8181 [all:vars] ansible_network_os=ios Playbook --- - name: Define Parameters   hosts: XE   gather_facts: no   connection: network_cli   tasks:    - name: backup the config      ios_config:       backup: yes      register: backup_config    - name: Store the config to directory      copy:       src: "{{ backup_config.backup_path }}"       dest: "/tmp/backups/{{ inventory_hostname }}" Running the playbook [prashant@Prashant-VM01 ~]$ ansible-playbook play03.yml -i /home/prashant/inventory -u developer -k SSH password: PLAY [Define Parameters] **********************************************
Read more

Ansible Playbook for Network OS Upgrade with pre and post checks

You have 100s of network switches or routers that you need to upgrade. How much time would it take for you to do the upgrades? There are a lot number of sub-tasks involved while upgrading IOS image of a Cisco router or a switch. This time of upgradation can be reduced through automation from various Enterprise Configuration Management tools that also have ability to upgrade network OS. Though these tools give an easy to use graphical interface, but this requires you to have appropriate license and also restricts you to customize your upgrade process.
Read more

Cisco ASA Active/Active Failover Configuration

Image
Active/Active failover is only available to security appliances in multiple context mode. In an Active/Active failover configuration, both security appliances can pass network traffic. In Active/Active failover, you divide the security contexts on the security appliance into failover groups. A failover group is simply a logical group of one or more security contexts. You can create a maximum of two failover groups on the security appliance. The admin context is always a member of failover group 1. Any unassigned security contexts are also members of failover group 1 by default. We have already seen the configuration for Active/Standby failover in the previous article. This article focuses on how to configure an Active/Active Failover configuration on ASA Security Appliance.
Read more

VMware NSX Traffic Flow — East-West & North-South

Image
Understanding how traffic is flowing in NSX environment is an important aspect to successfully maintain and troubleshoot networks having NSX. In this post we'll understand hop-by-hop flow of traffic in East-West and North-South directions. East-West: VMs on Same Subnet, Same Host VM-1 has IP address 172.16.20.6 and VM-2 has IP address 172.16.20.7 VM-1 vNIC è Logical Switch (Segment ID 5002) è VM-2 vNIC
Read more

Export or Backup Azure Network Security Groups into CSV using PowerShell

There could be many use cases where you may want to export Network Security Groups into CSV. You might have question, how to export or backup Azure Network Security Groups into CSV. Here is the PowerShell script that you can use to export Azure Network Security Groups into CSV using PowerShell script. This script will export Network Security Group along with rules of all Active subscriptions into a CSV.
Read more

Get Model Number and Serial number of Cisco devices using ios_facts module

 This ansible-playbook will get the model number and serial number of Cisco devices using ios_facts module --- - name: Define Parameters   hosts: XE   gather_facts: no   connection: network_cli   tasks:    - name: Get the facts      ios_facts:        gather_subset: all    - name: Display model and serial number      debug:        msg: "Model number of {{ ansible_net_hostname }} is {{ ansible_net_model }} and serial number is {{ ansible_net_serialnum }}" ~ ~ https://docs.ansible.com/ansible/latest/modules/ios_facts_module.html
Read more