From: David Miller <davem@davemloft.net>
To: brian.haley@hp.com
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, dlstevens@us.ibm.com
Subject: Re: [IPv6] Fix ICMPv6 redirect handling with target multicast address, try 3
Date: Mon, 08 Oct 2007 00:12:53 -0700 (PDT) [thread overview]
Message-ID: <20071008.001253.26300247.davem@davemloft.net> (raw)
In-Reply-To: <4703AAC1.3040500@hp.com>
From: Brian Haley <brian.haley@hp.com>
Date: Wed, 03 Oct 2007 10:44:17 -0400
> When the ICMPv6 Target address is multicast, Linux processes the
> redirect instead of dropping it. The problem is in this code in
> ndisc_redirect_rcv():
>
> if (ipv6_addr_equal(dest, target)) {
> on_link = 1;
> } else if (!(ipv6_addr_type(target) & IPV6_ADDR_LINKLOCAL)) {
> ND_PRINTK2(KERN_WARNING
> "ICMPv6 Redirect: target address is not
> link-local.\n");
> return;
> }
>
> This second check will succeed if the Target address is, for example,
> FF02::1 because it has link-local scope. Instead, it should be checking
> if it's a unicast link-local address, as stated in RFC 2461/4861 Section
> 8.1:
>
> - The ICMP Target Address is either a link-local address (when
> redirected to a router) or the same as the ICMP Destination
> Address (when redirected to the on-link destination).
>
> I know this doesn't explicitly say unicast link-local address, but it's
> implied.
>
> This bug is preventing Linux kernels from achieving IPv6 Logo Phase II
> certification because of a recent error that was found in the TAHI test
> suite - Neighbor Disovery suite test 206 (v6LC.2.3.6_G) had the
> multicast address in the Destination field instead of Target field, so
> we were passing the test. This won't be the case anymore.
>
> The patch below fixes this problem, and also fixes ndisc_send_redirect()
> to not send an invalid redirect with a multicast address in the Target
> field. I re-ran the TAHI Neighbor Discovery section to make sure Linux
> passes all 245 tests now.
>
> Signed-off-by: Brian Haley <brian.haley@hp.com>
> Acked-by: David L Stevens <dlstevens@us.ibm.com>
I believe everyone's concerns have been addressed in this
version of the patch, so I have applied it to net-2.6
Thanks everyone!
prev parent reply other threads:[~2007-10-08 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 16:26 [IPV6] Fix ICMPv6 redirect handling with target multicast address Brian Haley
2007-09-29 0:50 ` David Stevens
2007-09-29 1:04 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-01 3:27 ` Brian Haley
2007-10-01 11:49 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-01 17:36 ` Brian Haley
2007-10-02 19:18 ` [IPv6] " Brian Haley
2007-10-02 20:39 ` David Stevens
2007-10-02 21:06 ` Brian Haley
2007-10-02 22:41 ` David Stevens
2007-10-03 14:44 ` [IPv6] Fix ICMPv6 redirect handling with target multicast address, try 3 Brian Haley
2007-10-08 7:12 ` 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=20071008.001253.26300247.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brian.haley@hp.com \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--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).