netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karsten Keil <kkeil@suse.de>
To: netdev@vger.kernel.org
Subject: Linux IPv6 DAD not full conform to RFC 4862 ?
Date: Wed, 9 Jan 2008 16:36:56 +0100	[thread overview]
Message-ID: <20080109153656.GA16962@pingi.kke.suse.de> (raw)

Hi,

I tried to run the 1.5.0 Beta2  TAHI Selftest on recent Linux kernel.
It fails in the Stateless Address Autoconfiguration section with
6 tests.
These tests are for Duplicate Address Detection (DAD).
They are detect for the Link Local Address a duplicate address on the
network. It seems that our current behavior is to log an message and
do not assign this address.

But the RFC 4862 says:

5.4.5.  When Duplicate Address Detection Fails

   A tentative address that is determined to be a duplicate as described
   above MUST NOT be assigned to an interface, and the node SHOULD log a
   system management error.

   If the address is a link-local address formed from an interface
   identifier based on the hardware address, which is supposed to be
   uniquely assigned (e.g., EUI-64 for an Ethernet interface), IP
   operation on the interface SHOULD be disabled.  By disabling IP
   operation, the node will then:

   -  not send any IP packets from the interface,

   -  silently drop any IP packets received on the interface, and

   -  not forward any IP packets to the interface (when acting as a
      router or processing a packet with a Routing header).

   In this case, the IP address duplication probably means duplicate
   hardware addresses are in use, and trying to recover from it by
   configuring another IP address will not result in a usable network.
   In fact, it probably makes things worse by creating problems that are
   harder to diagnose than just disabling network operation on the
   interface; the user will see a partially working network where some
   things work, and other things do not.

   On the other hand, if the duplicate link-local address is not formed
   from an interface identifier based on the hardware address, which is
   supposed to be uniquely assigned, IP operation on the interface MAY
   be continued.


So I think we should disable the interface now, if DAD fails on a
hardware based LLA.

-- 
Karsten Keil
SuSE Labs

             reply	other threads:[~2008-01-09 15:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 15:36 Karsten Keil [this message]
2008-01-09 16:17 ` Linux IPv6 DAD not full conform to RFC 4862 ? 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
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=20080109153656.GA16962@pingi.kke.suse.de \
    --to=kkeil@suse.de \
    --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).