Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No. You can not use Squid for content filtering. You have to patch it with something like Squid Guard or Dans Guardian for that.
But there are other content filtering proxies like SafeSquid (http://freshmeat.net/projects/safesquid/) that can be used as proxy + web cache + content filtering. It also has a GUI interface for management. You can also forward request from SafeSquid to Squid.
who ever asked for content filtering??? you appear to just be advertising your own project, not answering the question at hand.
winxandlinx you can do exactly what you want very very simply with squid. there is no need whatsoever to use other tools in conjunction with it. you just want a dstdomain whitelist and permit everything in that whitelist and then follow up with a blanket deny after it.
acl whitelist dstdomain .google.com .mycompany.com
acl all src 0.0.0.0/0.0.0.0
http_access permit whitelist
http_access deny all
Last edited by acid_kewpie; 08-02-2007 at 04:59 AM.
who ever asked for content filtering??? you appear to just be advertising your own project, not answering the question at hand.
winxandlinx you can do exactly what you want very very simply with squid. there is no need whatsoever to use other tools in conjunction with it. you just want a dstdomain whitelist and permit everything in that whitelist and then follow up with a blanket deny after it.
acl whitelist dstdomain .google.com .mycompany.com
acl all src 0.0.0.0/0.0.0.0
http_access permit whitelist
http_access deny all
This is working. I implement in my network. This also work in RHEL 5.4.
acl whitelist dstdomain .google.com .mycompany.com
acl all src 0.0.0.0/0.0.0.0
http_access permit whitelist
http_access deny all
yes, but anybody could still visit https://www.facebook and other https sites. how to prevent this? I can't force users to use Proxy's, coz I want all control/management to be serverside only.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.