[LARTC] Load balancing on multiple NICs with iproute
bert hubert ahu@ds9a.nl
Sat, 17 Mar 2001 12:45:43 +0100
Previous message: [LARTC] Load balancing on multiple NICs with iproute
Next message: [LARTC] Load balancing on multiple NICs with iproute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--------------------------------------------------------------------------------
On Fri, Mar 16, 2001 at 09:06:18PM -0500, Scott Russell wrote:
> I'm using DNS to do cheap and easy round robin style connections to the box.
>
> [scottrus@linux scottrus]$ host ftp3.linux.ibm.com
> ftp3.linux.ibm.com has address 9.37.145.124
> ftp3.linux.ibm.com has address 9.37.145.120
> ftp3.linux.ibm.com has address 9.37.145.127
DNS is wildly underestimated as a loadbalancing/distribution device. It
works very well, especially if you set your TTL pretty low.
> 1) Incoming requests are responded to on the same interface they came in on.
> For example an ftp connection coming in on tr1 has all TX / RX packets stick
> to tr1.
This is possible, I think.
> As you can see I've tried simply adding default routes for each token ring
> interface and I think this is a step in the right direction but I'm missing
> something.
Add source routing, as described in
http://ds9a.nl/2.4Routing/HOWTO//cvs/2.4routing/output/2.4routing-4.html#ss4.1
Route packets with a source of 9.37.145.124 to trX, .120 to trY and 127 to
trZ.
> Any help would be great. Examples would be better of course. Thanks much!
# ip rule add from 9.37.145.124 table 124
# ip rule add from 9.37.145.120 table 120
# ip rule add from 9.37.145.127 table 127
# ip route add default via 9.37.145.1 dev tr0 table 124
# ip route add default via 9.37.145.1 dev tr1 table 120
# ip route add default via 9.37.145.1 dev tr2 table 127
# ip route flush cache
Something like that should work. I messed up the ip addresses I think, but
hey :-)
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
댓글