More info on QoS to help make sure the traffic you need to get through gets though. This one puts time limits on the policies. I find QoS to be so cool.

Networkers-Online

Limiting non-business related applications during work hours

In this post we will explore how to limit or even stop your employees from using applications that are not related to the business during work hours.
In the following example I am going to use HTTP as an example for unwanted applications, you can specify any type of application you would like to limit or stop (file sharing, chatting, downloading ..)
***Configuration Steps:***
1- create your time range in which these applications will be deined as show below
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>!&#8211; This timerange matches everyday from 9am to 5pm expcet weekends

time-range WEEKDAYS<br />
periodic ***weekdays ***9:00 to 17:00</td>
</tr>
</tbody>
</table>
2- Identify non-business applications using an ACL and attach the time-range to it. If you want to drop this traffic completely you can just attach this ACL to an interface.
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>!&#8211; Specify all types of traffic you need to limit

access-list 180 permit tcp any any eq ***www ***time-range ***WEEKDAYS***</td>
</tr>
</tbody>
</table>
3- Classify this traffic using class-map commands and configure your policy map to ***police ***this traffic to what ever suitable value may be 64Kbps or drop them as I am doing in the configuration below:
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>class-map match-all NON-WORK-APPS<br />
match access-group 180policy-map WORK-POLICY<br />
class NON-WORK-APPS<br />
drop</td>
</tr>
</tbody>
</table>
4- Apply the policy map to the router interface in the right direction.
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>int f0/0<br />
service-policy output WORK-POLICY</td>
</tr>
</tbody>
</table>
***Operation verfication:***
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>R1#show clock<br />
*** 10:03:59.183*** UTC ***Mon ***Jun 2 2008
!&#8211;Notice the ACL is active as the time is matching the time range.
R1#sh access-list 180<br />
Extended IP access list 180<br />
10 permit tcp any any eq www time-range WEEKDAYS ***(active) (4 matches)***
R1#sh policy-map int f0/0<br />
FastEthernet0/0
Service-policy output: WORK-POLICY
Class-map: WORK-APPS (match-all)<br />
*** 4 packets, 240 bytes***<br />
5 minute offered rate 0 bps, drop rate 0 bps<br />
Match: access-group 180<br />
drop
Class-map: class-default (match-any)<br />
69 packets, 6349 bytes<br />
5 minute offered rate 0 bps, drop rate 0 bps<br />
Match: any
!&#8211; ***using telnet to port 80 to test the configuration***
R1#telnet 192.168.12.2 80<br />
Trying 192.168.12.2, 80 &#8230;<br />
% ***Connection timed out***; remote host not responding
!&#8211; Notice the increment in the dropped number of packets
R1#sh policy-map int f0/0<br />
FastEthernet0/0
Service-policy output: WORK-POLICY
Class-map: WORK-APPS (match-all)<br />
*** 8 packets, 480 bytes***<br />
5 minute offered rate 0 bps, drop rate 0 bps<br />
Match: access-group 180<br />
drop
Class-map: class-default (match-any)<br />
80 packets, 7557 bytes<br />
5 minute offered rate 0 bps, drop rate 0 bps<br />
Match: any</td>
</tr>
</tbody>
</table>
***Now lets set the clock outside our defined time range to check the operation.***
<table style="border:1px solid gray; background-color: silver;" border="0">
<tbody>
<tr>
<td>R1#clock set ***18:0:0*** 2 june 2008
R1#show access-list 180<br />
Extended IP access list 180<br />
10 permit tcp any any eq www time-range WEEKDAYS ***(inactive) (8 matches)***
***!&#8211; telnet to port 80 succeeded***
R1#telnet 192.168.12.2 80<br />
Trying 192.168.12.2, 80 &#8230; ***Open ***</td>
</tr>
</tbody>
</table>
That was a basic example you can modify to suite your organization policy by changing any of the configuration parameters.
<br />