<?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: ASA nat access list hit count in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-access-list-hit-count/m-p/972174#M919074</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think to speed up things, for existing sessions (already in the state table) NAT policy and various other lookups etc are not performed. Perhaps this is the reason why you are seeing this behavior. So you will see a hit in the NAT statement for only the first packet in the flow (or based on some other similar criteria).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Jun 2008 18:21:13 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2008-06-02T18:21:13Z</dc:date>
    <item>
      <title>ASA nat access list hit count</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-access-list-hit-count/m-p/972173#M919066</link>
      <description>&lt;P&gt;Can someone tell me why v7.2 of the PIX/ASA OS doesn't register hits on an access list used for nat?  I always used this on v6 to check the rule was working.  The show nat command seems to be a bit random with it's counters as well.  Is there another way to monitor the nat rules that i'm missing? &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 12:54:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-access-list-hit-count/m-p/972173#M919066</guid>
      <dc:creator>edd.phillips</dc:creator>
      <dc:date>2019-03-11T12:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: ASA nat access list hit count</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-access-list-hit-count/m-p/972174#M919074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think to speed up things, for existing sessions (already in the state table) NAT policy and various other lookups etc are not performed. Perhaps this is the reason why you are seeing this behavior. So you will see a hit in the NAT statement for only the first packet in the flow (or based on some other similar criteria).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jun 2008 18:21:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-access-list-hit-count/m-p/972174#M919074</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-02T18:21:13Z</dc:date>
    </item>
  </channel>
</rss>

