In a previous lesson I explained how to configure dynamic NAT from the inside to the outside. In this lesson we add a DMZ and some more NAT translations. Here’s the topology that we will use:
In this example we have our INSIDE, OUTSIDE and DMZ interfaces. The security levels of these interfaces are:
- INSIDE: 100
- OUTSIDE: 0
- DMZ: 50
We can go from a “high” security level to a “low” security level so this means that hosts from the INSIDE can reach the DMZ and OUTSIDE. Hosts from the DMZ will also be able to reach the OUTSIDE. We will configure NAT for the following traffic patterns:
- Traffic from hosts on the INSIDE to the OUTSIDE, we’ll use a “public” pool for this.
- Traffic from hosts on the INSIDE to the DMZ, we’ll use a “DMZ” pool for this.
- Traffic from hosts on the DMZ to the OUTSIDE, we’ll use the same public pool for this.
Here’s what a visualization of these NAT rules look like:
Let’s start by configuring the interfaces:
ASA1(config)# interface e0/0
ASA1(config-if)# nameif INSIDE
ASA1(config-if)# ip address 192.168.1.254 255.255.255.0
ASA1(config-if)# no shutdownASA1(config)# interface e0/1
ASA1(config-if)# nameif OUTSIDE
ASA1(config-if)# ip address 192.168.2.254 255.255.255.0
ASA1(config-if)# no shutdownASA1(config)# int e0/2
ASA1(config-if)# nameif DMZ
ASA1(config-if)# security-level 50
ASA1(config-if)# ip address 192.168.3.254 255.255.255.0
ASA1(config-if)# no shutdownThe INSIDE and OUTSIDE security levels have a default value, the DMZ I configured to 50 myself. Now let’s look at the dynamic NAT configuration…
Dynamic NAT with three Interfaces
First we will create the pools:
ASA1(config)# object network PUBLIC_POOL
ASA1(config-network-object)# range 192.168.2.100 192.168.2.200ASA1(config)# object network DMZ_POOL
ASA1(config-network-object)# range 192.168.3.100 192.168.3.200I will use a range of IP addresses from the subnet that is configured on the OUTSIDE and DMZ interface. Now we can create some network objects for the NAT translations:
Hi Rene
As far as I know, by default, ASA will block all traffics from lower into higher area.
In this example, I can’t ping from R1 to 192.168.2.2 and 192.168.3.3 but I can telnet to them.
Why is it?
If we dont create the access-list something like below:
I cant ping to them!
Thank you!
Hi Zaman,
Here’s how it works:
This basically does two things:
We use this so a server on the INS
... Continue reading in our forumby default FW allow from Inside to DMZ, so that means I am from Inside network and I can RDP to my windows server in DMZ. it can be bad in some cases,
and if I want to block RDP from Inside to DMZ I will need to configure and access list?
Thank you
Hello there,
I am kind of new in networking field.
I have configured ASA dynamic NAT with DMZ as per Unit 2.
for some reason I can’t telnet into R2 and R3, gives me error “connection refused by remote host”
if you can help me out please.
thanks
Thanx again Laz!
I will try this again tomorrow on Devnet rather than GNS3.
Kind Regards
Frank