From: David Miller <davem@davemloft.net>
To: infrastation@yandex.ru
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: fix RTPROT_RA markup of RA routes w/nexthops
Date: Mon, 16 Jul 2012 22:56:11 -0700 (PDT) [thread overview]
Message-ID: <20120716.225611.1570342975310166446.davem@davemloft.net> (raw)
In-Reply-To: <20120710184550.7a5a8d89802473b4c28d07bf@yandex.ru>
From: Denis Ovsienko <infrastation@yandex.ru>
Date: Tue, 10 Jul 2012 18:45:50 +0400
> From: Denis Ovsienko <infrastation@yandex.ru>
>
> Userspace implementations of network routing protocols sometimes need to
> tell RA-originated IPv6 routes from other kernel routes to make proper
> routing decisions. This makes most sense for RA routes with nexthops,
> namely, default routes and Route Information routes.
>
> The intended mean of preserving RA route origin in a netlink message is
> through indicating RTPROT_RA as protocol code. Function rt6_fill_node()
> tried to do that for default routes, but its test condition was taken
> wrong. This change is modeled after the original mailing list posting
> by Jeff Haran. It fixes the test condition for default route case and
> sets the same behaviour for Route Information case (both types use
> nexthops). Handling of the 3rd RA route type, Prefix Information, is
> left unchanged, as it stands for interface connected routes (without
> nexthops).
>
> Signed-off-by: Denis Ovsienko <infrastation@yandex.ru>
Applied to net-next, thanks.
prev parent reply other threads:[~2012-07-17 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 7:37 [PATCH] fix RTPROT_RA markup of some RA routes in netlink Denis Ovsienko
2012-07-09 21:40 ` David Miller
2012-07-10 14:45 ` [PATCH] ipv6: fix RTPROT_RA markup of RA routes w/nexthops Denis Ovsienko
2012-07-17 5:56 ` David Miller [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=20120716.225611.1570342975310166446.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=infrastation@yandex.ru \
--cc=netdev@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).