Search squid archive

Re: Locking Proxy Chaining Down to a Specific Subnet

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

 



John Gardner wrote:
I wonder if anyone can point me in the correct direction of solving this
problem.

We are currently using two Squid (2.6) Caching Proxy Servers (CP1 and
CP2) on different sections of the network. The only way HTTP traffic can
get from one network to the other is via the proxy chained proxies. The
following works quite successfully;

acl redirect_to_live dstdomain server.local.net
cache_peer 10.0.0.45 parent 8080 3130 default no-query
cache_peer_access 10.0.0.45 allow redirect_to_live
never_direct allow redirect_to_live

This set of code sits on CP1 and anyone who tries get to
server.local.net gets chained to the CP2 proxy at 10.0.0.45 and the site
gets returned.

What we need now is a way to lock down this redirect to a specifc
subnet, I've tried adding

acl redirect_to_live src 192.168.10.0/24

but I get a syntax error, can anyone shed any light on how I could do
this?

http://wiki.squid-cache.org/SquidFaq/SquidAcl#Common_Mistakes

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


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

  Powered by Linux