We need to go with option number 1.
Users have found a way around the content filter - using the ip address of the site. Since we now need to enter the ip address in as well as the website name, it is best if we learn to use the rules, etc. to block certain sites
Also, we don't want to advertise that were are blocking (as with the content filter), we just want them to think they can't get there.
We are using sonicwall pro 2040 with enhanced os version 4.
any further info would be helpful
thanks
Main Topics
Browse All Topics





by: dpk_walPosted on 2009-07-06 at 12:14:59ID: 24788306
This can be done in two ways:
1. Create specific policies which deny access to specific website from the internal network. and/PR
2. Use Security Services -> Content Filter to Restrict web features. HEre you add Forbidden domains. Also, you have options to disable all web traffic except for Allowed Domains.
For option 2 to work, the traffic must be strictly web traffic, if it is any traffic other than web traffic, for eg, P2P, messenger, etc, then option 2 would not work. It works for HTTPS traffic but only IP based rather than URL based.
Option 1 would always work irrespective of the port/protocol used to access the website(s) in question; however, you would need to provide an extensive list of public IP address for the websites and include all possible IPs when configuring the policy.
And, if a website is heavily mirrored, example www.yahoo.com, you would need to keep updating the policy with all the modifications as and when there are modifications to the mirror addresses [making the task cumbersome and very tough].
Please let know if you need more details.
Thank you.