pptp shutdown after config IPSEC site to site

impelse

This is very extrange:

I configured simple pptp for many users outside of the company, I did a ACL to permit any to any, it was working fine.

Yesterday I confiugred a VPN site to site with IPSec, It is working perfect, but my pptp user can logon to the pix 501 but they can not ping my inside network (they can not do anything)

I just add one line to the control list to permit to the network with IPSec any.

Irvington# sh run
: Saved
:
PIX Version 6.3(5)
interface ethernet0 10baset
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password QqC9gTrF2tZtGV9G encrypted
passwd QqC9gTrF2tZtGV9G encrypted
hostname Irvington
domain-name rilcomain.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 101 permit ip 192.168.2.0 255.255.255.0 172.16.1.0 255.255.255.0
access-list 101 permit ip 172.16.1.0 255.255.255.0 192.168.2.0 255.255.255.0
access-list 101 permit ip 192.168.2.0 255.255.255.0 192.168.1.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside x.x.x.x 255.255.255.248
ip address inside 192.168.2.254 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool pptp-pool 172.16.1.1-172.16.1.10
pdm history enable
arp timeout 14400
global (outside) 1 76.247.253.34
nat (inside) 0 access-list 101
nat (inside) 1 192.168.2.0 255.255.255.0 0 0
route outside 0.0.0.0 0.0.0.0 x.x.x.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa authentication ssh console LOCAL
http server enable
http 192.168.2.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
crypto ipsec transform-set strong esp-3des esp-md5-hmac
crypto ipsec security-association lifetime seconds 900
crypto map irvington 10 ipsec-isakmp
crypto map irvington 10 match address 101
crypto map irvington 10 set peer x.x.x.x
crypto map irvington 10 set transform-set strong
crypto map irvington interface outside
isakmp enable outside
isakmp key ******** address x.x.x.x netmask 255.255.255.255
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
console timeout 0
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe auto
vpdn group 1 client configuration address local pptp-pool
vpdn group 1 pptp echo 60
vpdn group 1 client authentication local
vpdn username peter password *********
vpdn username rony password *********
vpdn enable outside
username rony password EXnj6HDOPr2nh9Jk encrypted privilege 2
terminal width 80
Cryptochecksum:6b08e7e6fd74eacb2f23b97266356b86
: end
Irvington#

Ahriakin

Your PTPP IP Pool does not match any interface IP on the pix?

mikej412

impelse wrote:

access-list 101 permit ip 192.168.2.0 255.255.255.0 172.16.1.0 255.255.255.0

You want your inside traffic going to the network that includes your pool addresses to go through the IPSec tunnel?

impelse

Ok.

Before doing th IPSec site to site I was working fine with PPTP, I was able to do everything. After I configured the IPSec the site to site beging to work fine between the two LANs but it shut me down the PPTP (the users in PPTP can login to the server, adquire the ip address, etc but they can not go to the inside network).

I discovered that when I set the command "crypto map irvington interface outside" activate the IPSec in the outside interface, in this moment the PPTP shutdown.

I need tp mix both systems.

I read that I can do it using PDM software but when I login with the web browser it said that because there are a access-list 101 that use NAT 0 I can not have config capabilities.

Raul

mikej412

Use 1 access list to avoid natting your pptp and IPSec traffic, and another access list to define the "interesting traffic" for IPSec. The ACLs for each side of the IPSec tunnel should be the "inverse" of each other.

impelse

I have this access list :

access-list 101 line 1 permit ip 192.168.1.0 255.255.255.0 172.16.1.0 255.255.255.0
access-list 101 line 2 permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0

nat (inside) 0 access-list 101

With this I am avoiding nat

The config says that I have to type:

crypto map remote-site interface outside.

How can I write the access-list for IPSec

Raul

Ahriakin

Mike's right about the access-lists, besides needing them separate for proper functionality (and not IPSEC encrypting your PPTP intended pool) the PDM will not allow you to use one access-list for 2 functions (NAT 0 and defining your IPSEC traffic), that's the source of your error when trying to use the GUI. Make a min. of 2 separate lists or If you want to simplify using similar subnets for both the way to do it is put them into object groups, then create 2 access-lists that reference those groups (not a biggy with just a couple of subnets but with lots it saves time and gives you the same result).

Your NAT 0 list can contain all of the PPTP/IPSEC Subnets/Pools combined.
Your IPSEC defining access list should permit Ip from your site-site local subnet(s) -> remote site subnet(s) only. And again as Mike said just reverse that on the other end. Set the route for those remote subnets to your outside default gateway.