I have a site with several squid servers setup as shown here http://wiki.squid-cache.org/Features/Tproxy4
All the Tproxy functionality is working fine. Now I would like to enable cache-peer sibling proxy-only to avoid duplication of objects between each server's hard drive. The servers sit in a dedicated subnet/vlan (router has "ip wccp redirect exclude in" on this subinterface ). If I enable cache_peer, I see that the ICP part works fine, but should server A try to fetch a HIT from server B, the connection fails because the source-ip is set to the client rather than server A. I end up with this type of thing in the cache.log 2009/09/19 17:53:09| Detected DEAD Sibling: cache03.<snipped> 2009/09/19 17:53:09| Detected REVIVED Sibling: cache03.<snipped> 2009/09/19 17:53:11| TCP connection to cache03.<snipped>/8080 failed 2009/09/19 17:53:11| Detected DEAD Sibling: cache03.<snipped> 2009/09/19 17:53:11| Detected REVIVED Sibling: cache03.<snipped> 2009/09/19 17:53:16| TCP connection to cache03.<snipped>/8080 failed 2009/09/19 17:53:16| Detected DEAD Sibling: cache03.<snipped> 2009/09/19 17:53:16| Detected REVIVED Sibling: cache03.<snipped> I guess we need to be able to disable the Tproxy functionality when talking to local cache_peers ? I see that Adrian Chadd made a patch for Squid v2 http://code.google.com/p/lusca-cache/issues/detail?id=48 I was wondering if there were any plans for such a feature to be added to Squid v3.1? Michael.
