<?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 Hi, in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985041#M147808</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;When you apply the global ACL, the implicit deny that you had on any other ACL will be moving to be at the end of the global ACL. But, any explicit deny will not be moved, it will remain on the other ACLs. Also, the order of matching will still start from the top of the other ACL applied, in your example, the check order will start on ACL outside_in from the top, as usual, if not match&amp;nbsp;is found on outside_in ACL, then it will start checking from the top on the global ACL, if no match is found the implicit deny on the global ACL will be applied and the traffic will be dropped. The easiest way to think about the global ACL is that it will be appended to any other ACL applied on an interface. In your case, it has been appended to the ACL outside_in, like if the ACL outside_in has extended its lines. Also please remember that global ACL is applied in inbound direction.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Aref&lt;/P&gt;</description>
    <pubDate>Fri, 13 Jan 2017 00:13:00 GMT</pubDate>
    <dc:creator>Aref Alsouqi</dc:creator>
    <dc:date>2017-01-13T00:13:00Z</dc:date>
    <item>
      <title>Global ACL query , does not work as documented</title>
      <link>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985039#M147806</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt; &lt;BR /&gt; I was studying about global acl and created a small lab 3 routers , one asa,&lt;BR /&gt; &lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;R2(DMZ)&lt;BR /&gt; &amp;nbsp;&amp;nbsp;^&lt;BR /&gt; (INSIDE)R3&amp;gt;ASA&amp;gt;R1 (OUTSIDE)&lt;BR /&gt; &lt;BR /&gt; Its from INE security video - 80&lt;BR /&gt; &lt;BR /&gt; have only 2 access-groups as of now outside_in and one global acl global_in&lt;BR /&gt; &lt;BR /&gt; documentation says once we have a global acl, the effect of interface specific ACL's explicity deny ip any goes. and global acl takes precendence. however i tested on gns3. it is still taking outside interface acl and not taking global acl for something i am not allowing through both acls.&lt;BR /&gt; &lt;BR /&gt; an output from logging is&lt;BR /&gt; &lt;BR /&gt; %ASA-4-106023: Deny tcp src outside:136.1.49.1/38389 dst dmz:136.1.59.2/23 by access-group "outside_in" [0x0, 0x0]&lt;BR /&gt; %ASA-4-106023: Deny tcp src outside:136.1.49.1/38389 dst dmz:136.1.59.2/23 by access-group "outside_in" [0x0, 0x0]&lt;BR /&gt; &lt;BR /&gt; however i was expecting the access-group should be global.&lt;BR /&gt; &lt;BR /&gt; Assistance appreciated. Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:46:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985039#M147806</guid>
      <dc:creator>himanshujain2009</dc:creator>
      <dc:date>2019-03-12T08:46:09Z</dc:date>
    </item>
    <item>
      <title>Please post show run access-l</title>
      <link>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985040#M147807</link>
      <description>&lt;P&gt;Please post show run access-l outside_in , show run access-l global_in, show run access-g&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Also, please check packet-trace to see where is the traffic getting dropped exactly.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jan 2017 06:12:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985040#M147807</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-01-12T06:12:44Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985041#M147808</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;When you apply the global ACL, the implicit deny that you had on any other ACL will be moving to be at the end of the global ACL. But, any explicit deny will not be moved, it will remain on the other ACLs. Also, the order of matching will still start from the top of the other ACL applied, in your example, the check order will start on ACL outside_in from the top, as usual, if not match&amp;nbsp;is found on outside_in ACL, then it will start checking from the top on the global ACL, if no match is found the implicit deny on the global ACL will be applied and the traffic will be dropped. The easiest way to think about the global ACL is that it will be appended to any other ACL applied on an interface. In your case, it has been appended to the ACL outside_in, like if the ACL outside_in has extended its lines. Also please remember that global ACL is applied in inbound direction.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Aref&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2017 00:13:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/global-acl-query-does-not-work-as-documented/m-p/2985041#M147808</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2017-01-13T00:13:00Z</dc:date>
    </item>
  </channel>
</rss>

