<?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: History, benefit, using of gt and lt in ACL rule in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4132660#M1072760</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;"gt" = greater than, which in your example this is permitting all dynamic ports above 1023, so from tcp port 1023 - 65535. Normally you'd specify "eq" which specifies the exact port, but in some circumstances you may wish to permit the dynamic ports for some applications, such as MS RPC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sequence number is important, the ACL is processed top down, so first match takes precedence. If a packet matches seq #10, then it will be permitted and not process the rest of the ACL. It also helps with re-ordering the ACE.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-3s/sec-data-acl-xe-3s-book/sec-acl-seq-num.html" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-3s/sec-data-acl-xe-3s-book/sec-acl-seq-num.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
    <pubDate>Sun, 09 Aug 2020 08:24:20 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2020-08-09T08:24:20Z</dc:date>
    <item>
      <title>History, benefit, using of gt and lt in ACL rule</title>
      <link>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4132656#M1072759</link>
      <description>&lt;P&gt;As rules below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;10 access-list 102 permit tcp any host 192.168.1.100 eq ftp
20 access-list 102 permit tcp any host 192.168.1.100 gt 1023&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;What is&amp;nbsp;History, benefit, using &lt;STRONG&gt;gt&lt;/STRONG&gt; and &lt;STRONG&gt;lt &lt;/STRONG&gt;(line 20)?&lt;/P&gt;&lt;P&gt;Is there meaning in ports sequence number?&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2020 08:06:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4132656#M1072759</guid>
      <dc:creator>mgae2m400</dc:creator>
      <dc:date>2020-08-09T08:06:09Z</dc:date>
    </item>
    <item>
      <title>Re: History, benefit, using of gt and lt in ACL rule</title>
      <link>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4132660#M1072760</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;"gt" = greater than, which in your example this is permitting all dynamic ports above 1023, so from tcp port 1023 - 65535. Normally you'd specify "eq" which specifies the exact port, but in some circumstances you may wish to permit the dynamic ports for some applications, such as MS RPC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sequence number is important, the ACL is processed top down, so first match takes precedence. If a packet matches seq #10, then it will be permitted and not process the rest of the ACL. It also helps with re-ordering the ACE.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-3s/sec-data-acl-xe-3s-book/sec-acl-seq-num.html" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_acl/configuration/xe-3s/sec-data-acl-xe-3s-book/sec-acl-seq-num.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Sun, 09 Aug 2020 08:24:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4132660#M1072760</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2020-08-09T08:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: History, benefit, using of gt and lt in ACL rule</title>
      <link>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4997562#M1107983</link>
      <description>&lt;P&gt;just to keep it exact:&lt;/P&gt;
&lt;P&gt;"gt" = greater than, which in your example this is permitting all dynamic ports above 1023, so from tcp port &lt;STRONG&gt;1024&lt;/STRONG&gt; - 65535.&lt;/P&gt;
&lt;P&gt;...gt is not "equal or greater than", just "greater than"&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2024 11:08:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/history-benefit-using-of-gt-and-lt-in-acl-rule/m-p/4997562#M1107983</guid>
      <dc:creator>r.heitmann</dc:creator>
      <dc:date>2024-01-16T11:08:36Z</dc:date>
    </item>
  </channel>
</rss>

