netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
	kkeil@suse.de, netdev@vger.kernel.org
Subject: Re: Linux IPv6 DAD not full conform to RFC 4862 ?
Date: Thu, 10 Jan 2008 07:25:49 -0500	[thread overview]
Message-ID: <20080110122549.GA17348@hmsreliant.think-freely.org> (raw)
In-Reply-To: <47853825.2030002@hp.com>

On Wed, Jan 09, 2008 at 04:09:57PM -0500, Vlad Yasevich wrote:
> Neil Horman wrote:
>> On Thu, Jan 10, 2008 at 01:38:57AM +0900, YOSHIFUJI Hideaki / 吉藤英明 wrote:
>>> In article <20080109153656.GA16962@pingi.kke.suse.de> (at Wed, 9 Jan 2008 16:36:56 +0100), Karsten Keil <kkeil@suse.de> says:
>>>
>>>> So I think we should disable the interface now, if DAD fails on a
>>>> hardware based LLA.
>>> I don't want to do this, at least, unconditionally.
>>>
>>> Options (not exclusive):
>>>
>>> - we could have "dad_reaction" interface variable and
>>>  > 1: disable interface
>>>  = 1: disable IPv6
>>>  < 0: ignore (as we do now)
>>>
>> I like the flexibility of this solution, but given that the only part of the RFC
>> that we're missing on at the moment is that we SHOULD disable the interface on
>> DAD failure for a link-local address, I would think this scheme would be good:
>>
>>   < 0 : ignore, and del address from interface (current behavior)   = 0 : 
>> disable interface for dad failure for a link-local address   > 0 : disable 
>> interface for dad failure for any address 
>> Regards
>> Neil
>>  
>
> Just a friendly reminder that such a scheme should only be
> applied to autoconfigured addresses.  A manually configured
> duplicated address should not bring down the whole interface.
>

I agree, but I think that case would be covered by the default option above
(sysctl < 0).

Neil

> -vlad

  reply	other threads:[~2008-01-10 12:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 15:36 Linux IPv6 DAD not full conform to RFC 4862 ? Karsten Keil
2008-01-09 16:17 ` Neil Horman
2008-01-09 20:26   ` Karsten Keil
2008-01-10 11:16     ` Karsten Keil
2008-01-09 16:38 ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-09 16:40   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-09 20:32     ` Karsten Keil
2008-01-09 18:57   ` Neil Horman
2008-01-09 21:09     ` Vlad Yasevich
2008-01-10 12:25       ` Neil Horman [this message]
2008-01-09 23:32 ` David Miller
2008-01-09 23:46   ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-09 23:55     ` David Miller
2008-01-10  0:09       ` YOSHIFUJI Hideaki / 吉藤英明
2008-01-10 11:29   ` Karsten Keil

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=20080110122549.GA17348@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=kkeil@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=vladislav.yasevich@hp.com \
    --cc=yoshfuji@linux-ipv6.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).