From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Hannes Frederic Sowa <hannes@redhat.com>
Cc: David Ahern <dsahern@gmail.com>,
YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: why are IPv6 addresses removed on link down
Date: Tue, 13 Jan 2015 10:13:52 -0500 [thread overview]
Message-ID: <20150113151352.GB28371@oracle.com> (raw)
In-Reply-To: <1421161791.13626.33.camel@redhat.com>
On (01/13/15 16:09), Hannes Frederic Sowa wrote:
>
> Yes, it does have something to do with it. But I didn't understand what
> you meant by doing DAD on the interface-id.
I have to dig up the RFCs for this, but I recall that, at one point,
the specs assert that it is sufficient to verify that the interface-id
(I think via DAD for the link-local address) is unique, and use
that to infer uniqueness of all the other non-link-local addresses
as well.
I think later specs may have changed that, asserting that the
correct, safe, proper thing to do is to separately DAD each address
by itself.
> If you look at the patches I just posted, only addresses which are in
> link-local and not in permanent state will be flushed.
>
> I also need to do research on how to safely approach this, I don't know,
> yet.
>
> Bye,
> Hannes
>
>
next prev parent reply other threads:[~2015-01-13 15:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:06 why are IPv6 addresses removed on link down David Ahern
2015-01-13 7:10 ` Stephen Hemminger
2015-01-13 10:35 ` Hannes Frederic Sowa
2015-01-13 11:58 ` YOSHIFUJI Hideaki
2015-01-13 12:15 ` YOSHIFUJI Hideaki
2015-01-13 12:36 ` Hannes Frederic Sowa
2015-01-13 14:53 ` David Ahern
2015-01-13 15:00 ` Hannes Frederic Sowa
2015-01-13 17:05 ` Nicolas Dichtel
2015-01-13 15:00 ` Sowmini Varadhan
2015-01-13 15:09 ` Hannes Frederic Sowa
2015-01-13 15:13 ` Sowmini Varadhan [this message]
2015-01-13 17:25 ` David Miller
2015-01-13 17:34 ` 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=20150113151352.GB28371@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=dsahern@gmail.com \
--cc=hannes@redhat.com \
--cc=hideaki.yoshifuji@miraclelinux.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.