Re: [squid-users] Trouble with transp proxy and always_direct clause

Are you sure you have understood the effect of putting always_direct in
squid.conf?

This directive will make Squid go direct to the requested source,
ignoring any cache peers you have. The traffic will however still be
intercepted by your TCP redirection rules. You cannot control what is
being intercepted by changing the Squid configuration as Squid has no
control over this. Interception is done by your TCP/IP configuration
and/or router.

Most likely, what you actually want is to exclude your local servers
from the TCP redirection rules, to cause your clients to go directly to
the local servers without being intercepted by Squid.

Regards
Henrik Nordström
Squid Hacker

Lutz Maibach wrote:
>
> Hi,
>
> I'm using Squid 2.2 / Stable 5 with SuSE Linux 6.4. I configured
> transparent proxy a few weeks ago and everything seemed to work right
> except the access to our local server-adresses where I got an "access
> denied". After inserting a always_direct clause for the local
> addresses this worked too. Today I discovered that transp. proxying
> wasn't started when I rebooted the server the last time.
>
> After rebooting the server again with the right (transp. proxy
> enabled) kernel everything seemed to work right again except....yes,
> except the local server-addresses. Cause I haven't changed anything in
> squid.conf since my first successfull test I don't know what to do to
> get a direct access to my local servers. Now I get a access denied no
> matter whether access_direct is activated or not. No error is shown
> when I reload the squid.conf
>
> My entries are shown above:
> acl myserver src 192.168.50.0/24
> always_direct allow myserver
>
> Does anybody know what I have done wrong?
>
> Greetings
>
> Lutz Maibach
Received on Mon Oct 01 2001 - 13:49:20 MDT