> Thanks for your help.  Alas no luck. 

What's luck got to do with it? ;-)

> The ads.log and the porn.log are never written to. 

If squidGuard *tried* to write to them and couldn't there would be
errors in squidGuard.log. If the squidGuard log is *empty* that's
bad, too, since squidGuard writes good and bad notifications to the 
log. Have you checked squidGuard.log?

> I gather that squid and squidguard never look up the id of the user
> at the browser.  Any suggestions.

No need to guess... what is squid logging in access.log? You have to
trace this down, step by step. You may find that squid had the 
information and didn't send it to squidGuard, or something totally
different.

Here's an entry from my squid log... I discarded the first 15 or so
characters and here's the rest:
192.168.44.3 TCP_MISS/200 1550 GET http://www.google.com/ rick DIRECT/216.239.51.101 
text/html
(the entry was not wrapped in the log)

That log entry shows that squid saw it as being from 192.168.44.3 and 
the ident was "rick".

Let me know what squud is logging.

Rick



> 
> Neil Watson wrote:
> > I've been trying to make squid and squiguard play nice for hours.
> > Squid works fine on its own. I've installed squidguard to filter
> > adult content. Squidguard never idents the user and therefore uses
> > the default rule of deny.
> 
> 
> Rick Mathews wrote:
> I can help you get there. Make the changes to your config file
> 
> that are marked below:
> 
> > logdir /usr/local/squidGuard/log
> > dbhome /usr/local/squidGuard/db
> >
> 
> > src neil {
> >     ip   10.0.0.10
> >     user   neil
> > }
> >
> 
> > dest porn {
> >     domainlist                porn/domains
> >     urllist           porn/urls
> 
> 
> 
> add>    logfile         porn.log
> add>    redirect                http://webserver/images/title.php?size=15&text=denied
> 
> 
> > }
> >
> 
> > dest ads {
> >     domainlist                ads/domains
> >     urllist           ads/urls
> 
> 
> 
> add>    expressionlist  ads.expressions         # see attached
> add>    logfile         ads.log
> add>    redirect                http://webserver/images/1x1.gif # see attached
> 
> 
> > }
> > acl {
> >     neil {
> >         pass !ads !porn all
> >     }
> >
> 
> >     default {
> >         pass none
> >         redirect http://webserver/images/title.php?size=15&text=denied
> >     }
> > }
> 
> 
> 
> Create:
> /usr/local/squidGuard/log/porn.log
> /usr/local/squidGuard/log/ads.log
> Give them the same ownership and permissions as squidGuard.log.
> 
> 
> - Make the config changes above and issue 'squid -k reconfigure'.
> - Check the messages in squidGuard.log for errors.
> - Enter a known-blocked porn url in your browser and hit enter.
> - The last (or one of the last) entries in squid's access.log will show
> the request, along with squid's understanding of your ip and ident.
> - The last entry in /usr/local/squidGuard/log/porn.log will show how
> squidGuard handled the request, including the ip and ident received
> from squid, and the source group and destination group from your
> squidGuard.conf file.
> 
> 
> -- 
> Neil Watson
> Network Administrator
> watson-wilson.ca
> 
> 

Reply via email to