From: Andi Kleen <ak@suse.de>
To: Claus Fischer <claus.fischer@clausfischer.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spoof protection with redundant routes
Date: 08 Apr 2002 22:23:23 +0200 [thread overview]
Message-ID: <p73d6xaos78.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20020408220215.A1987@clausfischer.com.suse.lists.linux.kernel>
Claus Fischer <claus.fischer@clausfischer.com> writes:
> - Is that known and by design?
Yes.
> - Is that the desired behaviour?
Yes.
> - Is there some possibility to change that?
You could define a multipath route with multiple nexthops (needs iproute2)
-Andi
next parent reply other threads:[~2002-04-08 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020408220215.A1987@clausfischer.com.suse.lists.linux.kernel>
2002-04-08 20:23 ` Andi Kleen [this message]
2002-04-08 20:02 Spoof protection with redundant routes Claus Fischer
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=p73d6xaos78.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=claus.fischer@clausfischer.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