Help with 501 pix vpn

[justinnickrand]

I am setting up a cisco pix 501 vpn tunnel but am having issues. The firewall works good as I am able to get out to the internet but the VPN isn't working. On the primary side I see the tunnel is up and traffic is being sent but not recieved.

Currently I am sitting at the secondary location but not sure what the issue maybe. Anyone know what I have wrong that would be preventing the data to send from this device?

Here is my config

Here is my config if that would help

show run
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 2KFQnbNIdI.2KYOU encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname ciscofirewall
domain-name hillsanddales.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 rsh 514
fixup protocol rtsp 5
fixup protocol rtsp 55
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.80.0 255.255.255.0 192.168.50.0 255.255.255.0
access-list nonat permit ip 192.168.80.0 255.255.255.0 192.168.50.0 255.255.255.0
access-list in_outside permit tcp any host 192.168.50.240
access-list in_outside permit tcp any host 64.90.xxx.xx
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 66.84.xxx.xx 255.255.255.252
ip address inside 192.168.80.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.50.0 255.255.255.0 outside
pdm location 192.168.80.2 255.255.255.255 inside
pdm location 192.168.50.0 255.255.255.0 inside
pdm location 182.168.80.0 255.255.255.255 inside
pdm location 0.0.0.0 255.255.255.0 inside
pdm location 0.0.0.0 255.255.255.255 inside
pdm location 192.168.80.5 255.255.255.255 inside
pdm location 192.168.80.7 255.255.255.255 inside
pdm logging informational 100
pdm history enable

arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 66.84.xxx.x
route inside 192.168.50.0 255.255.255.0 192.168.50.240 1
timeout xlate 0:05: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
http server enable
http 192.168.80.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
<--- More --->

sysopt connection permit-ipsec
crypto ipsec transform-set aptset esp-3des esp-md5-hmac
crypto map aptmap 10 ipsec-isakmp
crypto map aptmap 10 match address 101
crypto map aptmap 10 set peer 64.90.xxx.xx
crypto map aptmap 10 set transform-set aptset
crypto map aptmap interface outside
isakmp enable outside
isakmp key ******** address 64.90.xxx.xx netmask 255.255.255.255
isakmp identity address
isakmp nat-traversal 20
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
telnet 192.168.80.2 255.255.255.255 inside
telnet 182.168.80.0 255.255.255.255 inside
telnet 192.168.80.5 255.255.255.255 inside
telnet 192.168.80.0 255.255.255.0 inside
telnet 192.168.80.7 255.255.255.255 inside
telnet timeout 5
ssh timeout 5
management-access inside

console timeout 0
dhcpd address 192.168.80.2-192.168.80.33 inside
dhcpd dns 64.90.xxx.xx 64.90.xxx.xx
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:01532689fac9491fae8f86e91e2bd4c0
: end

[Jouni Forss · Accepted solution]

Hi,

Atleast the NAT0 ACL is not in use

You should have this added to the configuration

nat (inside) 0 access-list nonat

- Jouni

[Jouni Forss]

Also,

What is this route supposed to be?

route inside 192.168.50.0 255.255.255.0 192.168.50.240 1

According to the rest of the configuration the network 192.168.50.0/24 is supposed to be the remote network. And you dont have the gateway address 192.168.50.240 in your network.

You should probably remove the route.

- Jouni

[Matt Lang]

Nice catch!

[Matt Lang]

Justin,

It doesn't appear that you have configured the following on your PIX.

nat (inside) 0 access-list nonat

Matt

[justinnickrand]

When i type in nat (inside) 0 access-list nonat it tells me:

Type help or '?' for a list of available commands.  I am in config mode.

[Matt Lang]

You may not be able to use named access-lists.  Try the following:

access-list 120 permit ip 192.168.80.0 255.255.255.0 192.168.50.0 255.255.255.0

nat (inside) 0 access-list 120

Matt

[justinnickrand]

Matt I entered the command it is now working!!!  I also took out the route that JouniForss questioned.  I want to sincerly thank you guys for this help.  You guys are the type of people that enjoy helping others and make this world better.

Thank you, Justin

[Jouni Forss]

Hi,

Glad its working now.

Remember to rate helpfull answers and mark the questions that answered your question.

Actually Matt gave the correct answer. Please also mark/rate his answer. I dont remember that the ACL should be numerically named instead of alphabetically. Guess its been too long since I configured PIX the last time.

But to be honest I just remember that I had configure always with named ACL.

Command reference doesnt seem to make any mention of what the ACL should be.

- Jouni

[Jouni Forss]

Well this is strange.

I found this on the Command Reference for 6.3 software

 The following example shows use of the nat 0 access-list command  (NAT exemption) to permit internal host 10.1.1.15, which is accessible  through the inside interface, to bypass NAT when connecting to outside  host 10.2.1.3. 
access-list no-nat permit ip host 10.1.1.15 host 10.2.1.3



nat (inside) 0 access-list no-nat

Here the NAT0 uses alphabetically named ACL. Dont know what the problem was with your configurations.

- Jouni

[Matt Lang]

I thought the same thing, Jouni.  It's been a L-O-N-G time since I've seen that version of code though.

[Jouni Forss]

Hi,

You original post says you have this ACL configured on the PIX

access-list nonat permit ip 192.168.80.0 255.255.255.0 192.168.50.0 255.255.255.0

You should be able to use it in the mentioned NAT configuration line

nat (inside) 0 access-list nonat

Here is the link the Command Reference for this command

http://www.cisco.com/en/US/docs/security/pix/pix63/command/reference/mr.html#wp1032129

- Jouni