bwilliam13
IS-IT--Management
I have Cisco VPN clients connecting into a PIX with 6 interfaces (3 of the interfaces active), authenticating by RADIUS. Everything works regarding the VPN clients connecting to the inside interface of the PIX. However...
No VPN clients can access anything in the DMZ interface, which is where the mail, web, and ftp servers are. I have access-lists that specify to let anyone on the inside interface--or appropriate subnet--access any server in the DMZ...and every PC sitting physically on the inside interface can access them fine. However, VPN clients who get an IP address from a pool that is on a subnet in the inside range cannot access the DMZ on the same ports.
This is a problem...and one that I don't know how to get around.
Here's my applicable configuration - no modifications, posted as-is, commented so you can understand it:
#Let any hosts on inside (10.1.0.0/16) access any hosts in #the DMZ (10.0.2.0/24)
access-list acl_dmz1 permit icmp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit tcp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit udp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit ah 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit esp 10.1.0.0 255.255.0.0 any
#Let any VPN clients access any hosts on inside #(10.1.0.0/16) as well as DMZ (10.0.2.0/24)
access-list 101 permit ip 10.1.0.0 255.255.255.0 10.1.0.0 255.255.0.0
access-list 101 permit icmp 10.1.0.0 255.255.255.0 10.1.0.0 255.255.0.0
access-list 101 permit ip 10.1.0.0 255.255.0.0 10.1.0.0 255.255.255.0
access-list 101 permit icmp 10.1.0.0 255.255.0.0 10.1.0.0 255.255.255.0
access-list 101 permit ip 10.1.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 101 permit icmp 10.1.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 101 permit ip 10.0.2.0 255.255.255.0 10.1.0.0 255.255.255.0
access-list 101 permit icmp 10.0.2.0 255.255.255.0 10.1.0.0 255.255.255.0
#Specify IP addresses for VPN clients
ip local pool ippool 10.1.0.10-10.1.0.20
#Don't NAT VPN client traffic
nat (inside) 0 access-list 101
#Specify crypto/isakmp stuff for VPN clients
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client configuration address initiate
crypto map mymap client authentication AuthInbound
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup vpn3000 address-pool ippool
vpngroup vpn3000 dns-server 10.1.1.2 10.1.2.3
vpngroup vpn3000 wins-server 10.1.1.2 10.1.2.3
vpngroup vpn3000 default-domain whatever.com
vpngroup vpn3000 split-tunnel 101
vpngroup vpn3000 split-dns whatever.com
vpngroup vpn3000 idle-time 1800
vpngroup vpn3000 max-time 86400
Everything else works perfectly...except VPN clients getting to the DMZ. I'm at a complete loss at this point...been trying to figure this out off and on for the past 2 weeks. Any help is appreciated.
No VPN clients can access anything in the DMZ interface, which is where the mail, web, and ftp servers are. I have access-lists that specify to let anyone on the inside interface--or appropriate subnet--access any server in the DMZ...and every PC sitting physically on the inside interface can access them fine. However, VPN clients who get an IP address from a pool that is on a subnet in the inside range cannot access the DMZ on the same ports.
This is a problem...and one that I don't know how to get around.
Here's my applicable configuration - no modifications, posted as-is, commented so you can understand it:
#Let any hosts on inside (10.1.0.0/16) access any hosts in #the DMZ (10.0.2.0/24)
access-list acl_dmz1 permit icmp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit tcp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit udp 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit ah 10.1.0.0 255.255.0.0 any
access-list acl_dmz1 permit esp 10.1.0.0 255.255.0.0 any
#Let any VPN clients access any hosts on inside #(10.1.0.0/16) as well as DMZ (10.0.2.0/24)
access-list 101 permit ip 10.1.0.0 255.255.255.0 10.1.0.0 255.255.0.0
access-list 101 permit icmp 10.1.0.0 255.255.255.0 10.1.0.0 255.255.0.0
access-list 101 permit ip 10.1.0.0 255.255.0.0 10.1.0.0 255.255.255.0
access-list 101 permit icmp 10.1.0.0 255.255.0.0 10.1.0.0 255.255.255.0
access-list 101 permit ip 10.1.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 101 permit icmp 10.1.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 101 permit ip 10.0.2.0 255.255.255.0 10.1.0.0 255.255.255.0
access-list 101 permit icmp 10.0.2.0 255.255.255.0 10.1.0.0 255.255.255.0
#Specify IP addresses for VPN clients
ip local pool ippool 10.1.0.10-10.1.0.20
#Don't NAT VPN client traffic
nat (inside) 0 access-list 101
#Specify crypto/isakmp stuff for VPN clients
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client configuration address initiate
crypto map mymap client authentication AuthInbound
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup vpn3000 address-pool ippool
vpngroup vpn3000 dns-server 10.1.1.2 10.1.2.3
vpngroup vpn3000 wins-server 10.1.1.2 10.1.2.3
vpngroup vpn3000 default-domain whatever.com
vpngroup vpn3000 split-tunnel 101
vpngroup vpn3000 split-dns whatever.com
vpngroup vpn3000 idle-time 1800
vpngroup vpn3000 max-time 86400
Everything else works perfectly...except VPN clients getting to the DMZ. I'm at a complete loss at this point...been trying to figure this out off and on for the past 2 weeks. Any help is appreciated.