I have a small remote site connected via site-to-site VPN with a PIX 501 to our main office ASA 5520. Traffic from the remote site to the main office subnet, dmz subnet, and a small directly connected subnet passes just fine, however the remote site cannot pass traffic to any of the other sites/subnets on our WAN.
I've added one of the WAN subnets to the ACL on the PIX for the crypto map, as well as the ASA's crypto map and NAT exemptions, but still can't pass traffic to the WAN subnet.
This is the pertinent PIX config at the remote site:
access-list 101 permit ip 172.16.68.0 255.255.252.0 172.16.128.0 255.255.252.0 (main office) access-list 101 permit ip 172.16.68.0 255.255.252.0 10.10.10.0 255.255.255.0 (dmz) access-list 101 permit ip 172.16.68.0 255.255.252.0 172.16.132.0 255.255.252.0 (directly connected site to main office - wifi bridge) access-list 101 permit ip 172.16.68.0 255.255.252.0 172.16.104.0 255.255.252.0 (the WAN subnet I'm trying to access)
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...