<?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: Backup WAN is not pingable on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210322#M1065034</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/274064"&gt;@Matt&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Firewall does not allow for ping on the outside interfaces for security reason. Most exploit tools use icmp response to make sure host is alive and start scratching.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;If this is necessary for some reason try to allow it:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any unreachable outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any time-exceeded outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any echo-reply outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;no icmp deny any outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-If I helped you somehow, please, rate it as useful.-&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 03 Nov 2017 11:50:23 GMT</pubDate>
    <dc:creator>Flavio Miranda</dc:creator>
    <dc:date>2017-11-03T11:50:23Z</dc:date>
    <item>
      <title>Backup WAN is not pingable on ASA</title>
      <link>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210157#M1065030</link>
      <description>&lt;P&gt;I have an ASA with two WAN uplinks. The backup WAN is not pingable while the primary WAN is. However, I can SSH into the ASA on either uplink. I've seen a few articles saying that this behavior is expected and I was wondering if anyone could explain why I cannot ping the backup WAN even though I can SSH to it. Is there a routing condition that affects pings but not SSH in this case, or is there something else I am missing?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:38:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210157#M1065030</guid>
      <dc:creator>Matt</dc:creator>
      <dc:date>2020-02-21T14:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Backup WAN is not pingable on ASA</title>
      <link>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210322#M1065034</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/274064"&gt;@Matt&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;Firewall does not allow for ping on the outside interfaces for security reason. Most exploit tools use icmp response to make sure host is alive and start scratching.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;If this is necessary for some reason try to allow it:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any unreachable outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any time-exceeded outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;icmp permit any echo-reply outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;no icmp deny any outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-If I helped you somehow, please, rate it as useful.-&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2017 11:50:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210322#M1065034</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-11-03T11:50:23Z</dc:date>
    </item>
    <item>
      <title>Re: Backup WAN is not pingable on ASA</title>
      <link>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210457#M1065037</link>
      <description>&lt;P&gt;Hi Flavio,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That ICMP access is already permitted. Both the WAN1 and WAN2 use the same access-group to permit this traffic so in this case I think it's something outside of the access rules causing it to be unpingable.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2017 15:03:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210457#M1065037</guid>
      <dc:creator>Matt</dc:creator>
      <dc:date>2017-11-03T15:03:47Z</dc:date>
    </item>
    <item>
      <title>Re: Backup WAN is not pingable on ASA</title>
      <link>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210683#M1065039</link>
      <description>&lt;P&gt;Are you inspecting icmp on this firewall ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2017 20:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-wan-is-not-pingable-on-asa/m-p/3210683#M1065039</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2017-11-03T20:14:25Z</dc:date>
    </item>
  </channel>
</rss>

