<?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: Cisco ASA Public Interface in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675995#M543102</link>
    <description>&lt;P&gt;The usage guidelines&amp;nbsp;@&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/I-R/cmdref2/i1.html" target="_blank"&gt;icmp -- import webvpn webcontent&lt;/A&gt;&amp;nbsp;states,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;...&lt;BR /&gt;
&lt;P&gt;&lt;SPAN&gt;The ASA only responds to ICMP traffic sent to the interface that traffic comes in on; you cannot send ICMP traffic through an interface to a far interface.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;...&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;It's probably due to routing in a stateful firewall, such as ASA.&lt;/P&gt;
&lt;P&gt;For network troubleshooting, we may ping another device either in the same public subnet or further upstream.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Jul 2018 05:35:56 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2018-07-27T05:35:56Z</dc:date>
    <item>
      <title>Cisco ASA Public Interface</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675943#M543096</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to access from a network behind a Cisco ASA Firewall Lan Interface to its own public IP Interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Eg&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;User 10.1.1.100/24 ------------10.1.1.1/24 : LAN FW PUB : 1.1.1.1/32&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible that the user (10.1.1.100) can access to ip 1.1.1.1 of the ASA Public Interface.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:47:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675943#M543096</guid>
      <dc:creator>maileh</dc:creator>
      <dc:date>2019-03-11T08:47:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Public Interface</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675948#M543099</link>
      <description>&lt;P&gt;No it’s not possible. The ASA will not allow you to reach it’s own interface through the device.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jul 2018 02:37:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675948#M543099</guid>
      <dc:creator>Troy Jackson</dc:creator>
      <dc:date>2018-07-27T02:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Public Interface</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675952#M543101</link>
      <description>&lt;P&gt;Hi Troy&lt;/P&gt;
&lt;P&gt;Thanks for your confirmation. Yes thats right and that is what i am experiencing.&lt;/P&gt;
&lt;P&gt;I also work with Huawei UDEMON FW which they allowed.&lt;/P&gt;
&lt;P&gt;Its really interesting to know why ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jul 2018 02:50:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675952#M543101</guid>
      <dc:creator>maileh</dc:creator>
      <dc:date>2018-07-27T02:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Public Interface</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675995#M543102</link>
      <description>&lt;P&gt;The usage guidelines&amp;nbsp;@&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa-command-reference/I-R/cmdref2/i1.html" target="_blank"&gt;icmp -- import webvpn webcontent&lt;/A&gt;&amp;nbsp;states,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;...&lt;BR /&gt;
&lt;P&gt;&lt;SPAN&gt;The ASA only responds to ICMP traffic sent to the interface that traffic comes in on; you cannot send ICMP traffic through an interface to a far interface.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;...&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;It's probably due to routing in a stateful firewall, such as ASA.&lt;/P&gt;
&lt;P&gt;For network troubleshooting, we may ping another device either in the same public subnet or further upstream.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jul 2018 05:35:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-asa-public-interface/m-p/3675995#M543102</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2018-07-27T05:35:56Z</dc:date>
    </item>
  </channel>
</rss>

