If you don't bind Squid to a specific address you should be able to
solve this with routing, allowing Squid to pick the address of the
interface it went out on.
The default operation is not to bind to a specific address.
(tcp_outgoing_address).
-- Henrik Nordstrom Squid hacker Jeremy wrote: > > Hi, > > I have a setup using eql to load share outgoing traffic using two dial-up > modems. This is running on a RedHat 6.2 system > > I want to use both of the modems for receiving upstream data. I do not have > the cooperation of the ISP for this. > > eql allows balancing of the outgoing requests, but the source address is > fixed as the address that squid is bound to. This means that all replies to > squid come in on the one modem, irrespective of which modem the request went > out on. > > I want to bind more than one copy of squid on the same machine to different > virtual IP's. I can then arrange routing so that one copy of squid gets > return traffic through one modem and the other copy gets return traffic from > the other modem. I then assume I can make the copies to be peers of each > other and so achieve an overall balance in the modem usage. > > Can anyone advise if : > > 1. Squid can be bound to a specific IP on a machine - for upstream requests? > 2. Multiple copies of squid can coexist? > 3. Multiple copies of squid on a machine can act as cache peers? > > JeremyReceived on Tue Apr 03 2001 - 13:00:47 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:59:08 MST