I have a VPN set between a PIX and router. One has network 10.0.0.0 behind it and another has 192.168.1.0.
Everything is working ok with the encrypting and decrypting of packets (apart from the VPN only coming up from the PIX to the router, and not the other way around, although i am setting it to bidirectional).
The new requirement is to forward all the traffic for an IP address 193.x.x.x on the router through the VPN, into the PIX and then the PIX routes it correctly.
I added 193.x.x.x to the permit command to the access-list on the router's crypto map. The traffic still doesn't go through the VPN tunnel.
Then I added it to the NAT exempt access-list. The result was that the tunnel that was fine now continuously goes up and down. I tried to do the simmetric configuration on the PIX but to no avail.
I am sorry for the lack of configuration snippets but this is more a theoretical question. Why does the tunnel go up and down just by adding a new access-list entry to the NAT exempt list. Can anyone help me?
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...