Re: [LARTC] Multipath, 2.4.16 + Julian's patches.

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux