From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Peter Hernberg <petehern@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Implementing an "on demand" routing protocol?
Date: Sun, 02 May 2004 19:45:49 -0700 [thread overview]
Message-ID: <4095B25D.2020607@backtobasicsmgmt.com> (raw)
In-Reply-To: <1083549369.613.23.camel@mine>
Peter Hernberg wrote:
> 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.
A starting point might be a daemon that listens on a tun interface, with
that interface being the target of a "default" route. The daemon can
then receive the packets, do what it likes with them, add routes to the
routing table, then reinject the packets back into the tun interface
once the route is in place.
prev parent reply other threads:[~2004-05-03 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 1:56 Implementing an "on demand" routing protocol? Peter Hernberg
2004-05-03 2:45 ` Kevin P. Fleming [this message]
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=4095B25D.2020607@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=petehern@yahoo.com \
/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