Subject: Re: down interfaces, link detection, and connected routes
To: Pavel Cahyna <email@example.com>
From: David Young <firstname.lastname@example.org>
Date: 01/18/2005 13:30:19
On Tue, Jan 18, 2005 at 10:01:56AM +0100, Pavel Cahyna wrote:
> On Mon, 17 Jan 2005 20:27:46 -0600, David Young wrote:
> > FWIW, I have improved [*] the RADIX_MPATH patches from KAME.net.
> > RADIX_MPATH most famously lets us store more than one nexthop for a
> > single destination prefix; it chooses the nexthop to use by hashing
> > the source/destination pair; for better or worse, the forwarding
> > decision is cached "in the usual way." I have added a hook to
> > RADIX_MPATH for "weighting" routes [**], made it possible to keep both
> > RTF_GATEWAY/RTF_LLINFO information (indirect/direct route) for a single
> > destination, and added a "wireless" forwarding heuristic [***].
> > Dave
> > * They're "improved" except for the bugs. I ahd to cut the project
> > loose shortly after the FIB code started to make sense, FSVO of
> > "make sense." [****]
> Please, what is the FIB code? Also, are your patches publicly available?
Forwarding Information Base, another term for the routing table.
I have put the patches at
David Young OJC Technologies
email@example.com Urbana, IL * (217) 278-3933