<?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's top to bottom? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/acl-s-top-to-bottom/m-p/5272211#M1120101</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199267"&gt;@sir_yrwins&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;you need to consolidate all the rules into a single ACL instead of applying multiple separate ACLs.&lt;/P&gt;
&lt;P&gt;routerA(config)#access-list 100 deny ip 0.0.0.0 0.255.255.255 any &lt;BR /&gt;routerA(config)#access-list 100 deny ip 10.16.1.0 0.0.0.255 any &lt;BR /&gt;routerA(config)#access-list 100 permit ip any any&amp;nbsp;&lt;BR /&gt;routerA(config)#interface Gi/0/0 &lt;BR /&gt;routerA(config-if)#ip access-group 100 in&lt;/P&gt;
&lt;P data-start="1139" data-end="1356"&gt;Now, the router will evaluate packets against &lt;STRONG data-start="1185" data-end="1201"&gt;ACL 100 only&lt;/STRONG&gt;, processing rules in order. It will first block any traffic from 0.0.0.0/8, then block traffic from 10.16.1.0/24, and finally allow everything else.&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;The key takeaway here is that you can only have one ACL per interface per direction.&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 21:38:50 GMT</pubDate>
    <dc:creator>M02@rt37</dc:creator>
    <dc:date>2025-03-17T21:38:50Z</dc:date>
    <item>
      <title>ACL's top to bottom?</title>
      <link>https://community.cisco.com/t5/network-security/acl-s-top-to-bottom/m-p/5272208#M1120100</link>
      <description>&lt;P&gt;internet-----&amp;gt; Gi/0/0&amp;nbsp;&lt;/P&gt;&lt;P&gt;routerA(config)#access-list 100 deny ip 0.0.0.0 0.255.255.255 any&lt;/P&gt;&lt;P&gt;routerA(config)#access-list 101 deny ip 10.16.1.0 0.0.0.255 any&lt;/P&gt;&lt;P&gt;routerA(config)#access-list 102 permit ip 10.16.1.0 0.0.0.255 any&lt;/P&gt;&lt;P&gt;routerA(config)#interface Gi/0/0&lt;/P&gt;&lt;P&gt;routerA(config-if)#ip access-gorup 100 in&lt;/P&gt;&lt;P&gt;routerA(config-if)#ip access-gorup 101 in&lt;/P&gt;&lt;P&gt;routerA(config-if)#ip access-gorup 102 in&lt;/P&gt;&lt;P&gt;this were I am lost ( why all traffic destined for the&amp;nbsp;10.16.1.0 /24 network will be allowed)&lt;/P&gt;&lt;P&gt;why rule 101 (deny) is been ignored. the packet (rules) is read from top to bottom! and it read rule 101 is for deny so it drops, before I can read 102?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 21:31:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-s-top-to-bottom/m-p/5272208#M1120100</guid>
      <dc:creator>sir_yrwins</dc:creator>
      <dc:date>2025-03-17T21:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: ACL's top to bottom?</title>
      <link>https://community.cisco.com/t5/network-security/acl-s-top-to-bottom/m-p/5272211#M1120101</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199267"&gt;@sir_yrwins&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;you need to consolidate all the rules into a single ACL instead of applying multiple separate ACLs.&lt;/P&gt;
&lt;P&gt;routerA(config)#access-list 100 deny ip 0.0.0.0 0.255.255.255 any &lt;BR /&gt;routerA(config)#access-list 100 deny ip 10.16.1.0 0.0.0.255 any &lt;BR /&gt;routerA(config)#access-list 100 permit ip any any&amp;nbsp;&lt;BR /&gt;routerA(config)#interface Gi/0/0 &lt;BR /&gt;routerA(config-if)#ip access-group 100 in&lt;/P&gt;
&lt;P data-start="1139" data-end="1356"&gt;Now, the router will evaluate packets against &lt;STRONG data-start="1185" data-end="1201"&gt;ACL 100 only&lt;/STRONG&gt;, processing rules in order. It will first block any traffic from 0.0.0.0/8, then block traffic from 10.16.1.0/24, and finally allow everything else.&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;The key takeaway here is that you can only have one ACL per interface per direction.&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="1358" data-end="1596" data-is-last-node="" data-is-only-node=""&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 21:38:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/acl-s-top-to-bottom/m-p/5272211#M1120101</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2025-03-17T21:38:50Z</dc:date>
    </item>
  </channel>
</rss>

