AODV RFC is now ratified

[Bruce M Simpson]

On Tue, Jul 08, 2003 at 08:13:03AM -0600, M. Warner Losh wrote:
> Cool!  Hopefully this work will include fixing lucent cards too :-)

Hail Eris. All hail Discordia.

By the way, have you seen RFC 3561? It's just out.

http://www.faqs.org/rfcs/rfc3561.html
Ad hoc On-Demand Distance Vector (AODV) Routing

I'm putting together a brief FreeBSD HOWTO -- 'On-demand Routing with
XRESOLVE for Dummies' -- hinted at by fenestro. My technique is quite
simple, I create a CLONE+XRESOLVE route pointing to disc0 (to avoid
routing loops when ip forwarding is enabled) for the route(s) intended
to use the wireless cloud as a next-hop, then listen for RTM_RESOLVE
messages when the stack tries to use those route entries to clone routes
from. That then enables our hypothetical aodvd to issue RTM_CHANGE to
route the data to its peer. Seems pretty clean.

We can of course tweak the net.inet.ip.rt* cache tunables to prevent
the stack getting swamped with stale wireless routes.

I may not be able to get AODV all done on my own, but I may have a crack
at it - have a lot on my plate just now.

BMS