Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Adrian Chung <adrian@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath, 2.4.16 + Julian's patches.
Date: Fri, 14 Dec 2001 20:20:05 +0000	[thread overview]
Message-ID: <marc-lartc-100836130132038@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100831072321841@msgid-missing>

On Fri, Dec 14, 2001 at 07:33:25PM +0200, Julian Anastasov wrote:
> On Fri, 14 Dec 2001, Adrian Chung wrote:
[...]
> > And have the first link used fulltime, and the second (eth1) link only
> > used when the first is "dead".
> 
> 	You can mix a list of unipath or multipath routes into
> alternative routes, see my docs. One of the alternative routes is used
> until it fails. If you need different algorithm you have to create script
> to handle it.

Ah!  I obviously didn't pay close enough attention to the
documentation.  I'll give this a shot.

So, should I be able to do something like this (I'll test later):

ip route add default via aaa.bbb.ccc.ddd dev eth1 table 100
ip route add default via bbb.ccc.ddd.eee dev eth2 table 100

And eth1 will be used until failure?

> > Is "weight 0" used for anything right now, or even possible?
> 
> 	Weight 0 is not allowed, it will need changing too much code.
> If you can call ip route change, then you can call del+add and to
> apply the new routes.

Makes sense, and it's not necessary with your alternative routes
implementation.  I'll re-read the docs. :)

Thanks for the help.

BTW, any idea whether your patches are going to make it into 2.4
proper?

--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.enfusion-group.com] 3:16pm up 134 days, 7:15, 4 users


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

  parent reply	other threads:[~2001-12-14 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14  6:17 [LARTC] Multipath, 2.4.16 + Julian's patches Adrian Chung
2001-12-14 11:09 ` Christoph Simon
2001-12-14 11:45 ` Julian Anastasov
2001-12-14 15:00 ` Adrian Chung
2001-12-14 15:02 ` Adrian Chung
2001-12-14 15:09 ` Adrian Chung
2001-12-14 15:30 ` Christoph Simon
2001-12-14 15:52 ` Adrian Chung
2001-12-14 16:15 ` Christoph Simon
2001-12-14 17:08 ` Adrian Chung
2001-12-14 17:10 ` Adrian Chung
2001-12-14 17:33 ` Julian Anastasov
2001-12-14 20:20 ` Adrian Chung [this message]
2001-12-14 21:24 ` Julian Anastasov

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-100836130132038@msgid-missing \
    --to=adrian@enfusion-group.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox