I got issue regarding ASA 9.1 NAT. I have 3 networks on 3 dedicated interfaces. I want to give internet access via WAN interface only on port 80 and 443 for those 3 networks. I also want to access some services (443, DNS, GRE etc..) on specific machines (10.10.10.5, 10.10.11.3) on my A network and B network from the Internet via my wan IP. How can make rules based on these requirements?
interface GigabitEthernet0/0.571 WAN vlan 571 security-level 10 ip address XX.XX.XX.XX !
interface GigabitEthernet0/1 A NETWORK security-level 50 ip address 10.10.10.1 255.255.255.0 ! interface GigabitEthernet0/2 B NETWORK security-level 50 ip address 192.168.0.1 255.255.0.0 ! interface GigabitEthernet0/3 C NETWORK security-level 50 ip address 10.10.11.1 255.255.255.0 !
For the requirement of allowing the Outbound access for these Networks to the internet on these ports:- 80 and 443 , you can apply three interface NAT statements and allow only specific port 80 and 443 traffic through the ASA device using the access rule on the inside interface for the outbound traffic.
object network obj-10.10.10.0
subnet 10.10.10.0 255.255.255.0
nat (A NETWORK,WAN) dynamic interface
access-list Anetwrok-WAN permit tcp any any eq 443
access-list Anetwrok-WAN permit tcp any any eq 80 [NOTE:- You might also want to allow DNS thorugh as that would be required for the internet access]
access-group Anetwrok-WAN in interface A Network
Do the same for the other 2 Networks.
For the access from the WAN to the Internal Hosts , you can use Static PAT for this purpose.
Something like this:-
object network obj-10.10.10.5
nat (Anetwork,WAN) static interface service tcp 443 443
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...