From: David Miller <davem@davemloft.net>
To: sahne@0x90.at
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ipv6: ignore looped-back NA while dad is running
Date: Fri, 15 Apr 2011 15:44:57 -0700 (PDT) [thread overview]
Message-ID: <20110415.154457.28809247.davem@davemloft.net> (raw)
In-Reply-To: <20110414070925.GA78446@0x90.at>
From: Daniel Walter <sahne@0x90.at>
Date: Thu, 14 Apr 2011 09:09:25 +0200
> [ipv6] Ignore looped-back NAs while in Duplicate Address Detection
>
> If we send an unsolicited NA shortly after bringing up an
> IPv6 address, the duplicate address detection algorithm
> fails and the ip stays in tentative mode forever.
> This is due a missing check if the NA is looped-back to us.
>
> Signed-off-by: Daniel Walter <dwalter@barracuda.com>
Applied to net-next-2.6
next prev parent reply other threads:[~2011-04-15 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 7:09 [PATCH 1/1] ipv6: ignore looped-back NA while dad is running Daniel Walter
2011-04-15 22:44 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-13 15:02 Daniel Walter
2011-04-13 21:30 ` David Miller
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=20110415.154457.28809247.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sahne@0x90.at \
/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).