ASA 5520 inside interface used for Clients Default Gateway
I'm having issues when I point my clients DHCP lease gatway to the inside addr of the ASA ( they can not connect to any internal network the ASA has routes too. I validated from the ASA inside addr can see these networks "ping" and he recieves replies... So, I'm thinking the ASA is trying to nat the internal source ADDR when the source conects to him " internal side of the Asa" for the route next hop.
Re: ASA 5520 inside interface used for Clients Default Gateway
The commadn will effect only the traffic between networks specified in access list. For example, your inside network is 192.168.1.0/24, and you have an internal network routed via ASA 172.16.10.0/24. If you type the following,
access-list inside_nat0_outbound permit ip 192.168.1.0 255.255.255.0 172.16.10.0 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound
Traffic between these networks wont be NATed bidirectionally, so hosts on these network will be able to connect each other on their actual IPs. But traffic from 192.168.1.0 to any other destination, for example a host in internet 18.104.22.168, this traffic will be natted and connection will be successful.
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...