Rather
than blocking sites, try this one: (this is an effective for normal downloads
via http port)
Define the rule (on top of all the other
rules related with http, ftp services in your
rulebase);
source
destination
service
action
Any Any
http --> drop
The
crucial point is the service, you have to define a new http service with
resource, (here, named as )
xxx
will be defined from Resources -- New -- URI
In the
URI definition,
General Tab: Set name to anything (here, denoted
as xxx)
Check both Connection Methods: Transparent, Proxy
Choose Wild Cards in URI Match Specification Type
Match
Tab: Check Schemes: http, ftp, (these two must be checked...) and any
other (if required)
Check
Methods: GET
Host: *
Path: {*/*.mp3,*.mp3}
Query:
*
Action
Tab: Do not define or change anything, leave as default (you may change,
but since we're concerned with mp3 blocking, needn't have to be
changed)
Click
OK, Save everythg, and Install the policy.
Oh, by
the way, you can add this rule also as a secondary precaution (but not so
effective, since the IP' s of Napsters, etc, often change)
source
destination
service
action
Any NAPSTER-GROUP
Any
drop
In the
NAPSTER-GROUP, define these sites
64.124.41.0 (as
Network)
208.178.163.56
208.178.175.128
208.49.239.240
Hi ,
Have any one tried blocking MP3 downloads, if so
I would need which ports and sites that needs to blocked access. As majority
of internet bandwidth is being utilized for this.
Thanks in advance.
regs
sathish m r
|