From: Peter Hernberg <petehern@yahoo.com>
To: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Implementing an "on demand" routing protocol?
Date: Sun, 02 May 2004 21:56:09 -0400 [thread overview]
Message-ID: <1083549369.613.23.camel@mine> (raw)
I'm implementing the AODV routing protocol (RFC 3561) on Linux. One of
the protocol's salient features is being "on demand": rather than
receiving (and transmitting) regular updates on the topology of the
network, it waits until it needs a route to a given host (or network).
With AODV routing, in the following simple network
Host A <----> Host B <----> Host C,
it may be that A is unaware of its route to C. If A has a packet
destined for C, it buffers that packet and broadcasts a request for a
route to C.
Is there an interface whereby the kernel can be told "when you have a
packet, but lack a route to its destination, pass a message to this
daemon requesting a route and buffer that packet until the daemon is
done searching for route"? Any info would be appreciated.
--
Peter Hernberg
next reply other threads:[~2004-05-03 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 1:56 Peter Hernberg [this message]
2004-05-03 2:45 ` Implementing an "on demand" routing protocol? Kevin P. Fleming
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=1083549369.613.23.camel@mine \
--to=petehern@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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.