ASA 5510 - Setting up ACL to permit access only to the Nat'ed subnet
I experiencing an issue in setting up an ACL on my ASA 5510 to permit access only to the Nat subnet from inside to the outside interface. This firewall is setup for the DR solution in the production network. I am applying following acl in the inbound direction on the inside interface.
permit ip any "Nat_subnet"
After appliying this acl to inside interface I observed that I can ping to the destinations in NAT'ed subnet but unable to ssh to the servers. Following is the summary of my configuration. I would appreciate if someone please advice to resolve this issue.
ip address 192.168.135.241 255.255.255.248 standby 192.168.135.242
ip address 192.168.135.249 255.255.255.248 standby 192.168.135.250
ASA 5510 - Setting up ACL to permit access only to the Nat'ed su
Thanks for the reply. The basic idea behind NATing is to hide the 10.210.x.x subnet connected to the outside interface of the firewall from the inside. In the current scenario we have 10.210.x.x subnets in the production and same subnets in DR environment. We are using ACL to make sure that firewall can only pass taffic destined for 192.168.x.x subnets.
As I have mentioned that ping to the servers are working fine so I asume that translation is working fine. At this moment the only services I can test is SSH which is not working for some reason.
If I add acl permit ip any any it works fine.any ideas?
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...