From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pekkas@netcore.fi,
kaber@trash.net, yoshfuji@linux-ipv6.org
Subject: Re: [RFC] IPv6 route replacement
Date: Wed, 22 Jul 2009 20:09:10 +0900 [thread overview]
Message-ID: <4A66F356.3000803@linux-ipv6.org> (raw)
In-Reply-To: <20090722095040.GC3517@psychotron.englab.brq.redhat.com>
Hi,
Jiri Pirko wrote:
> Now do you think this is the right behaviour? I would expect the first route to
> be replaced. The same result is when you do "ip -6 route replace"
Well, even in IPv4 you cannot change metric;
same route can be installed e.g., for manual
backup route entry.
But well, NLM_F_REPLACE handler is completely
missing in IPv6. I think we are okay with
"replace" (NLM_F_CREATE|NLM_F_REPLACE) but we
could return "no such route" for "change"
(NLM_F_REPLACE).
--yoshfuji
prev parent reply other threads:[~2009-07-22 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 9:50 [RFC] IPv6 route replacement Jiri Pirko
2009-07-22 11:09 ` YOSHIFUJI Hideaki [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=4A66F356.3000803@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
/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).