All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Load balancing on multiple NICs with iproute
Date: Sat, 17 Mar 2001 11:45:43 +0000	[thread overview]
Message-ID: <marc-lartc-98482961726373@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98479481719835@msgid-missing>

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

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-03-17 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-17  2:06 [LARTC] Load balancing on multiple NICs with iproute Scott Russell
2001-03-17 11:45 ` bert hubert [this message]
2001-03-18 22:05 ` Scott Russell
2001-03-19 12:40 ` Arthur van Leeuwen
2001-03-20  4:43 ` Scott Russell
2001-03-20  9:24 ` Arthur van Leeuwen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-98482961726373@msgid-missing \
    --to=ahu@ds9a.nl \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.