cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5388
Views
0
Helpful
9
Replies

Allow ICMP to DMZ

Stephen Sisson
Level 1
Level 1

Hello,

Need some help to allow ICMP from the internet into our internal DMZ.

We have a ASA 5505 with IOS 8.4 with three networks configured. Inside interface 192.168.1.x, outside interface 98.101.206.x, DMZ interface 172.16.5.x we need anyone from the outside or internet to have the ability to ping the DMZ and the servers we have.

We need to know is this possible, if so can you show how to setup the ACL's to allow this.

Thank you

1 Accepted Solution

Accepted Solutions

Hi,

A bit busy at work at the moment so didnt have time to look this one through right away.

So i guess this would be the complete NAT configuration of the server you mention

object network obj-172.16.5.2

host 172.16.5.2

nat (PCSFTP,outside) static 98.101.206.51

Therefore you should be able to allow ICMP to this host by issuing the following command

access-list outside_access_in permit icmp any object obj-172.16.5.2 echo

If you use only ASDM for example you can insert the CLI format command from the ASDM through the following path

Tools -> Command Line Interface ->

Then insert the above command to the Command line in the window that opened and "Send" it to the device.

- Jouni

View solution in original post

9 Replies 9

Jouni Forss
VIP Alumni
VIP Alumni

Hi,

If you are planning on PING/ICMP hosts from Internet to DMZ, then every host you want to PING/ICMP on the DMZ needs a public IP address.

Does every host have a public IP address currently? Of will they be natted to their own public IP on the ASA?

- Jouni

The DMZ is an internal DMZ on the 172.16.5.x network we have NAT translation setup for anyone trying to access our FTP servers.

Hi,

Does every host needed to ping have a Static NAT configured on the ASA?

If yes then you just need to allow ICMP/echo on the "outside" interface ACL

In the examples will use the ACL name "OUTSIDE-IN"

THis would be configured on the ASA in the direction "in" for the interface "outside"

access-group OUTSIDE-IN in interface outside

for example

From "any" source address

access-list OUTSIDE-IN permit icmp any host echo

or

From "any" source address using the object name of the NAT (if one exists)

access-list OUTSIDE-IN permit icmp any object echo

From specific source address/network

access-list OUTSIDE-IN permit icmp host host echo

or

access-list OUTSIDE-IN permit icmp host echo

- Jouni

Jouni,

We have only one server and yes the object NAT rule has the 98.101.206.x pointing to the host or server 172.16.5.x

I think the answer is yes - we had a contractor setup the ASA and not sure about the configuration.

Thanks

Hi,

If you can copy the needed NAT configurations here we can check it and the needed ACLs statements for ICMP.

- Jouni

I will try to summit everything you need from the running-config

object network obj_any

subnet 0.0.0.0 0.0.0.0

object network obj-172.16.5.2

host 172.16.5.2

object service FTPS

service tcp source eq 990 destination eq 989

description FTPS_DMZ_FTP_Server_11-29-12

access-list outside_access_in extended permit object FTPS any object obj-172.16.5.2

access-list outside_access_in extended permit tcp any object obj-172.16.5.2 eq ssh

access-list outside_access_in extended permit tcp any object obj-172.16.5.2 eq https

access-list outside_access_in extended permit tcp any host 172.16.5.2 eq ftp

pager lines 24

icmp unreachable rate-limit 1 burst-size 1

icmp permit host 172.16.5.2 outside

icmp permit any PCSFTP

nat (inside,outside) source dynamic any interface description PAT_Inside_Outside_on_MPLS_Circuit

!

object network obj_any

nat (PCSFTP,outside) dynamic interface

object network obj-172.16.5.2

nat (PCSFTP,outside) static 98.101.206.51

access-group outside_access_in in interface outside

route outside 0.0.0.0 0.0.0.0 98.101.206.1 1

I hope this is all you need, if not please let me know

Thank you

Hi,

A bit busy at work at the moment so didnt have time to look this one through right away.

So i guess this would be the complete NAT configuration of the server you mention

object network obj-172.16.5.2

host 172.16.5.2

nat (PCSFTP,outside) static 98.101.206.51

Therefore you should be able to allow ICMP to this host by issuing the following command

access-list outside_access_in permit icmp any object obj-172.16.5.2 echo

If you use only ASDM for example you can insert the CLI format command from the ASDM through the following path

Tools -> Command Line Interface ->

Then insert the above command to the Command line in the window that opened and "Send" it to the device.

- Jouni

I’m sure you are very busy, when people have experience like you they are in high demand.

We really appreciate Cisco – you for having time to help us configure our equipment, show the mistakes as we learn.

Thank you my friend – Merry Christmas.

Were you able to get it working with the above command or is there any problems?

If it doesnt work yet you might need to add the following "inspect icmp" to your configuration

Provided the configuration is pretty default on your firewall you could add this configuration. The 2 first lines are just for the firewall to move to the right configuration prompt and "inspect icmp" is the actual command/setting that will be inserted

policy-map global_policy

class inspection_default

  inspect icmp

If on the other hand you solved the problem already please rate and mark the question as answered.

EDIT: Ah you did already

EDIT2: Merry Christmas to you too. I will be doing firewall migrations around christmas, ho ho ho

- Jouni

Review Cisco Networking for a $25 gift card