ASA 5520 DMZ Configuration Question

I have a general DMZ configuration question.

I have two networks:

DMZ - 192.168.155.0 /24
Inside - 172.22.0.0 /16

Here is what I have done:

static (Inside,DMZ) 172.22.0.0 172.22.0.0 netmask 255.255.0.0
global (Outside) 10 interface
global (DMZ) 10 interface
nat (Inside) 10 0.0.0.0 0.0.0.0
nat (DMZ) 10 0.0.0.0 0.0.0.0

So right now I have this:
- DMZ can access the internet
- 172.22.x.x network can access DMZ across all ports

How can I restrict access into the DMZ from the Inside so only port 25 is open from the Inside to the DMZ? or port 21 ex...
I have seen examples where the static command lists only the IP of the Inside host and not the entire range.  The problem is, I have a device
that would need to be accessed by all users in the 22 network over a specified port, not a single host.

Thanks in advance.

Nick


Paisley-ConsultingAsked:
Who is Participating?
 
lrmooreCommented:
>restrict access into the DMZ from the Inside so only port 25 is open from the Inside to the DMZ?
Access-lists ---

 access-list DMZ_Restricted permit tcp 172.22.0.0 255.255.0.0 192.168.155.0 255.255.255.0 eq smtp
 access-list DMZ_Restricted permit tcp 172.22.0.0 255.255.0.0 192.168.155.0 255.255.255.0 eq <port#>
 access-list DMZ_Restricted deny ip 172.22.0.0 255.255.0.0 192.168.155.0 255.255.255.0
 access-list DMZ_Restricted permit ip any any
 access-group DMZ_Restricted in interface inside

BTW, you don't need the static unless you want the systems in the DMZ to address the internal users directly by their private IP's. Given the rest of the information that you provided, I don't think that is your intention..
 
0
 
Paisley-ConsultingAuthor Commented:
Thanks that is exactly what I wanted and it worked great.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.