cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
454
Views
0
Helpful
5
Replies

Remote access via Anycconnect and IPSec cannot access local LAN issue

weixing73
Level 1
Level 1

Hi,

    I'm new to Cisco ASA and I create 2 VPN on an ASA5508:

1) AnyConnect for user to access network 192.168.8.0.

2) IPSec for user to access 192.168.30.0. (create using the ASDM IPSec wizard)

    Both can connect, but can only access the server list under the "dns-server" in their respective VPN settings... that is: AnyConnect user can only access 192.168.8.8, but not other PC in the same network. IPSec user can only access 192.168.30.8, but not other PC in the same network. 

   Any idea what might be the issue or I miss out anything??

   Thanks and have a nice day.

Below is the config:


ASA Version 9.4(1)
!
hostname Firewall
names
ip local pool FLNetAnyConnectClientPool 192.168.9.100-192.168.9.199
ip local pool PNetVPNPool 192.168.31.100-192.168.31.199 mask 255.255.255.0
!
interface GigabitEthernet1/1
nameif outside
security-level 0
ip address 123.123.123.188 255.255.255.248
!
interface GigabitEthernet1/2
nameif inside
security-level 100
no ip address
!
interface GigabitEthernet1/2.8
vlan 8
nameif FLNet
security-level 100
ip address 192.168.8.254 255.255.255.0
!
interface GigabitEthernet1/2.30
vlan 30
nameif PNet
security-level 80
ip address 192.168.30.254 255.255.255.0
!
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object network obj_any
subnet 0.0.0.0 0.0.0.0
object network FLNet-192.168.8.0
subnet 192.168.8.0 255.255.255.0
object network PNet-192.168.30.0
subnet 192.168.30.0 255.255.255.0
object network FLNetAnyConnect-192.168.9.0
subnet 192.168.9.0 255.255.255.0
object network PNetVPN-192.168.31.0
subnet 192.168.31.0 255.255.255.0
object network NETWORK_OBJ_192.168.31.0_24
subnet 192.168.31.0 255.255.255.0

access-list ACL-FLNetAnyConnect-Split-Tunnel standard permit 192.168.8.0 255.255.255.0
access-list ACL-FLNetAnyConnect-Split-Tunnel standard permit 192.168.9.0 255.255.255.0
access-list ACL-FLNetAnyConnect-Split-Tunnel standard permit 192.168.30.0 255.255.255.0
access-list VPH-GROUP_splitTunnelAcl standard permit 192.168.30.0 255.255.255.0
pager lines 24
logging enable
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu FLNet 1500
mtu PNet 1500

no failover
no monitor-interface service-module
icmp unreachable rate-limit 1 burst-size 1
asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (FLNet,outside) source static any any destination static FLNetAnyConnect-192.168.9.0 FLNetAnyConnect-192.168.9.0 no-proxy-arp route-lookup
nat (PNet,outside) source static any any destination static FLNetAnyConnect-192.168.9.0 FLNetAnyConnect-192.168.9.0 no-proxy-arp route-lookup
nat (outside,outside) source static any any destination static NETWORK_OBJ_192.168.31.0_24 NETWORK_OBJ_192.168.31.0_24 no-proxy-arp route-lookup
nat (PNet,outside) source static PNet-192.168.30.0 PNet-192.168.30.0 destination static NETWORK_OBJ_192.168.31.0_24 NETWORK_OBJ_192.168.31.0_24 no-proxy-arp route-lookup
!
object network obj_any
nat (any,outside) dynamic interface
object network FLNet-192.168.8.0
nat (FLNet,outside) dynamic interface
object network PNet-192.168.30.0
nat (PNet,outside) dynamic interface

route outside 0.0.0.0 0.0.0.0 123.123.123.185 1
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
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
user-identity default-domain LOCAL
aaa authentication ssh console LOCAL
http server enable
http 192.168.8.0 255.255.255.0 FLNet
no snmp-server location
no snmp-server contact
service sw-reset-button
crypto ipsec ikev1 transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec ikev1 transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec ikev1 transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec security-association pmtu-aging infinite
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set ikev1 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 ca trustpoint FLLocalTrust
enrollment self
fqdn FL.dyndns.org
subject-name CN=FL.dyndns.org
keypair FLsslvpnkeypair
crl configure
crypto ca trustpool policy
crypto ca certificate chain FLLocalTrust

crypto ikev1 enable outside
crypto ikev1 policy 10
authentication crack
encryption aes-256
hash sha
group 2
lifetime 86400
crypto ikev1 policy 20
authentication rsa-sig
encryption aes-256
hash sha
group 2
lifetime 86400
crypto ikev1 policy 30
authentication pre-share
encryption aes-256
hash sha
group 2
lifetime 86400
crypto ikev1 policy 40
authentication crack
encryption aes-192
hash sha
group 2
lifetime 86400
crypto ikev1 policy 50
authentication rsa-sig
encryption aes-192
hash sha
group 2
lifetime 86400
crypto ikev1 policy 60
authentication pre-share
encryption aes-192
hash sha
group 2
lifetime 86400
crypto ikev1 policy 70
authentication crack
encryption aes
hash sha
group 2
lifetime 86400
crypto ikev1 policy 80
authentication rsa-sig
encryption aes
hash sha
group 2
lifetime 86400
crypto ikev1 policy 90
authentication pre-share
encryption aes
hash sha
group 2
lifetime 86400
crypto ikev1 policy 100
authentication crack
encryption 3des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 110
authentication rsa-sig
encryption 3des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 120
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 130
authentication crack
encryption des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 140
authentication rsa-sig
encryption des
hash sha
group 2
lifetime 86400
crypto ikev1 policy 150
authentication pre-share
encryption des
hash sha
group 2
lifetime 86400
telnet timeout 5
no ssh stricthostkeycheck
ssh 0.0.0.0 0.0.0.0 outside
ssh 192.168.8.0 255.255.255.0 FLNet
ssh timeout 10
ssh key-exchange group dh-group1-sha1
console timeout 0
dhcpd dns 8.8.8.8 8.8.4.4
!

webvpn
enable outside
anyconnect image disk0:/anyconnect-win-4.2.01035-k9.pkg 1
anyconnect image disk0:/anyconnect-macosx-i386-4.2.01035-k9.pkg 2
anyconnect image disk0:/anyconnect-linux-64-4.2.01035-k9.pkg 3
anyconnect enable
tunnel-group-list enable
error-recovery disable
group-policy FLNetAnyConnectClientPolicy internal
group-policy FLNetAnyConnectClientPolicy attributes
dns-server value 192.168.8.8
vpn-tunnel-protocol ssl-client
split-tunnel-policy tunnelspecified
split-tunnel-network-list value ACL-FLNetAnyConnect-Split-Tunnel
default-domain value corp.FL.com.sg
address-pools value FLNetAnyConnectClientPool
group-policy VPH-GROUP internal
group-policy VPH-GROUP attributes
dns-server value 192.168.30.8
vpn-tunnel-protocol ikev1
split-tunnel-policy tunnelspecified
split-tunnel-network-list value VPH-GROUP_splitTunnelAcl
split-tunnel-all-dns disable
dynamic-access-policy-record DfltAccessPolicy

username VPH attributes
vpn-group-policy VPH-GROUP
username stn attributes
service-type remote-access

tunnel-group FLNetAnyConnectClientProfile type remote-access
tunnel-group FLNetAnyConnectClientProfile general-attributes
default-group-policy FLNetAnyConnectClientPolicy
tunnel-group FLNetAnyConnectClientProfile webvpn-attributes
group-alias FLNetAnyConnectClient enable
tunnel-group VPH-GROUP type remote-access
tunnel-group VPH-GROUP general-attributes
address-pool PNetVPNPool
default-group-policy VPH-GROUP
tunnel-group VPH-GROUP ipsec-attributes
ikev1 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
inspect icmp
inspect icmp error
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
hpm topN enable

5 Replies 5

Aditya Ganjoo
Cisco Employee
Cisco Employee

Hi,

Are you using names to resolve the PC or just pinging the IP's from the Anyconnect users ?

Regards,

Aditya

Hi,

    I use the IP address.

1) Anyconnect user can ping and access the server list under the dns-server (192.168.8.8), but not other device in that network (192.168.8.0). For example, I had a xerox printer at 192.168.8.20 and I'm not able to ping it or access the printer web interface via the IP address.

2) Same thing happen to the IPSec user... can ping and access the server list under the dns-server (192.168.30.8), but not other device in that network (192.168.30.0). For example, I had a phone system at 192.168.30.2 and I'm not able to ping it or access the phone system web interface via the IP address.

   Thanks and have a nice day.

Hi,

The config looks fine.

Can you check whether the pings from the Anyconnect client reach the ASA?

If they are then check the default gateway on the other hosts and see if it is pointing to the ASA's interface IP.

Regards,

Aditya

Hi,   

    After I reboot the ASA 5508, the AnyConnect user can now access any of the device on the 192.168.8.0 network, but still can't access the 192.168.30.0 device except 192.168.30.8.

   The IPSec (ikev1 - VPH-GROUP) user (192.168.31.0) still can't access the 192.168.30.0 device except 192.168.30.8. Below, I ping both 192.168.30.8 and 192.168.30.7 and capture the packet between 192.168.31.0 and 192.168.30.0:

1: 00:51:50.349286       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.8: icmp: echo request
   2: 00:51:50.349453       802.1Q vlan#30 P0 192.168.30.8 > 192.168.31.100: icmp: echo reply
   3: 00:51:51.356182       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.8: icmp: echo request
   4: 00:51:51.356320       802.1Q vlan#30 P0 192.168.30.8 > 192.168.31.100: icmp: echo reply
   5: 00:51:52.357067       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.8: icmp: echo request
   6: 00:51:52.357205       802.1Q vlan#30 P0 192.168.30.8 > 192.168.31.100: icmp: echo reply
   7: 00:51:53.359936       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.8: icmp: echo request
   8: 00:51:53.360058       802.1Q vlan#30 P0 192.168.30.8 > 192.168.31.100: icmp: echo reply
   9: 00:51:56.899047       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.7: icmp: echo request
  10: 00:52:01.276612       802.1Q vlan#30 P0 192.168.31.100.49603 > 192.168.30.8.53:  udp 43
  11: 00:52:01.276825       802.1Q vlan#30 P0 192.168.30.8.53 > 192.168.31.100.49603:  udp 92
  12: 00:52:01.681544       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.7: icmp: echo request
  13: 00:52:06.671733       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.7: icmp: echo request
  14: 00:52:11.681941       802.1Q vlan#30 P0 192.168.31.100 > 192.168.30.7: icmp: echo request

    By the way, 192.168.8.8 and 192.168.30.8 are actually the same server, but on different network port.

    Any help will be appreciate.

   Thanks and have a nice day.

Hi,

    Anyone had any idea what cause the IPSec VPN user cannot access the device on PNet (192.168.30.0).

    By the way, I notice that device on FLNet (192.168.8.0 security level 100) cannot access the device on PNet (192.168.30.0 security level 80), but can access other device in lower security level interface (not shown to reduce the config length). Device in PNet (192.168.30.0 security level 80) still can access device in other lower security level interface(not shown to reduce the config length).

     From what I understand, if there is no access list define for that interface, access from higher security level to lower security level is permit by default. Does the VPN split tunnel access list affect this default behavior??

   Any help will be appreciate.

  Thanks and have a nice day.