|
Just to inform that this problem is now fixed.
In case anyone has the same problem I thought it would good to post the
solution.
I'm running squid and squidguard on Centos 4.1 and it seems that selinux was
enabled preventing squidguard from reading its DB files.
Thanks to all those who tried to help.
Tony
> -----Original Message-----
> From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:lvs-users-
> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Horms
> Sent: 14 October 2005 02:48
> To: LinuxVirtualServer.org users mailing list.
> Subject: Re: lvs + squid + squidguard
>
> On Thu, Oct 13, 2005 at 04:00:30PM +0100, Tony Spencer wrote:
>
> [snip, snip, snip,...]
>
> > > > You are correct that I'm running LVS-NAT.
> > > > I'm a little lost on your reply though.
> > > > Are you speaking about the SquidGuard rules or the LVS rules??
> > >
> > > SquidGuard. It's just a guess.
> >
> > SquidGuard has no IP rules.
> > It just blocks certain domains/urls listed in a db file.
>
> All that LVS-NAT should be doing is changing the destination IP address
> in the IP header of the packet from the VIP to the appropriate RIP. It
> does not mangle the data section of the packet.
>
> I guess Squidgaurd must be using the IP address that
> a connection is made to as part of its test somewhere.
>
> Perhaps its as simple as telling squidguard to act on
> connections to the RIP instead of (or as well as if you like)
> the VIP. But I am really just guessing at this point.
>
> --
> Horms
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
