<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>jklogic.net &#187; ICMP</title>
	<atom:link href="http://jklogic.net/tag/icmp/feed/" rel="self" type="application/rss+xml" />
	<link>http://jklogic.net</link>
	<description>logical reality</description>
	<lastBuildDate>Tue, 07 Oct 2008 19:43:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Cisco ASA and ICMP Configurations</title>
		<link>http://jklogic.net/cisco-asa-and-icmp-configurations/</link>
		<comments>http://jklogic.net/cisco-asa-and-icmp-configurations/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 15:59:50 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[Cisco]]></category>
		<category><![CDATA[ASA]]></category>
		<category><![CDATA[ICMP]]></category>
		<category><![CDATA[Pix]]></category>

		<guid isPermaLink="false">http://jklogic.net/cisco-asa-and-icmp-configurations/</guid>
		<description><![CDATA[As I am sure many of you who have ever worked with a Cisco firewall know, ICMP is not allowed through the firewall by default.  If you are just configuring the device, this can make it very difficult to troubleshoot connectivity issues.  Thankfully, there are several ways to get around this.

Solution 1:  [...]]]></description>
			<content:encoded><![CDATA[<p>As I am sure many of you who have ever worked with a Cisco firewall know, ICMP is not allowed through the firewall by default.  If you are just configuring the device, this can make it very difficult to troubleshoot connectivity issues.  Thankfully, there are several ways to get around this.<br />
<br />
Solution 1:  Use access-lists to allow pings from inside/DMZ to the outside.<br />
To allow pinging from the inside to the outside interfaces, you will need to configure an access-list for the outside interface.</p>
<div class="code">access-list OUTSIDE_IN_ACL permit icmp any any echo-reply</div>
<p>Then apply the access-list to the outside interface.</p>
<div class="code">access-group OUTSIDE_IN_ACL in interface outside</div>
<p>This will allow only ping.  If you would like to allow trace route, you will also need to allow time-exceeded.</p>
<div class="code">access-list OUTSIDE_IN_ACL permit icmp any any time-exceeded</div>
<p>Solution 2: Use access-list to allow ping and trace route from the internet to your dmz/inside servers.<br />
To do this, we are going to build off of what we did above, so you should already have this in the config.</p>
<p><span id="more-19"></span></p>
<div class="code">access-list OUTSIDE_IN_ACL permit icmp any any echo-reply<br />
access-list OUTSIDE_IN_ACL permit icmp any any time-exceeded<br />
access-group OUTSIDE_IN_ACL in interface outside</div>
<p>Now all we need to do is allow echo into the network.</p>
<div class="code">access-list OUTSIDE_IN_ACL permit icmp any any echo</div>
<p>Even though we are allowing icmp, we still need to have a static mapping to allow the packets to reach the DMZ.</p>
<div class="code">static (dmz,outside) PUBLIC_IP DMZ_IP netmask 255.255.255.255</div>
<p>Of course, you will need to have a static mapping for every server you want to have reachable from the internet.<br />
<br />
Solution 3: This is a bit more complex, but will allow higher security level interfaces to ping/trace route lower security level interfaces without the use of access-lists.  To do this, we will tell the ASA to inspect icmp in a service policy.  If you are using a ASA, you should have a default policy in the base config called global_policy.</p>
<p>global_policy:</p>
<div class="code">class-map inspection_default<br />
match default-inspection-traffic<br />
!<br />
!<br />
policy-map type inspect dns migrated_dns_map_1<br />
parameters<br />
message-length maximum 512<br />
policy-map global_policy<br />
class inspection_default<br />
inspect dns migrated_dns_map_1<br />
inspect ftp<br />
inspect h323 h225<br />
inspect h323 ras<br />
inspect rsh<br />
inspect rtsp<br />
inspect esmtp<br />
inspect sqlnet<br />
inspect skinny<br />
inspect sunrpc<br />
inspect xdmcp<br />
inspect sip<br />
inspect netbios<br />
inspect tftp<br />
!<br />
service-policy global_policy global</div>
<p>To add icmp inspection.</p>
<div class="code">
FW-ASA(config)# policy-map global_policy<br />
FW-ASA(config-pmap)# class inspection_default<br />
FW-ASA(config-pmap-c)# inspect icmp</div>
]]></content:encoded>
			<wfw:commentRss>http://jklogic.net/cisco-asa-and-icmp-configurations/feed/</wfw:commentRss>
		<slash:comments>56</slash:comments>
		</item>
	</channel>
</rss>
