<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ASA NAT/Traceroute Inside to Outside Issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215584#M349507</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I beleive ICMP Inspecition is enabled, for both ICMP and ICMP error, I see this in the ASDM and on CLI, see below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map type inspect dns preset_dns_map&lt;/P&gt;&lt;P&gt; parameters&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum client auto&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225 &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rtsp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect esmtp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect skinny&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect xdmcp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect netbios &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect tftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ip-options &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp error &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not run the "fixup protocol icmp" - I am not sure what this is?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EIDT: After a quick look into this fixup protocol I see it's the same as enabling the inspect icmp &amp;amp; icmp error as shown above, well from what I understand, please correct me if I am wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 May 2013 23:57:46 GMT</pubDate>
    <dc:creator>hiltonstroud</dc:creator>
    <dc:date>2013-05-22T23:57:46Z</dc:date>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215582#M349505</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Product in question: ASA5512-x in HA Active/Standby Failover mode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When running a ping from the inside network to a device on the internet I recieve replies and all is good.&amp;nbsp; However when running a traceroute from inside the network to a device on the internet I receive timeouts which look to be caused by a ACL deny rule, that being "outside/internet_access_in"&amp;nbsp; If I quickly add an access rule for "outside/internet" incoming rule and allow any any with ICMP_Group then I get replies and the ACL is allowing it, however the replies for the traceroute are always the same, which is the device IP your tracing.&amp;nbsp; I wouldn't think you would want an outside/internet incoming rule for this kind of service as it would open you up and kinda defeat the purpose of firewal etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To me it sounds like NAT is certainly causing some weirdness here, possilby they way it's setup... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following is the explanation from the Deny message on syslog.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;A name="wp4769023" target="_blank"&gt;&lt;/A&gt;%ASA-4-106023: Deny protocol src 
[&lt;EM&gt;interface_name&lt;/EM&gt;:&lt;EM&gt;source_address&lt;/EM&gt;/&lt;EM&gt;source_port&lt;/EM&gt;] [([&lt;EM&gt;idfw_user&lt;/EM&gt;|&lt;EM&gt;FQDN_string&lt;/EM&gt;], &lt;EM&gt;sg_info&lt;/EM&gt;)] 
dst &lt;EM&gt;interface_name&lt;/EM&gt;:&lt;EM&gt;dest_address&lt;/EM&gt;/&lt;EM&gt;dest_port&lt;/EM&gt; [([&lt;EM&gt;idfw_user&lt;/EM&gt;|&lt;EM&gt;FQDN_string&lt;/EM&gt;], &lt;EM&gt;sg_info&lt;/EM&gt;)] 
[type {&lt;EM&gt;string&lt;/EM&gt;}, code {&lt;EM&gt;code&lt;/EM&gt;}] by &lt;EM&gt;access_group acl_ID&lt;/EM&gt; [0x8ed66b60, 0xf8852875]&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; A real IP packet was denied by the ACL. This message appears even if you&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; do not have the &lt;STRONG&gt;log&lt;/STRONG&gt; option enabled for an ACL. The&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IP address is the real IP address instead of the values that display&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; through NAT. Both user identity information and FQDN information is&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; provided for the IP addresses if a matched one is found. The ASA logs&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; either identity information (domain\user) or FQDN (if the username is&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; not available). If the identity information or FQDN is available, the&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ASA logs this information for both the source and destination.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following are the 2 NAT rules in place at the moment - The first one was auto created when configuration a site-to-site VPN which is meant to tell the traffice over the VPN not to NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside,internet) source static Private_Network_Classes Private_Network_Classes destination static Test_VPN_Site Test_VPN_Site no-proxy-arp route-lookup&lt;/P&gt;&lt;P&gt;nat (inside,internet) source dynamic any interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this gives some insight into the issue I am having and someone can suggest some fixes/reconfig's to work around this.&amp;nbsp; It certainly hasn't been easy trying to explain what is occuring here in writting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your time.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:47:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215582#M349505</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2019-03-12T01:47:05Z</dc:date>
    </item>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215583#M349506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you enabled ICMP Inspection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;fixup protocol icmp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;fixup protocol icmp error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or you add them under the "policy-map" configurations along with the other "inspect"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;inspect icmp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;inspect icmp error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I remember reading on these forums that this might be some bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2013 09:06:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215583#M349506</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-22T09:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215584#M349507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I beleive ICMP Inspecition is enabled, for both ICMP and ICMP error, I see this in the ASDM and on CLI, see below&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;class-map inspection_default&lt;/P&gt;&lt;P&gt; match default-inspection-traffic&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;policy-map type inspect dns preset_dns_map&lt;/P&gt;&lt;P&gt; parameters&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum client auto&lt;/P&gt;&lt;P&gt;&amp;nbsp; message-length maximum 512&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;/P&gt;&lt;P&gt; class inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect dns preset_dns_map &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 h225 &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect h323 ras &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rsh &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect rtsp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect esmtp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sqlnet &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect skinny&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sunrpc &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect xdmcp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect sip&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect netbios &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect tftp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect ip-options &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp &lt;/P&gt;&lt;P&gt;&amp;nbsp; inspect icmp error &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not run the "fixup protocol icmp" - I am not sure what this is?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EIDT: After a quick look into this fixup protocol I see it's the same as enabling the inspect icmp &amp;amp; icmp error as shown above, well from what I understand, please correct me if I am wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2013 23:57:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215584#M349507</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-22T23:57:46Z</dc:date>
    </item>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215585#M349508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To my understanding there shouldnt be many things preventing traceroute through the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Usually its related to the Inspections and/or lacking the ACL statements on the "outside" interface which allow echo-reply, time-exceeded and unreachable messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you post some exact Syslog messages when a ICMP message is blocked? (Can naturally mask the public IP addresses) To my understanding the ASA is at the moment blocking the messages that the routers in between the destination and the source are sending to the source host behind the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One other usual problem regarding ASA and traceroute is also the fact that the ASA doesnt show up on the traceroute. IF that is required you will also need some additional configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is also the possibility that you are running into some software bug. To try to determine that we would need to know your current software level.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And regarding the "fixup" commands. These are the predecessor of "inspect" on old Cisco PIX firewalls. The ASAs still seem to support these old commands but ASA will convert the commands to "inspect" configurations. Sometimes its just faster and easier to use the "fixup" command to insert the configuration than going under the "policy-map" configurations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 07:14:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215585#M349508</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-23T07:14:17Z</dc:date>
    </item>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215586#M349509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have to agree with Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we see this issues the command that fix it is the "fixup protocol icmp error" but it seems that it's doing nothing here,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I would say captures on the inside and outside plus logs would allow a better troubleshooting here,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share the show service-policy ( did you perform a clear local-host after entering the fixup protocol icmp and icmp error?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 May 2013 16:36:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215586#M349509</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-05-23T16:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215587#M349510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would agree with your comments as well after obtaining better understanding of the issue myself with your support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per request below is exact syslog message from traceroute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:19:01|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:19:01|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:19:01|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:59|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:55|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:51|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:47|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:45|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:43|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:41|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:39|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:37|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:35|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:33|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:31|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:29|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:27|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:25|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:23|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:21|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:19|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:17|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:15|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:13|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:11|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:09|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:07|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:05|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:18:03|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:18:01|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:59|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:57|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:55|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:53|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:51|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:49|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:47|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:45|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:43|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:41|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:39|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:37|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:35|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:33|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:31|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:29|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:27|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:25|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:23|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:21|106023|x.x.x.x.144||172.18.20.12||Deny icmp src internet:x.x.x.x.144 dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:19|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:17|106023|x.x.x.x.144||172.18.20.12||Deny icmp src internet:x.x.x.x.144 dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:15|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:13|106023|x.x.x.x.144||172.18.20.12||Deny icmp src internet:x.x.x.x.144 dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:11|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:09|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:07|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:05|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:17:03|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:17:01|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:59|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:57|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:55|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:53|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:51|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:49|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:47|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:45|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:43|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:41|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:39|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:37|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:35|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:33|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:31|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:29|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:27|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:25|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:23|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:21|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:19|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:17|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:15|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:13|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:11|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:09|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:07|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:05|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:16:03|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:16:01|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:59|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:57|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:55|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:53|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:51|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:49|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:47|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:45|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:43|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:41|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:39|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:37|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:35|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:33|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:31|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:29|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:15:27|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:15:25|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|10:00:02|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|10:00:00|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|09:59:57|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|09:59:55|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|09:59:53|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|09:59:51|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;6|May 27 2013|09:59:50|302021|x.x.x.x|0|172.18.20.12|1|Teardown ICMP connection for faddr x.x.x.x/0 gaddr x.x.x.x/1 laddr 172.18.20.12/1&lt;/P&gt;&lt;P&gt;4|May 27 2013|09:59:48|106023|x.x.x.x||172.18.20.12||Deny icmp src internet:x.x.x.x dst inside:172.18.20.12 (type 11, code 0) by access-group "internet_access_in" [0x0, 0x0]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Software Version:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Cisco Adaptive Security Appliance Software Version 9.0(1) &lt;/P&gt;&lt;P&gt;Device Manager Version 7.1(3)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 00:25:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215587#M349510</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-27T00:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215588#M349511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jcarvaja,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not perfomed a "clear local-host" after entering the fixup protocol commands.&amp;nbsp; May I ask what this command is and what it may do to fix the issue, I would like to understand it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As requested below is output from "show service-policy"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Global policy: &lt;/P&gt;&lt;P&gt;&amp;nbsp; Service-policy: global_policy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Class-map: inspection_default&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: dns preset_dns_map, packet 662143, lock fail 0, drop 14018, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: ftp, packet 17758, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: h323 h225 _default_h323_map, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcp-proxy: bytes in buffer 0, bytes dropped 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: h323 ras _default_h323_map, packet 2, lock fail 0, drop 2, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: rsh, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: rtsp, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcp-proxy: bytes in buffer 0, bytes dropped 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: esmtp _default_esmtp_map, packet 27, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: sqlnet, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: skinny , packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcp-proxy: bytes in buffer 0, bytes dropped 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: sunrpc, packet 16, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcp-proxy: bytes in buffer 0, bytes dropped 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: xdmcp, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: sip , packet 1, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcp-proxy: bytes in buffer 0, bytes dropped 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: netbios, packet 22990348, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: tftp, packet 246352, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: ip-options _default_ip_options_map, packet 0, lock fail 0, drop 0, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: icmp, packet 276266, lock fail 0, drop 12, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Inspect: icmp error, packet 2682, lock fail 0, drop 2, reset-drop 0, v6-fail-close 0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 00:34:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215588#M349511</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-27T00:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215589#M349512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni and Crew,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I played a bit more since my reply this morning around this issue and found following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I create an ace against the internet_access_in (outside) acl that has source and destination as any and permit all ICMP Protocols by uisng a group I created with them all added too.&amp;nbsp; An excert of the running config for this is below.&amp;nbsp; When I enable this ace the traceroutes work straight away, I thought this may be the case with the error's that syslog was showing with deny &lt;SPAN style="font-size: 10pt;"&gt;by access-group "internet_access_in" &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;access-list internet_access_in extended permit icmp any4 any object-group ICMP_Group&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I woudln't think that the above is a best practice or a good rule to have enabled as it seams to open you up from to the outside, thoughts anyone?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also notice that my outside interface responds to ping requests, I am a little confused on how it does when no rule has been specified for this.&amp;nbsp; Is it just something ASA does or? I woudln't think you would want your outside interface or public facing IP address's to respond to ICMP requests etc.&amp;nbsp; Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 04:55:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215589#M349512</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-27T04:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215590#M349513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To my understanding by default the &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;inspect icmp&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;inspect icmp error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should handle most of what you need related to ICMP. I think you need &lt;STRONG&gt;"inspect icmp error"&lt;/STRONG&gt; to make it possible for the devices in between your source host and the destination host to be able to reply through the ASA. If not you should look at opening the below mentioned ICMP messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would say its rather common to allow certain ICMP messages through the firewall. You dont have to allow ICMP echo but rather ICMP messages that are replys from remote devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess the most usual are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;time-exceeded&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;unreachable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;echo-reply&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could open the above and not allow any other ICMP messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With regards to the interface ICMP. This is not controlled by the default interface ACL. This is controlled by the command "icmp". By default each interface answers to ICMP from anywhere.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you would have to use for example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;icmp deny any outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To block ICMP. But to my understanding this will also result in the fact that the ASA cant ping anything through its "outside" unless you add "permit" format command before the "deny" that permit "echo-reply" and the other types I mentioned earlier.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;icmp permit any echo-reply outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;icmp permit any time-exceeded outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;icmp permit any unreachable outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;icmp deny any outside&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont know why the default setting is so. Might be because the ASA is shipped without any interface configurations other than the management interface. So there is no way to set the interface ICMP configuration when no such interface exists as "outside".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember to mark the reply as the correct answer if it answered your question. And/or rate helpfull answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Naturally ask more if needed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 06:24:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215590#M349513</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-27T06:24:32Z</dc:date>
    </item>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215591#M349514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Oh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And the ICMP messages being blocked on your firewall are the replys from the devices between your source host and destination host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see the ICMP Type is 11 which is time-exceeded&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the full list of the ICMP Type/Code for reference&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.iana.org/assignments/icmp-parameters/icmp-parameters.xml"&gt;http://www.iana.org/assignments/icmp-parameters/icmp-parameters.xml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 06:26:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215591#M349514</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-27T06:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215592#M349515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks so much, all makes a lot more sense now, it was staring me in the face but I didn't see it.&amp;nbsp; First time playing with ASA here &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 more question, I notice that the ASA inside and outside IP's don't show in the traceroute, from some info I have read there is some extra config required for the asa to show up on traceroutes, are you aware what this may be? Would this be a no no to do, or go against best practice? Not sure why they haven't this avail as default as one would imagine it would make life a lot easier when trouble shooting networks that every hop is scene.&amp;nbsp; Would like to hear your take on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already done some ratings and will mark your repsonse as correct onece above last question is answered as I notice you can't add to a thread once marked as correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 07:15:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215592#M349515</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-27T07:15:10Z</dc:date>
    </item>
    <item>
      <title>ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215593#M349516</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default the Cisco firewall doesnt show as a hop in the traceroute.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would imagine that the reason for this is that a security device should not be visible/detectable for the LAN/WAN users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess it depends on your network environment and policys if you want/can allow the firewall to be seen in the traceroute. Personally I havent enabled this in any of our customer environments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a good document that explains different things related to Cisco firewalls and ICMP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094e8a.shtml#asatrace"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094e8a.shtml#asatrace&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 07:27:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215593#M349516</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-05-27T07:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: ASA NAT/Traceroute Inside to Outside Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215594#M349517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jouni,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all your help with these issues, it has helped a lot.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would agree with your comments on the ASA showing in traceroute.&amp;nbsp; I tended to think before your reply that this is not something would normally do as it is a security device and yes depends on requirements and policys and so on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had just starting reading over the link you posted last night too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again, thanks for the help &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 22:57:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-traceroute-inside-to-outside-issues/m-p/2215594#M349517</guid>
      <dc:creator>hiltonstroud</dc:creator>
      <dc:date>2013-05-27T22:57:50Z</dc:date>
    </item>
  </channel>
</rss>

