> the only thing wrong that I see here is the acl rule.

squidGuard won't redirect without a redirect statement.



> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Matthew Trey
> Sent: Monday, March 01, 2004 12:01 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Not blocking
> 
> 
> ok lets back up here.. from a few posts back this was the config:
> 
> dbhome /usr/share/squidGuard-1.2.0/db
> logdir /var/log/squidGuard
> 
> destination bl_audio-video {
>         domainlist audio-video/domains
>         urllist audio-video/urls
> }
> 
> destination bl_porn {
>      domainlist porn/domains
>          urllist porn/urls
> }
> 
> acl {
> 
>     default {
>         block    !bl_audo-video  !bl_porn
>     }
> }
> 
> the only thing wrong that I see here is the acl rule. change it to
> pass !bl_audo-video !bl_porn all
> 
> then your config is 100% ok
> yes, leave in the all.. It works just fine, its what I use.
> 
> now ... restart squid altogether.. squid will start squidGuard up and make
> it reread its config.
> 
> wherever your logfile for SQUIDGUARD exists.. go there.. and make sure
> squidGuard is NOT in emergency mode.. if you have anything wrong with your
> config, or missing files, etc... squidguard will just pass everything
> (Really I think it should default to passing nothing, but I did'nt write it
> so I don't get a say.)
> 
> if squidGuard is up and running but still passing the traffic, then we can
> reasonably assume the problem is not squidGuard at all, but a
> misconfiguration of squid (squid may not be using the redirector at all)
> 
> 
> 

Reply via email to