Search squid archive

Re: squid 3 and cache peer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 14/09/11 16:38, Ankit Sagwekar wrote:
i have one proxy server base on centos 6.0 which come with squid 3.1.4

server have two LAN ip address eth0 192.168.0.35
eth0:1 192.168.0.34
eth1 XXX.XXX.XXX.XXX WAN IP

i want to forward request to other proxy which is on internet (WAN IP)

so i create rule that if some proxy traffic come to ip 192.168.0.34 from
internal network it get forward to wan proxy

if i get request to 192.168.0.35 from internal network. it process from
local proxy which is on same server


i add this line in my squid.conf in squid 3.1.4 for this

http_port 3128
http_port 192.168.0.34:3120
acl external myip 192.168.0.34

cache_peer 173.208.xxx.xxx parent 25981 0 no-query no-digest
cache_peer_access 173.208.xxx.xxx allow external

this rule work fine on squid 2.7 but not work in squid 3-3.1

anybody have any idea what's wrong with this ?

i already check iptables so it's not firewall problem


Are you doing traffic interception on that 192.168.0.34:3120 port? Squid-2 had a bug which meant it saw the Squid IP as the "myip" value. When the actual "myip" value should have been the clients original destination IP.

If you can please try 3.1.15 and see if it works (note: ACL name changed to localip around 3.1.13). I think we fixed the my* bugs but can't find the exact patch right now to see what versions.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.15
  Beta testers wanted for 3.2.0.11


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux