Extended Configuration Of Squidguard

28/01/2011

SquidGuard

SquidGuard
HOME Downloads Documentation Development Blacklists Contributions Contact

Extended Configuration of SquidGuard
There are several more options to configureSquidGuard according to your needs. Not allowing IP adresses Rules based on source IP adresses Regular Expressions Blocking against dns based blacklists Times Logging blocked access triesAuthentication

Documentation Installation Configuration
Getting started Destination ACLs Source ACLs Redirect Rule

Not allowing IP adresses To make sure that people don't bypass the URL filter by simplyusing the IP addresses instead of the fully qualified domain names, you can add the !in-addr following to your acl:
Disallowing access to IP addresses acl { default { pass !in-addr all redirecthttp://localhost/block.html } }

Time Constraints Authentication Regular Expressions Examples

Runtime Options About blocking Troubleshooting

Blocking against dns based blacklists

Known IssuesOther Sources Attention: This feature requires squidGuard 1.5 or later or the dnsbl patch for squidGuard 1.4 provided by INL - http://www.inl.fr/. If you want to use external dns based blacklists suchas black.uribl.com for blocking you can use !dnsbl to dynamically check domain names against such services:
Using external dns based blacklists acl { default { pass!dnsbl:your.preferred.blacklist.domain.com all redirect http://localhost/block.html } }

If you use !dnsbl without specifying a domain, black.uribl.com is used as default.
squidguard.org/Doc/extended.html 1/3

28/01/2011SquidGuard

Be aware that this will raise several DNS requests every time squidGuard receives a request to filter. SquidGuard will not cache any DNS result, so make sure your DNS server does, andmeasure the performance impact before using this feature in production. Blocking based on times There are two ways to define times and dates where access to websites are allowed or disallowed. The weekly...