From: Hannes Frederic Sowa <hannes@stressinduktion•org>
To: Duan Jiong <duanj.fnst@cn•fujitsu.com>
Cc: David Miller <davem@davemloft•net>, netdev@vger•kernel.org
Subject: Re: [PATCH] ipv6: match those routes that have different metirc
Date: Mon, 11 Nov 2013 07:07:53 +0100 [thread overview]
Message-ID: <20131111060753.GA27030@order.stressinduktion.org> (raw)
In-Reply-To: <52804865.8090206@cn.fujitsu.com>
On Mon, Nov 11, 2013 at 11:00:53AM +0800, Duan Jiong wrote:
> Now the kernel only match those routes that have the same
> metirc, so if those routes are non-reachable, then the packets
> can't be sent out.
>
> But according to the rfc 4191 section 3.2, if the best route
> points to a non-reachable route, the next best route should be
> consulted. So the kernel should not only match those routes that
> have minimum metric, and should also match others.
I am not so keen on chaning how metrics get handled. Please note that
metrics are a pure linux-centric concept and are not standardized. I bet
some people depend on how these work and have the same semantic as IPv4
ones because they use the same code in their routing daemon backends.
Also, I think it is better targetted for net-next, which is currently closed.
So we have some time to discuss. ;)
Greetings,
Hannes
next prev parent reply other threads:[~2013-11-11 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 3:00 [PATCH] ipv6: match those routes that have different metirc Duan Jiong
2013-11-11 6:07 ` Hannes Frederic Sowa [this message]
2013-11-11 7:16 ` Duan Jiong
2013-11-11 7:39 ` Hannes Frederic Sowa
2013-11-11 8:29 ` Duan Jiong
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=20131111060753.GA27030@order.stressinduktion.org \
--to=hannes@stressinduktion$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=duanj.fnst@cn$(echo .)fujitsu.com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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