From: Ben Greear <greearb@candelatech.com>
To: David Miller <davem@davemloft.net>
Cc: brian.haley@hp.com, netdev@vger.kernel.org
Subject: Re: [net-next] ipv6: Enable netlink notification for tentative addresses.
Date: Thu, 26 Aug 2010 14:19:30 -0700 [thread overview]
Message-ID: <4C76DA62.8040109@candelatech.com> (raw)
In-Reply-To: <20100826.131801.246519955.davem@davemloft.net>
On 08/26/2010 01:18 PM, David Miller wrote:
> From: Brian Haley<brian.haley@hp.com>
> Date: Thu, 26 Aug 2010 15:57:51 -0400
>
>> But then we get a message for an address that can't be used because
>> it hasn't passed DAD, I'm not so sure that is a good thing,
>> especially if we don't get notified when it passes DAD.
>
> I think that we shouldn't send notifications for an address that can't
> even be used. So essentially I argue against this patch in any form :)
In our case, we enable IPv6 in user-space, and then we want to get some
immediate indication that indeed the process is working as expected.
In other cases, we want to remove all IPv6 addresses, so if we have not
even been notified that the IP exists, then we cannot know how to delete it.
In my patch, we still get the update when DAD completes, so applications
can take note of the flags if they care about the details.
We've been running this patch for several years, and it has not caused
any obvious problems with other tools, so I think it's safe enough.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-08-26 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 18:26 [net-next] ipv6: Enable netlink notification for tentative addresses Ben Greear
2010-08-26 4:24 ` David Miller
2010-08-26 18:50 ` Ben Greear
2010-08-26 19:57 ` Brian Haley
2010-08-26 20:18 ` David Miller
2010-08-26 21:19 ` Ben Greear [this message]
2010-08-26 21:27 ` David Miller
2010-08-27 4:24 ` Ben Greear
2010-08-26 21:22 ` Ben Greear
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=4C76DA62.8040109@candelatech.com \
--to=greearb@candelatech.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.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).