<?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: firewall interface un-pingable in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firewall-interface-un-pingable/m-p/1456543#M654956</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bruce,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're trying to ping one interface coming in from the other it will not work (not in a basic connectivity set, possible solution is to you management-inside + VPN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, show us the logs on informtion level generated by firewall at time of pinging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Jul 2010 09:51:39 GMT</pubDate>
    <dc:creator>Marcin Latosiewicz</dc:creator>
    <dc:date>2010-07-03T09:51:39Z</dc:date>
    <item>
      <title>firewall interface un-pingable</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interface-un-pingable/m-p/1456542#M654954</link>
      <description>&lt;P&gt;Hey folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm working on a FWSM code v3.2(2) in multiple context mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a context that has several hosts within a VLAN terminated in this context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can ping into and out from these hosts.&amp;nbsp; However, I am unable to ping into the firewall and get a response from the VLAN interface for that vlan..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hosts can ping the interface, the firewall can of course ping the interface, but from outside, i cannot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have configured the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; ICMP any &amp;lt;interface&amp;gt;&lt;/P&gt;&lt;P&gt;Access-group &amp;lt;acl name&amp;gt; in &amp;lt;interface&amp;gt;&lt;/P&gt;&lt;P&gt;access-list &amp;lt;acl name&amp;gt; permit icmp any any&lt;/P&gt;&lt;P&gt;access-list &amp;lt;outside acl&amp;gt; permit icmp any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts on what is occurring...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bruce&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:06:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interface-un-pingable/m-p/1456542#M654954</guid>
      <dc:creator>Bruce Summers</dc:creator>
      <dc:date>2019-03-11T18:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: firewall interface un-pingable</title>
      <link>https://community.cisco.com/t5/network-security/firewall-interface-un-pingable/m-p/1456543#M654956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bruce,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you're trying to ping one interface coming in from the other it will not work (not in a basic connectivity set, possible solution is to you management-inside + VPN).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not, show us the logs on informtion level generated by firewall at time of pinging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jul 2010 09:51:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firewall-interface-un-pingable/m-p/1456543#M654956</guid>
      <dc:creator>Marcin Latosiewicz</dc:creator>
      <dc:date>2010-07-03T09:51:39Z</dc:date>
    </item>
  </channel>
</rss>

