I've used a similar config to this on a few other configs and everything worked great. My problem now is, the connection is made, and my machine is sending data, but, nothing is being recieved. I'm also noticing a lot of bypassed packets. Any have any idea why?
PIX Version 6.3(1)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxx
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
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
access-list test permit tcp any host 207.229.x.x eq smtp
access-list test permit tcp any host 207.229.x.x eq www
access-list test permit tcp any host 207.229.x.x eq 3306
access-list nonat permit ip 192.168.100.0 255.255.255.0 192.168.200.0 255.255.25
access-list 151 permit ip 192.168.100.0 255.255.255.0 192.168.200.0 255.255.255.
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 207.229.x.x 255.255.255.224
ip address inside 192.168.100.86 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPNPOOL 192.168.200.1-192.168.200.20
Also, make sure any routers on the Internal network know to route these IPs to the PIX.
If that is not the issue, what kind of device is your VPN client behind? If you do not configure a Linksys DSL/Cable FW/Router for IPSEC Passthrough, then the tunnel will be made, the packets will be sent to the PIX, but when the PIX sends the packets back, the Linksys will drop them.
Assuming that your PIX does not pick up any dynamic routes using RIP or OSPF then yes, that would suffice. I would consider adding that route statement anyway, just to hard code this on to the PIX. Kind of like puting a deny any any statement at the end of an ACL. It is there by default, but is good practice to put that line in anyway.
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...
Table of Contents 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 an...