<?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: Issue with interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/issue-with-interface/m-p/1653232#M627520</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How is the NATing done between the interfaces? If you are actually NATing those traffic, you won't be able to perform "ping inside x.x.x.x" to ping an external host as ASA does not NAT when traffic is being sourced from its internal interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe more information on the actual ASA interface, the NATing that you have configured, also the source and destination ip address. That will help to provide more context into the actual topology.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Mar 2011 00:12:10 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2011-03-11T00:12:10Z</dc:date>
    <item>
      <title>Issue with interface</title>
      <link>https://community.cisco.com/t5/network-security/issue-with-interface/m-p/1653231#M627506</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am currently having an issue accessing a network through my firewall.&amp;nbsp; I have access-list that allow this particular network in and access-list that allow me to this network(inside out).&amp;nbsp; I have checked my acl's, static routes, reverted to failover, rebooted my firewall as well as checked my switch settings all with failed results.&amp;nbsp; From the firewall I can ping network (ping x.x.x.x) but when I try it from the interface that need to talk to the network it doesn't work (ping inside x.x.x.x).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone has any suggestions or pointers it would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:04:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-with-interface/m-p/1653231#M627506</guid>
      <dc:creator>ciscona728</dc:creator>
      <dc:date>2019-03-11T20:04:42Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with interface</title>
      <link>https://community.cisco.com/t5/network-security/issue-with-interface/m-p/1653232#M627520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How is the NATing done between the interfaces? If you are actually NATing those traffic, you won't be able to perform "ping inside x.x.x.x" to ping an external host as ASA does not NAT when traffic is being sourced from its internal interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe more information on the actual ASA interface, the NATing that you have configured, also the source and destination ip address. That will help to provide more context into the actual topology.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Mar 2011 00:12:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/issue-with-interface/m-p/1653232#M627520</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2011-03-11T00:12:10Z</dc:date>
    </item>
  </channel>
</rss>

