I definitely don't recommend doing it based on time as below.
You can add routing table entries that split your traffic
approximately according to the bandwidth available. Ie, something like:
route add default main_gateway
route add net 192.0.0.0 mask 240.0.0.0 secondary_gateway
You may have to try different routes and add many of them to get the
balance right.
> > My bandwidth 'supply' is as follows:
> > 2Mb Link (main feed, fast but expensive)
> > 128k Simplex satellite link (secondary feed, cheap, but cannot
> > handle much)
> >
> > Is there any way in which squid can be made to use one outgoing IP
> > address until the 128k link is saturated, and then use another outgoing
> > IP for requests over that saturation point?
> >
> > Does anyone have any ideas for implementing something like this?
>
>
> ifconfig eth0 1.2.3.4 # via telstra
> ifconfig eth0:1 2.3.4.5 # via bird
>
> #
> # Put 2/3rds of traffic via bird.
>
> while sleep 1 ; do
> route add default gw 1.2.3.5 # address of gateway router
> sleep 2
> route add default gw 2.3.4.6 # secondary address of same
> # router.
> done
>
> The source address will be the IP address of the interface the packets
> will be routed out. If the packets are routed via an aliased interface
> then they'll use that IP number. So just keep flipping the default
> route to suit.
>
> Michael.
>
Received on Thu Oct 15 1998 - 06:52:05 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:30 MST