Re: Load Balancing over several interfaces

> [snip]
> >
> >2. A deamon that plays with the routing entries based on network load.
> >If 128k link not saturated then use a default route that causes the
> >Squid machine to use the appropriate address, and if this is saturated
> >then change the routing table to use the other address.
> >
> >3. Similar to 2 but coded in Squid.
>
>
> the difficulty is this... the outgoing requests all go via the 2Mb link..
> the source IP dictates the return path.
> Thus, to alter the routing, one must change the outgoing address.
>
> Does anyone have any good ideas on implementation of such a daemon? If a
> patch could be written for something like this, then it would prove
> *very* popular in Australia, where Telstra Internet charge ridiculous
> prices for bandwidth.

I think a better way would be to have multiple tcp_outgoing_address
tags configured with a loading on each !

# Usage: tcp_outgoing_address address.favoured.by.one.isp 1
# Usage: tcp_outgoing_address address.favoured.by.another.isp 16

So for every 1 request sent bound as address.favoured.by.one.isp squid
would send 16 requests bound as address.favoured.by.another.isp.

That should load balance and should not be that hard to implement.
You would need an interface (looback ethernet alias/whatever) on the squid
to allow it to do that though.

------------------------------------------------------------------
Stephen Baxter SE Network Access/Big Networks Australia
phone : +61 8 8221 5221 222 Grote Street
fax : +61 8 8221 5220 Adelaide 5000, Australia
Received on Sun Oct 11 1998 - 15:17:12 MDT