<?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 I'm pretty sure you just in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882665#M159246</link>
    <description>&lt;P&gt;I'm pretty sure you just messed the 4 ACLs you're using on in/out for the two interfaces.&lt;BR /&gt;&lt;BR /&gt;I suggest you use the now classic&amp;nbsp;&lt;EM&gt;in direction&amp;nbsp;&lt;/EM&gt;for each of the two interfaces and so you get rid of two additional ACLs. Then carefully review the rest of applied ACLs.&lt;BR /&gt;&lt;BR /&gt;If you still have issues run&amp;nbsp;&lt;EM&gt;clear configure access-group&amp;nbsp;&lt;/EM&gt;and test again.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Feb 2016 21:22:42 GMT</pubDate>
    <dc:creator>Florin Barhala</dc:creator>
    <dc:date>2016-02-22T21:22:42Z</dc:date>
    <item>
      <title>ASA Outside Interface Ping not working ...</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882660#M159241</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;Not entirely convinced that I've not missed something very simple along the way but am looking for some help. Essentially I can't ping the outside interface of my ASA from another network several hops away.&amp;nbsp; However I can ping devices on the 'inside' interface.&amp;nbsp; I am guessing this some sort of ICMP policy stopping this or perhaps just the default behaviour of the ASA but I'm not sure what I've missed.&amp;nbsp; I am running version 9.4.&lt;/P&gt;
&lt;P&gt;Topology is as follows:&lt;/P&gt;
&lt;P&gt;192.168.1.0 - Inside&lt;/P&gt;
&lt;P&gt;192.168.10.0 - Outside&lt;/P&gt;
&lt;P&gt;|&lt;/P&gt;
&lt;P&gt;MPLS Network&lt;/P&gt;
&lt;P&gt;|&lt;/P&gt;
&lt;P&gt;192.168.20.0 - Remote site&lt;/P&gt;
&lt;P&gt;Access lists as follows:&lt;/P&gt;
&lt;P&gt;outside_out extended permit icmp any any object-group networksvc-ping&lt;/P&gt;
&lt;P&gt;outside_in extended permit icmp any any object-group networksvc-ping&amp;nbsp;&lt;/P&gt;
&lt;P&gt;inside_outextended permit icmp any any object-group networksvc-ping&lt;/P&gt;
&lt;P&gt;inside_in extended permit icmp any any object-group networksvc-ping&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Applied to:&lt;/P&gt;
&lt;P&gt;access-group outside_in in interface Outside&lt;BR /&gt;access-group outside_out out interface Outside&lt;BR /&gt;access-group inside_in in interface inside &lt;BR /&gt;access-group inside_out out interface inside&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Also policy-maps:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;policy-map icmp_policy&lt;BR /&gt;&amp;nbsp;class icmp-class&lt;BR /&gt;&amp;nbsp; inspect icmp &lt;BR /&gt;policy-map global_policy&lt;BR /&gt;&amp;nbsp;class inspection_default&lt;BR /&gt;&amp;nbsp; inspect dns preset_dns_map &lt;BR /&gt;&amp;nbsp; inspect ftp &lt;BR /&gt;&amp;nbsp; inspect h323 h225 &lt;BR /&gt;&amp;nbsp; inspect h323 ras &lt;BR /&gt;&amp;nbsp; inspect rsh &lt;BR /&gt;&amp;nbsp; inspect rtsp &lt;BR /&gt;&amp;nbsp; inspect esmtp &lt;BR /&gt;&amp;nbsp; inspect sqlnet &lt;BR /&gt;&amp;nbsp; inspect skinny &amp;nbsp;&lt;BR /&gt;&amp;nbsp; inspect sunrpc &lt;BR /&gt;&amp;nbsp; inspect xdmcp &lt;BR /&gt;&amp;nbsp; inspect sip &amp;nbsp;&lt;BR /&gt;&amp;nbsp; inspect netbios &lt;BR /&gt;&amp;nbsp; inspect tftp &lt;BR /&gt;&amp;nbsp; inspect ip-options&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Single default route via the inside.&amp;nbsp; Couple of statics pointing to internal networks behind the inside interface.&amp;nbsp; All inside interface IPs can be pinged.&amp;nbsp; However from the outside I cannot ping the outside interface.&amp;nbsp; Any ideas/thoughts? Can see nothing on the logs or via debug ICMP which makes me think its some sort of default behaviour that drops this traffic automatically.&amp;nbsp; No nat if configured.&lt;/P&gt;
&lt;P&gt;Thanks in advance, happy to post more config if needed.&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:22:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882660#M159241</guid>
      <dc:creator>Jim R</dc:creator>
      <dc:date>2019-03-12T07:22:24Z</dc:date>
    </item>
    <item>
      <title>FYI networksvc-grp is as</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882661#M159242</link>
      <description>&lt;P&gt;FYI networksvc-grp is as follows:&lt;/P&gt;
&lt;P&gt;object-group icmp-type networksvc-ping&lt;BR /&gt;&amp;nbsp;icmp-object echo&lt;BR /&gt;&amp;nbsp;icmp-object echo-reply&lt;BR /&gt;&amp;nbsp;icmp-object time-exceeded&lt;BR /&gt;&amp;nbsp;icmp-object traceroute&lt;BR /&gt;&amp;nbsp;icmp-object source-quench&lt;BR /&gt;&amp;nbsp;icmp-object unreachable&lt;/P&gt;</description>
      <pubDate>Sun, 21 Feb 2016 21:15:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882661#M159242</guid>
      <dc:creator>Jim R</dc:creator>
      <dc:date>2016-02-21T21:15:23Z</dc:date>
    </item>
    <item>
      <title>Where is the PC located that</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882662#M159243</link>
      <description>&lt;P&gt;Where is the PC located that you are pinging from? &amp;nbsp;Is the outside interface the ingress interface for the ICMP packets? &amp;nbsp;You may already know, but you can not ping an interface that is not the ingress interface on the ASA.&lt;/P&gt;
&lt;P&gt;If this is not the case, try adding the command &lt;STRONG&gt;icmp permit any outside&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Sun, 21 Feb 2016 21:42:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882662#M159243</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-02-21T21:42:52Z</dc:date>
    </item>
    <item>
      <title>Hi Maria</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882663#M159244</link>
      <description>&lt;P&gt;Hi Maria&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The PC is on the outside so the packet would be inbound on the outside interface. I did try the command you discussed previously but with no success.&amp;nbsp; Thanks for taking the time to reply though &lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Feb 2016 22:34:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882663#M159244</guid>
      <dc:creator>Jim R</dc:creator>
      <dc:date>2016-02-21T22:34:13Z</dc:date>
    </item>
    <item>
      <title>If you put a laptop on the</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882664#M159245</link>
      <description>&lt;P&gt;If you put a laptop on the same network as the outside interface, are you then able to ping the outside IP of the ASA?&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Sun, 21 Feb 2016 22:37:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882664#M159245</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-02-21T22:37:56Z</dc:date>
    </item>
    <item>
      <title>I'm pretty sure you just</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882665#M159246</link>
      <description>&lt;P&gt;I'm pretty sure you just messed the 4 ACLs you're using on in/out for the two interfaces.&lt;BR /&gt;&lt;BR /&gt;I suggest you use the now classic&amp;nbsp;&lt;EM&gt;in direction&amp;nbsp;&lt;/EM&gt;for each of the two interfaces and so you get rid of two additional ACLs. Then carefully review the rest of applied ACLs.&lt;BR /&gt;&lt;BR /&gt;If you still have issues run&amp;nbsp;&lt;EM&gt;clear configure access-group&amp;nbsp;&lt;/EM&gt;and test again.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2016 21:22:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882665#M159246</guid>
      <dc:creator>Florin Barhala</dc:creator>
      <dc:date>2016-02-22T21:22:42Z</dc:date>
    </item>
    <item>
      <title>Hi Florin,</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882666#M159247</link>
      <description>&lt;P&gt;Hi Florin,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Originally the configuration had the traditional 'in' rules only.&amp;nbsp; The outbound rules were added to see if they made any difference which they didn't.&amp;nbsp; I've had it set where we have allowed ICMP in on both in the inside and outside interfaces yet still no dice.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your input though.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;J&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2016 21:39:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882666#M159247</guid>
      <dc:creator>Jim R</dc:creator>
      <dc:date>2016-02-22T21:39:07Z</dc:date>
    </item>
    <item>
      <title>I'm not physically able to</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882667#M159248</link>
      <description>&lt;P&gt;I'm not physically able to get near the device to try this at the moment Marius, however I will give this a go (I am reasonably sure this has worked in the past though as I think we tested this during deployment)&lt;/P&gt;
&lt;P&gt;Cheer,&lt;/P&gt;
&lt;P&gt;J&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2016 21:40:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882667#M159248</guid>
      <dc:creator>Jim R</dc:creator>
      <dc:date>2016-02-22T21:40:37Z</dc:date>
    </item>
    <item>
      <title>Another thing to check is if</title>
      <link>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882668#M159249</link>
      <description>&lt;P&gt;Another thing to check is if the ASA has a route back to the network you are pinging from.&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;Please select a correct answer and rate helpful posts&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2016 21:54:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-outside-interface-ping-not-working/m-p/2882668#M159249</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2016-02-22T21:54:45Z</dc:date>
    </item>
  </channel>
</rss>

