V
V
Vladimir2020-04-02 11:34:05
VPN
Vladimir, 2020-04-02 11:34:05

How to properly configure NAT for IPSec VPN clients on ASA 5510?

Good afternoon, I don’t understand why VPN users don’t see internal resources, I tried everything ...
The config is here:

Result of the command: "show running-config"

: Saved
:
ASA Version 8.2(5) 
!
hostname vpn2
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
name 192.168.0.0 localnet
!
interface Ethernet0/0
 nameif inside
 security-level 0
 ip address 192.168.10.10 255.255.255.0 
!
interface Ethernet0/1
 nameif outside
 security-level 0
 ip address x.x.x.165 255.255.255.248 
!
interface Ethernet0/2
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Ethernet0/3
 shutdown
 no nameif
 no security-level
 no ip address
!
interface Management0/0
 nameif management
 security-level 100
 ip address 192.168.1.2 255.255.255.0 
 management-only
!
ftp mode passive
same-security-traffic permit inter-interface
access-list VPN_splitTunnelAcl standard permit localnet 255.255.0.0 
access-list inside_nat0_outbound extended permit ip localnet 255.255.0.0 192.168.201.0 255.255.255.0 
access-list inside_access_in extended permit ip 192.168.10.0 255.255.255.0 192.168.201.0 255.255.255.0 
access-list inside_access_in extended permit ip 192.168.10.0 255.255.255.0 any 
access-list inside_access_in extended permit ip 192.168.201.0 255.255.255.0 any 
pager lines 24
logging asdm informational
mtu management 1500
mtu inside 1500
mtu outside 1500
ip local pool VPN 192.168.201.1-192.168.201.255 mask 255.255.255.0
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (inside) 101 interface
nat (management) 101 0.0.0.0 0.0.0.0
nat (inside) 0 access-list inside_nat0_outbound
static (outside,inside) 192.168.10.0 192.168.201.0 netmask 255.255.255.0 
access-group inside_access_in in interface inside
route outside 0.0.0.0 0.0.0.0 x.x.x.161 1
route inside 0.0.0.0 0.0.0.0 192.168.10.1 tunneled
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac 
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac 
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac 
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac 
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac 
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac 
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac 
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac 
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac 
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac 
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs group1
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 86400
telnet timeout 5
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
 anyconnect-essentials
group-policy VPN internal
group-policy VPN attributes
 dns-server value 192.168.10.2 8.8.8.8
 vpn-tunnel-protocol IPSec 
 split-tunnel-policy tunnelspecified
 split-tunnel-network-list value VPN_splitTunnelAcl
username vpnuser password 7Bdumxv8hUcgjd3b encrypted privilege 0
username vpnuser attributes
 vpn-group-policy VPN
tunnel-group VPN type remote-access
tunnel-group VPN general-attributes
 address-pool VPN
 default-group-policy VPN
tunnel-group VPN ipsec-attributes
 pre-shared-key *****
!
class-map inspection_default
 match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
 parameters
  message-length maximum client auto
  message-length maximum 512
policy-map global_policy
 class inspection_default
  inspect dns preset_dns_map 
  inspect ftp 
  inspect h323 h225 
  inspect h323 ras 
  inspect rsh 
  inspect rtsp 
  inspect esmtp 
  inspect sqlnet 
  inspect skinny  
  inspect sunrpc 
  inspect xdmcp 
  inspect sip  
  inspect netbios 
  inspect tftp 
  inspect ip-options 
!
service-policy global_policy global
prompt hostname context 
no call-home reporting anonymous
Cryptochecksum:a434346b011125b22da8cbfac75f1c15
: end

Answer the question

In order to leave comments, you need to log in

1 answer(s)
G
gosha-z, 2020-04-06
@gosha-z

1. You mixed up name and object/object-group (I don't remember if they were already in 8.2 or not). In any case, the VPN_splitTunnelAcl must explicitly describe the network.
2. Traffic from the internal network to the network allocated for remote access should not be flown. More precisely, it must natitsya "into itself."
3. There are excellent Configuration Examples and Technotes on cisco.com.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question