> if anyone can figure out why it is not blocking he can send me a 
> reply

Alex is correct about the database versions, but I see a couple of
other problems, and I'm worried that there may be more.

squidGuard does not "block" a url, it "redirect" the request to
somewhere else.  Squid sends the request to squidGuard and squidGuard 
either returns a blank line (approved), or a new url for Squid to 
retrieve (redirecting to the new url).  Your config file does not 
contain a redirect statement, thus making it impossible for squidGuard
to redirect. 

Your acl statements should end with either "none" or "all".

Is squidGuard writing to its logfile? (squidGuard.log)  You should
see a bunch of entries there every time you start and stop squidGuard.
Then you should check that logfile whenever squidGuard is not
doing what it should be doing.  Many times your answer will be there
in the logfile.

Rick





> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Alex Harrington
> Sent: Monday, March 24, 2003 10:31 AM
> To: [EMAIL PROTECTED]
> Subject: RE: squid guard is not blocking
> 
> 
> > Please post your squidGuard.conf file and let us know what revision of
> > BerkelyDB you have compiled squidGuard with...
> 
> Mostafa sent me this:
> 
> BEGIN QUOTE--
> this is the output of squidGuard -v:
> 
> SquidGuard: 1.2.0 Sleepycat Software: Berkeley DB 4.0.14: (November 18,
> 2001)
> 
> and this is a copy of my conf file:
> 
> logdir /usr/local/squidGuard/log
> dbhome /usr/local/squidGuard/db
> 
> 
> 
> source new {
>       ip              172.16.3.0/24
> }
> 
> destination bl_proxy {
>            domainlist  proxy/domains
> }
> 
> destination bad {
>       domainlist      bad.destdomainlist
> }
> 
> 
> acl {
>       new {
>               pass !bl_proxy !bad
>       }
> 
>     default {
>               pass !bl_proxy !bad
>     }
> }
> 
> if anyone can figure out why it is not blocking he can send me a reply
> 
> END QUOTE--
> 
> If you're using .db files, you need to recompile squidGuard with BerkelyDB
> 3.2.9 - no other version will do. Alternativly, delete the .db files and run
> from the text files (ie do not run squidGuard -C all)
> 
> HTH
> 
> Alex
> 
> 

Reply via email to