From: David Ahern <dsahern@gmail.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] net: ipv6: Make address flushing on ifdown optional
Date: Tue, 27 Jan 2015 07:55:18 -0700 [thread overview]
Message-ID: <54C7A6D6.8020805@gmail.com> (raw)
In-Reply-To: <1422351861.13969.5.camel@stressinduktion.org>
On 1/27/15 2:44 AM, Hannes Frederic Sowa wrote:
>> You are probably correct that many will not switch, but this sysctl
>> gives those who want to switch a nice option without having to carry
>> extra kernel patches. I like it.
>
> I don't see any problem with the patch in general but DAD should
> definitely happen on reenabling interfaces. Current behavior does not
> seem fine to me. It's ok if this patch doesn't change this behavior now
> but a follow-up one will be needed then.
>
> David, will you look after the DAD logic and do you plan a follow-up
> patch?
Yes, I do plan a follow-up patch for this change. Will work on that this
week.
From the discussion a second patch is needed to make sure DAD is done
on a link up if there is an address configured.
David
next prev parent reply other threads:[~2015-01-27 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:17 [RFC PATCH] net: ipv6: Make address flushing on ifdown optional David Ahern
2015-01-19 15:02 ` Hannes Frederic Sowa
2015-01-19 16:12 ` Harout Hedeshian
2015-01-19 19:11 ` Hannes Frederic Sowa
2015-01-20 17:07 ` David Ahern
2015-01-23 6:40 ` Stephen Hemminger
2015-01-23 12:22 ` Hannes Frederic Sowa
2015-01-27 4:56 ` Andy Gospodarek
2015-01-27 9:44 ` Hannes Frederic Sowa
2015-01-27 14:55 ` David Ahern [this message]
2015-01-27 15:28 ` Hannes Frederic Sowa
2015-01-28 3:21 ` David Ahern
2015-01-28 8:25 ` Hannes Frederic Sowa
2015-01-27 16:09 ` Andy Gospodarek
2015-01-23 18:47 ` David Ahern
2015-01-23 16:09 ` Brian Haley
2015-01-23 18:23 ` David Ahern
2015-01-23 21:17 ` Brian Haley
2015-01-26 16:49 ` Hannes Frederic Sowa
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=54C7A6D6.8020805@gmail.com \
--to=dsahern@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).