From: klink@clouddancer.com (Colonel)
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: ethernet links should remember routes the same as addresses
Date: Thu, 29 Nov 2001 12:58:54 -0800 (PST) [thread overview]
Message-ID: <20011129205854.E4E187843A@phoenix.clouddancer.com> (raw)
In-Reply-To: <9u64q7$46m$1@phoenix.clouddancer.com>
In-Reply-To: <3C068ED1.D5E2F536@nortelnetworks.com> <9u64q7$46m$1@phoenix.clouddancer.com>
In clouddancer.list.kernel, you wrote:
>
>
>I just wanted to get some opinions on this for possible inclusion in 2.5.
>Alexey, if you have any comments...
>
>The scenario is as follows:
>
>Suppose I have a fancy routing setup, dynamically configured by different
>binaries, scripts, etc, complete with multiple addresses per link, additional
>routing rules and tables specified using iproute2, etc.
....
>Does this sound like a good idea? How hard would this be to implement (not
>knowing what the current code looks like, I don't know how this would be done)?
Most routing daemons handle your problem just fine. Perhaps you
should look into those daemons first, try 'bird' for instance.
--
Windows 2001: "I'm sorry Dave ... I'm afraid I can't do that."
next prev parent reply other threads:[~2001-11-29 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9u64q7$46m$1@phoenix.clouddancer.com>
2001-11-29 19:38 ` RFC: ethernet links should remember routes the same as addresses Christopher Friesen
2001-11-29 20:58 ` Colonel [this message]
[not found] <3C068ED1.D5E2F536@nortelnetworks.com.suse.lists.linux.kernel>
2001-11-29 19:55 ` Andi Kleen
2001-11-29 20:59 ` Christopher Friesen
2001-11-29 21:03 ` Ben Greear
2001-11-29 21:18 ` Christopher Friesen
2001-11-29 21:18 ` Andi Kleen
2001-11-29 23:04 Julian Anastasov
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=20011129205854.E4E187843A@phoenix.clouddancer.com \
--to=klink@clouddancer.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).