Problems with parent proxy using squid 2.3 STABLE 2

Squid gurus,

> Here is a configuration I have (hopefully the ascii art looks okay) to
> help illustrate a couple of problems I am having with parent proxy
> configurations:
>
>
> |
> | (206.207.117.145)
> -------------------
> | linux 1 |
> -------------------
> | (192.168.2.100)
> |
> ------------------------------
> | |
> | (192.168.2.10) | (192.168.2.11)
> --------------- -------------
> | linux 2 | | PC1 |
> --------------- --------------
> | (192.168.1.1)
> |
> | (192.168.1.10)
> ---------------
> | PC2 |
> ---------------
>
>
> Given the above configuration, I am having a couple of problems with squid
> (2.3 Stable 2), which I don't believe existed in squid 2.1 PATCH 2.
>
> 1) If linux 2 is configured in proxy mode (port 5000) and linux 2 is set
> to use linux 1 as a parent proxy (port 5001), linux 2 will always send
> requests to linux 1 on port 80 instead of parent proxy port (5001). Squid
> running on Linux 1 will not see this request as it comes in on the wrong
> port. Here is my line in squid.conf on linux 2:
>
> cache_peer 192.168.2.100 parent 5001 0 no-query default long=test:test
>
> In this configuration, a browser configured to talk on port 5001 running
> on PC1 can browse the Internet fine.
>
> 2) If linux 2 is configured in transparent proxy mode, the linux 2 ACL
> allow list doesn't work IF linux 2 is configured to use linux 1 as a
> parent proxy. All requests get the ACL deny page. The deny list works in
> this configuration.
>
> Thanks for any help,
>
> Eric Nelson
> ericn@extendsys.com
Received on Thu May 11 2000 - 10:56:32 MDT