Thanks Mark, I read the document but did not understand the very well. Could you please tell me the what would be ACL for redirecting traffic of 192.168.0.10 to 192.168.0.3 Thanks --- Mark Elsen <mark.elsen@xxxxxxxxx> wrote: > > Dear all, > > > > I have two squid proxy servers and two ISP > > > > 1) 192.168.0.1 running on port 3128 > > 2) 192.168.0.3 running on port 3128 > > > > We have around 70 comps assigned IP's between > > 192.168.0.4 to 192.168.0.250 > > The default proxy we are using is 192.168.0.1 > which is > > on the ISP 1. > > Now I have configured 192.168.0.3 squid proxy > server > > on ISP 2 line. > > Both ISP 1 and ISP 2 are landing (connected) on > the > > same Switch. > > > > Now I want to setup users from IP range > (192.168.0.4 > > to 192.168.0.50) to use this 192.168.0.1 proxy > server > > And for others 192.168.0.3. If others from IP > range > > (192.168.0.50 to 192.168.0.250) are trying to > access > > 192.168.0.1 the request will forward to > 192.168.0.3 > > proxy server. > > On all machines I have setup the proxy settings as > > 192.168.0.1:3128. > > I don't want to change there proxy settings in > > browser. The request will invisibly forward to > > 192.168.0.3. > > > > - Check the cache_peer_access directive in > squid.conf.default > (read all the comments) > > M. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
