I took it that the more specific static entry (for the public address) would override the static mapping that already exists for the whole LAN.
Is this the case? When connecting from the outside inbound the xlate entry is created because the destination address is the public IP. However connnections initiated from the inside are translated to the 10. address rather than the public IP.
This is not a problem as the setup is designed for external connections in. However I am curious about this behaviour - is the order of the static statements in the config important?
This has been bugging me an a couple of colleagues for a while - would be v grateful for any ideas?!
If someone from outside initiates connection to 22.214.171.124 host, it will be translated to 126.96.36.199 and reply will go accordingly. If someone initiates connections to 188.8.131.52, the reply will follow first static because it comes first in order.
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...