Neil Watson wrote: > > I added a log to the default section of squidGaurd.conf as you suggested. Great! That should give us some information to work with.
> SquidGaurd.conf: <clipped> Your config file looks good. > As neil I attempt to have mozilla access a website via squid. > Squid access.log: <reformatted> > > 1033220088.802 28681 127.0.0.1 TCP_MISS/200 568 GET \ > http://slashdot.org/ neil DIRECT/216.138.221.7 image/png > 1033220091.358 41 127.0.0.1 TCP_MISS/200 568 GET | > http://slashdot.org/ neil DIRECT/216.138.221.7 image/png > > SquidGauard default.log: <reformatted> > > 2002-09-28 09:34:48 [20078] Request(default/none/-) \ > http://slashdot.org/ 127.0.0.1/- - GET > 2002-09-28 09:34:51 [20078] Request(default/none/-) | > http://slashdot.org/ 127.0.0.1/- - GET > > My requests are always redirected to the default deny policy. Why > is this? The reason that your request is being handled by the default acl is easily seen in the log file entry: 2002-09-28 09:34:48 [20078] pid handling the request Request Is always "request", AFAIK (default/none/-) (source group/destination group/-) http://slashdot.org/ full requested url 127.0.0.1 request received from this ip /- - /- ident GET http method squidGuard sees this request as coming from ip:127.0.0.1 / ident:-, and checks through the source definitions: src neil - must be ip:127.0.0.1 AND ident:neil - no match src lisamarie - must be ip:10.0.0.10/8 AND ident:lisamarie - no match So squidGuard processes the request as an unknown source, through the default acl. So why didn't squid include the ident information in the request sent to squidGuard? Are you running squid as a tranparent proxy? Ident and transparent don't get along too well together. You might want to also test from a different box to see if transparent proxy makes the ip show as 127.0.0.1 for everyone. Well, at least now you have some information to work with? Rick
