<?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: Time range ACL on ASA5510 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730712#M9331</link>
    <description>&lt;P&gt;The example i have given to allow in that time range, you should have deny rule also to cover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Oct 2018 13:05:25 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2018-10-23T13:05:25Z</dc:date>
    <item>
      <title>Time range ACL on ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730155#M9323</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I try to allow communication for one specific IP to connect on the Internet in only specific time ranges.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Monday to Friday 7:00PM to 8:30PM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As I know I not possible to start a new communication outside of this time window.&amp;nbsp; But I was expect if a communication was started&amp;nbsp;within the time range, that communication will be deny starting at 8:30PM, but I found the communication was still available at 8:45PM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any other option that I should modify to make it work as I was expected ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:22:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730155#M9323</guid>
      <dc:creator>christianpho</dc:creator>
      <dc:date>2020-02-21T16:22:55Z</dc:date>
    </item>
    <item>
      <title>Re: Time range ACL on ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730194#M9326</link>
      <description>&lt;P&gt;what is the ASA Version here :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but high level example&amp;nbsp;&amp;nbsp;:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;time-range working_hours&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;periodic weekdays 19:00 to 20:30&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;access-list limit extended permit ip host 192.168.1.10 any time-range working_hours&lt;BR /&gt;access-list limit extended permit ip any host 192.168.1.10 time-range working_hours&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;class-map class&lt;BR /&gt;match access-list limit&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;policy-map outside-policy&lt;BR /&gt;class class&lt;BR /&gt;service-policy outside-policy interface outside&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 21:05:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730194#M9326</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2018-10-22T21:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Time range ACL on ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730645#M9329</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Actually, the ASA run 9.1.(7)16 and ASDM&amp;nbsp; VERSION 7.7.(1)150.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ACL is directly applied on the inside interface without using any service policy.&amp;nbsp; I works at some point since the connection not start if the connection is tried before the allowed period.&amp;nbsp; But after the communication flow is establish it continue to works after the allowed period.&amp;nbsp; Maybe important ting to notice most of the communication would based on UDP paquets.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Inside interface as been dedicated for that communication.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 23 Oct 2018 12:00:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730645#M9329</guid>
      <dc:creator>christianpho</dc:creator>
      <dc:date>2018-10-23T12:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: Time range ACL on ASA5510</title>
      <link>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730712#M9331</link>
      <description>&lt;P&gt;The example i have given to allow in that time range, you should have deny rule also to cover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Oct 2018 13:05:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/time-range-acl-on-asa5510/m-p/3730712#M9331</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2018-10-23T13:05:25Z</dc:date>
    </item>
  </channel>
</rss>

