From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: chunkeey@web.de
Cc: hostap@lists.shmoo.com, netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: IPv6 unique local address flushes on up/down
Date: Wed, 26 Mar 2008 00:24:28 +0900 (JST) [thread overview]
Message-ID: <20080326.002428.19095257.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <200803251557.21563.chunkeey@web.de>
In article <200803251557.21563.chunkeey@web.de> (at Tue, 25 Mar 2008 15:57:21 +0100), Chr <chunkeey@web.de> says:
> Now my question, which _one_ should we fix the applications or the stack?!
> I think the network stack, but I don't know if there are RFC about this
> issue... or is there already some flag/setting which I've missed so far?
Well..., in fact, this is known as an uneasy-to-fix issue.
The behavior han not been changed for long time, so you definately
need to have work-around for this issue, anyway.
>From specification point of view, we need to re-perform DAD (duplicate
address detection) after down-up cycle or even link-down and up.
One possible way is to add "tentative" flag for static addresses
(instead of purging them) when the interface is going down and
reperform DAD for all of such addresses when the interface is coming up.
If the link is being down, we might want to use "Optimistic" DAD instead.
--yoshfuji
next prev parent reply other threads:[~2008-03-25 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 14:57 IPv6 unique local address flushes on up/down Chr
2008-03-25 15:11 ` Denis V. Lunev
2008-03-25 15:24 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2008-03-25 16:07 ` Chr
2008-03-25 16:20 ` YOSHIFUJI Hideaki / 吉藤英明
2008-03-25 17:16 ` Chr
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=20080326.002428.19095257.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=chunkeey@web.de \
--cc=hostap@lists.shmoo.com \
--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).