From: Thomas Graf <tgraf@suug.ch>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: vnuorval@tcs.hut.fi, davem@davemloft.net, kim.nordlund@nokia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 13/13] [RFC] [IPV6] Fix source prefix routing problems when source address undefined.
Date: Tue, 17 Oct 2006 14:34:15 +0200 [thread overview]
Message-ID: <20061017123415.GO12964@postel.suug.ch> (raw)
In-Reply-To: <20061017.211730.51920084.yoshfuji@linux-ipv6.org>
* YOSHIFUJI Hideaki / ?$B5HF#1QL@ <yoshfuji@linux-ipv6.org> 2006-10-17 21:17
> In article <20061017113511.GN12964@postel.suug.ch> (at Tue, 17 Oct 2006 13:35:11 +0200), Thomas Graf <tgraf@suug.ch> says:
>
> :
> > different logic. In order to solve this, rules must be restricted to
> > one of these paths, i.e. a rule intending to make certain prefixes
> > unreachable may not apply to the source selection logic. This can be
> > achieved using the 'reason' field I proposed in my netconf slides, it
> > would allow turning the first rule example into
> >
> > rule add from 2001::1/128 for INPUT unreachable
> >
> > which would no longer apply when looking up the source address or
> > deciding the outgoing route.
>
> And/or, to take into account input interface, we could do
> rule add from 2001::1/128 in eth0 unreachable
> maybe.
Right, that works as well but duplicating the rule for every
interface is not very practical.
Anyways, the point is that the proposed change to modify the
source prefix matching logic is not acceptable and other way
has to be found.
next prev parent reply other threads:[~2006-10-17 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 0:27 [PATCH 13/13] [RFC] [IPV6] Fix source prefix routing problems when source address undefined Ville Nuorvala
2006-10-17 10:14 ` Thomas Graf
2006-10-17 11:00 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-17 11:35 ` Thomas Graf
2006-10-17 12:17 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-17 12:34 ` Thomas Graf [this message]
2006-10-17 16:49 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-17 20:11 ` Ville Nuorvala
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=20061017123415.GO12964@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=kim.nordlund@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=vnuorval@tcs.hut.fi \
--cc=yoshfuji@linux-ipv6.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).