From: Brian Haley <brian.haley@hp.com>
To: Jens Rosenboom <jens@mcbone.net>
Cc: Linux Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] ipv6: Log the explicit address that triggered DAD failure
Date: Wed, 12 Aug 2009 21:33:36 -0400 [thread overview]
Message-ID: <4A836D70.1040702@hp.com> (raw)
In-Reply-To: <1250089107.6641.36.camel@fnki-nb00130>
Jens Rosenboom wrote:
> If an interface has multiple addresses, the current message for DAD
> failure isn't really helpful, so this patch adds the address itself to
> the printk.
>
> Signed-off-by: Jens Rosenboom <jens@mcbone.net>
>
> ---
>
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index 43b3c9f..01a4b25 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -1403,8 +1403,8 @@ void addrconf_dad_failure(struct inet6_ifaddr
> *ifp)
> struct inet6_dev *idev = ifp->idev;
>
> if (net_ratelimit())
> - printk(KERN_INFO "%s: IPv6 duplicate address detected!\n",
> - ifp->idev->dev->name);
> + printk(KERN_INFO "%s: IPv6 duplicate address %pI6 detected!\n",
> + ifp->idev->dev->name, &ifp->addr);
>
> if (idev->cnf.accept_dad > 1 && !idev->cnf.disable_ipv6) {
> struct in6_addr addr;
I have no problem with this patch, I should have done this when I
last changed this code.
The other thing I've come across that is similar to this is the
issue that when DAD fails, /sbin/ip doesn't show that it did,
the address just stays in a tentative state forever:
inet6 dead:beef::1/64 scope global tentative
valid_lft forever preferred_lft forever
Does anyone have an issue of adding a "dadfailed" flag to make
this more obvious:
inet6 dead:beef::1/64 scope global tentative dadfailed
valid_lft forever preferred_lft forever
-Brian
next prev parent reply other threads:[~2009-08-13 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 14:58 [PATCH] ipv6: Log the explicit address that triggered DAD failure Jens Rosenboom
2009-08-13 1:33 ` Brian Haley [this message]
2009-08-13 8:16 ` Jens Rosenboom
2009-08-13 14:03 ` Brian Haley
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=4A836D70.1040702@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=jens@mcbone.net \
--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).