<?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 ACL Hits in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412546#M309710</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;Is this some ACL on a router or a firewall? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a typo in the network/IP in the ACL? Post says 172.18.0.0 and the ACL 172.180.0.0?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would presume that since your first rule specifies &lt;STRONG&gt;"any"&lt;/STRONG&gt; as the source address it then matches all the connections from the 172.18.0.0/xx (or 172.180.0.0) subnet and because of this the new rule below it doesnt get any hitcounts. That is if you are lookking for ACL hits towards 10.114.172.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First thing would be to determine if there is a typo in the ACL and after that insert the rule with the correct subnet at the top. Then again the only affect this would have is that you would see the hitcounts from this certain source network while nothing else would change with regards to the ACL behaviour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Nov 2013 09:08:41 GMT</pubDate>
    <dc:creator>Jouni Forss</dc:creator>
    <dc:date>2013-11-04T09:08:41Z</dc:date>
    <item>
      <title>ACL Hits</title>
      <link>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412545#M309706</link>
      <description>&lt;P&gt;hi i have a question this acl is accessed by only 172.18.0.0 subnet so i created another acl placed at the bottom of this acl.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; any&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.114.172.10&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; permit &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;172.180.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.114.172.10&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; permit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above acl is getting hits but the second one is not getting hits. I have enabled both rules. do i need 2 change order or disable the 1st rule please give your suggestions. &lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:59:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412545#M309706</guid>
      <dc:creator>nishanthjavvadi1</dc:creator>
      <dc:date>2019-03-12T02:59:44Z</dc:date>
    </item>
    <item>
      <title>ACL Hits</title>
      <link>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412546#M309710</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;Is this some ACL on a router or a firewall? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a typo in the network/IP in the ACL? Post says 172.18.0.0 and the ACL 172.180.0.0?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would presume that since your first rule specifies &lt;STRONG&gt;"any"&lt;/STRONG&gt; as the source address it then matches all the connections from the 172.18.0.0/xx (or 172.180.0.0) subnet and because of this the new rule below it doesnt get any hitcounts. That is if you are lookking for ACL hits towards 10.114.172.10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First thing would be to determine if there is a typo in the ACL and after that insert the rule with the correct subnet at the top. Then again the only affect this would have is that you would see the hitcounts from this certain source network while nothing else would change with regards to the ACL behaviour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 09:08:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412546#M309710</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-11-04T09:08:41Z</dc:date>
    </item>
    <item>
      <title>ACL Hits</title>
      <link>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412547#M309712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Jouni.&amp;nbsp; The first entry matches any source destined for the address 10.114.172.10.&amp;nbsp; So technically you would not need the second command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to see matches on the &lt;STRONG&gt;172.180.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.114.172.10&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; permit&lt;/STRONG&gt; statement then that needs to be placed above the first rule.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 09:36:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-hits/m-p/2412547#M309712</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2013-11-04T09:36:32Z</dc:date>
    </item>
  </channel>
</rss>

