<?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: Query on Time Based Access-lists in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/query-on-time-based-access-lists/m-p/1286680#M859330</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The creation of a time range does not restrict access to the device. The time-range command defines the time range only. After a time range is defined, you can attach it to traffic rules or an action.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to implement a time-based ACL, use the time-range command to define specific times of the day and week. Then use the with the access-list extended time-range command to bind the time range to an ACL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The time range relies on the system clock of the security appliance. However, the feature works best with NTP synchronization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After you have created a time range and entered time-range configuration mode, you can define time range parameters with the absolute and periodic commands. In order to restore default settings for the time-range command absolute and periodic keywords, use the default command in time-range configuration mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to implement a time-based ACL, use the time-range command to define specific times of the day and week. Then use the with the access-list extended command to bind the time range to an ACL. The next example binds an ACL named "Sales" to a time range named "New York Minute": &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This example creates a time range named "New York Minute" and enters time-range configuration mode: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hostname(config)#time-range New_York_Minute&lt;/P&gt;&lt;P&gt;hostname(config-time-range)#periodic weekdays 07:00 to 19:00&lt;/P&gt;&lt;P&gt;hostname(config)#access-list Sales line 1 extended deny ip any any time-range New_York_Minute&lt;/P&gt;&lt;P&gt;hostname(config)#access-group Sales in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Jun 2009 18:38:58 GMT</pubDate>
    <dc:creator>ldardon</dc:creator>
    <dc:date>2009-06-22T18:38:58Z</dc:date>
    <item>
      <title>Query on Time Based Access-lists</title>
      <link>https://community.cisco.com/t5/network-security/query-on-time-based-access-lists/m-p/1286679#M859326</link>
      <description>&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been using the time based ACLs for quite a while now. But I never able to figure out, to how many time-ranges we can create on a ASA 5510 and ASA 5520. Is there any limitation to that, to how many time-ranges we can define?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Arabinda&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:44:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/query-on-time-based-access-lists/m-p/1286679#M859326</guid>
      <dc:creator>arabindas</dc:creator>
      <dc:date>2019-03-11T15:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Time Based Access-lists</title>
      <link>https://community.cisco.com/t5/network-security/query-on-time-based-access-lists/m-p/1286680#M859330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The creation of a time range does not restrict access to the device. The time-range command defines the time range only. After a time range is defined, you can attach it to traffic rules or an action.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to implement a time-based ACL, use the time-range command to define specific times of the day and week. Then use the with the access-list extended time-range command to bind the time range to an ACL. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The time range relies on the system clock of the security appliance. However, the feature works best with NTP synchronization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After you have created a time range and entered time-range configuration mode, you can define time range parameters with the absolute and periodic commands. In order to restore default settings for the time-range command absolute and periodic keywords, use the default command in time-range configuration mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to implement a time-based ACL, use the time-range command to define specific times of the day and week. Then use the with the access-list extended command to bind the time range to an ACL. The next example binds an ACL named "Sales" to a time range named "New York Minute": &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This example creates a time range named "New York Minute" and enters time-range configuration mode: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hostname(config)#time-range New_York_Minute&lt;/P&gt;&lt;P&gt;hostname(config-time-range)#periodic weekdays 07:00 to 19:00&lt;/P&gt;&lt;P&gt;hostname(config)#access-list Sales line 1 extended deny ip any any time-range New_York_Minute&lt;/P&gt;&lt;P&gt;hostname(config)#access-group Sales in interface inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jun 2009 18:38:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/query-on-time-based-access-lists/m-p/1286680#M859330</guid>
      <dc:creator>ldardon</dc:creator>
      <dc:date>2009-06-22T18:38:58Z</dc:date>
    </item>
  </channel>
</rss>

