<?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: ACL NAT ICMP Confusion in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907631#M974643</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You probably need to ask Cisco about the reasoning behind this logic.  maybe they saw no need to allow users to be able to use nat exemption based on ports/protocols&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Sep 2007 18:08:02 GMT</pubDate>
    <dc:creator>srue</dc:creator>
    <dc:date>2007-09-21T18:08:02Z</dc:date>
    <item>
      <title>ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907626#M974638</link>
      <description>&lt;P&gt;Riddle me this.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Given an ACL that has the following line in it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TEST-NONAT extended permit icmp host EDISRV host X.X.X.X&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I attempt the following I get this error message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA(config)# nat (INSIDE) 0 access-list TEST-NONAT&lt;/P&gt;&lt;P&gt;ERROR: access-list has protocol or port&lt;/P&gt;&lt;P&gt;ASA(config)# &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At which point I scratch my head and say "well of course the acl has a protocol and port"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I remove the ACL line I posted above the nat statement is accepted just fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not understand why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:15:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907626#M974638</guid>
      <dc:creator>whisperwind</dc:creator>
      <dc:date>2019-03-11T11:15:05Z</dc:date>
    </item>
    <item>
      <title>Re: ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907627#M974639</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use a port in an access-list that is there for NAT exemption. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use ports in access-lists for policy NAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 17:33:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907627#M974639</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-09-21T17:33:08Z</dc:date>
    </item>
    <item>
      <title>Re: ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907628#M974640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yeah but icmp is a protocol not a port....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 17:42:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907628#M974640</guid>
      <dc:creator>whisperwind</dc:creator>
      <dc:date>2007-09-21T17:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907629#M974641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;and the error says "protocol or port".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 17:47:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907629#M974641</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-09-21T17:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907630#M974642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Come on srue that is not helpful at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why does exempting ping something is it denied? I can understand the port but not icmp, can anyone explain that to me?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 17:53:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907630#M974642</guid>
      <dc:creator>whisperwind</dc:creator>
      <dc:date>2007-09-21T17:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: ACL NAT ICMP Confusion</title>
      <link>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907631#M974643</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You probably need to ask Cisco about the reasoning behind this logic.  maybe they saw no need to allow users to be able to use nat exemption based on ports/protocols&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2007 18:08:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-nat-icmp-confusion/m-p/907631#M974643</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-09-21T18:08:02Z</dc:date>
    </item>
  </channel>
</rss>

