Search squid archive

Re: TProxy + cache_peer parent

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

 



On Fri, 15 Oct 2010 14:47:48 -0300, Alex Montoanelli
<alexmontoanelli@xxxxxxxxx> wrote:
> Hello everyone,
> 
> I have a box with Squid + WCCP + tproxy working well, they have two
> squid process running.
> One is the frontend registered in WCCP, serving small files from RAM
> without disk cache, and another is a backend, not registered on WCCP,
> used for large files cached on disk as father of the frontend.
> 
> When a request comes in the frontend and it makes the request to the
> destination, the client ip is what arrives at the destination, but
> when the frontend forwards the request to the backend (based on
> cache_peer_access), IP arrives at the destination is no longer the
> client, but the IP of the squid.
> My question is, is there a way from a request reach the destination
> forwarded by parent cache with the IP address of the original the
> customer ?

Squid-3.1 will happily spoof its client IP to peers. Behind WCCP this
seems to lead to routing problems on the return paths.

Squid-3.2 allows Squid to process the XFF header passed between proxies
and spoof the origin client IP only on direct external connections.

Amos



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

  Powered by Linux