I have a PIX515E v6.22 that is configured for two site to site VPNs(Crypto map 10 and 20 and Isakmp policy 10). I'm trying to add a configuration for a VPN client connection. With the following configuration, the VPN client 3.6 will establish the connection, but I can't ping the outside interface or anything in the 10.0.0.0 subnet or the 192.168.254.0 subnet. The pix adds the access lists when a connection is made, but they do not show any hits when I attempt to make connections. Does anyone see what I'm doing wrong?
PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password lui78Uo/LBYLTriJ encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
access-list 100 permit ip 10.0.0.0 255.255.255.0 k.l.m.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 host n.o.p.129
access-list 100 permit ip 10.0.0.0 255.255.255.0 192.168.200.0 255.255.255.0
access-list 100 permit ip 192.168.254.0 255.255.255.0 192.168.200.0 255.255.255.0
access-list 101 permit ip 10.0.0.0 255.255.255.0 k.l.m.0 255.255.255.0
access-list 102 permit ip 10.0.0.0 255.255.255.0 host n.o.p.129
pager lines 24
logging console debugging
logging monitor debugging
interface ethernet0 auto
interface ethernet1 auto
mtu outside 1500
mtu inside 1500
ip address outside h.i.j.5 255.255.255.0
ip address inside 192.168.254.198 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool bigpool 192.168.200.1-192.168.200.254
Re: VPN Client to PIX515E with two site to site VPN
Your tunnel is being built properly. Don't worry about the ISAKMP debug, the PIX has a bug where it only shows the first 10 or 15 (or some number) policy attempts, so it will be getting to your policy 20 it's just the debug isn't showing it. This is verified by the fact that your tunnel is being built, as shown in teh IPSec debug.
Anyway, can't see anything wrong with your config. Sounds sort of like the ESP packets are getting blocked somewhere. Keep in mind that the tunnel is built on ISAKMP (UDP 500) packets, then all the data is sent with ESP packets.
When you ping, does the Encrypted Packets counter go up on the client? Does the Pkts Decaps counter go up on the PIX in a "sho cry ipsec sa" output? Does the Pkts Encaps go up (indicating the PIX has received the response from the inside client and has sent it on to your VPN client)? Does the Decrypted Packets counter go up on teh VPn client? check all of these counters and it should give you a good indication of where the problem lies.
Are you going thru a PAT device between the PIX and client? If so, upgrade the PIX to 6.3 and add the command:
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
[toc:faq]Introduction:This document describes details on how NAT-T
works.Background:ESP encrypts all critical information, encapsulating
the entire inner TCP/UDP datagram within an ESP header. ESP is an IP
protocol in the same sense that TCP and UDP are I...