All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hadmut Danisch <hadmut@danisch.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: David Miller <davem@davemloft.net>,
	akpm@linux-foundation.org, netdev@vger.kernel.org,
	bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 28282] New: forwarding turns autoconfiguration off
Date: Tue, 08 Feb 2011 23:59:52 +0100	[thread overview]
Message-ID: <4D51CAE8.6070706@msgid.danisch.de> (raw)
In-Reply-To: <20110208224411.GA9674@electric-eye.fr.zoreil.com>

On 08.02.2011 23:44, Francois Romieu wrote:
>
> RFC 4862        IPv6 Stateless Address Autoconfiguration  September 2007
> [...]
>    The autoconfiguration process specified in this document applies only
>    to hosts and not routers.  Since host autoconfiguration uses
>    information advertised by routers, routers will need to be configured
>    by some other means.  However, it is expected that routers will
>    generate link-local addresses using the mechanism described in this
>    document.  In addition, routers are expected to successfully pass the
>    Duplicate Address Detection procedure described in this document on
>    all addresses prior to assigning them to an interface.

Thanks for the citation.


Since Linux machines can - in contrast to Windows desktops and cisco
routers - can be a host and a router at the same time, even on the same
interface (i.e. use a autoconf IPv6 address as a host and an fe80::
address as a router address).

So I'd consider this in a different way. From my point of view the
decision between host and router must be done per assigned IPv6 address
(or address range) and not per IPv6 interface.

(Maybe it would be a more correct implementation to assign a special IP
address pattern like  xxxx::.../64 to tell the interface to accept
autoconfiguration for a particular network range, probably  for 2::/3 in
most cases.)

regards
Hadmut



  reply	other threads:[~2011-02-08 22:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-28282-10286@https.bugzilla.kernel.org/>
2011-02-08 21:34 ` [Bugme-new] [Bug 28282] New: forwarding turns autoconfiguration off Andrew Morton
2011-02-08 21:44   ` David Miller
2011-02-08 22:12     ` Hadmut Danisch
2011-02-08 22:30       ` David Miller
2011-02-08 22:44         ` Francois Romieu
2011-02-08 22:59           ` Hadmut Danisch [this message]
2011-02-08 23:49             ` Francois Romieu
2011-02-09  4:47           ` Bill Fink
2011-02-09  7:42             ` Francois Romieu
2011-02-09  7:56               ` Hadmut Danisch
2011-03-24 15:07               ` Hadmut Danisch
2011-03-24 16:25                 ` David Lamparter

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=4D51CAE8.6070706@msgid.danisch.de \
    --to=hadmut@danisch.de \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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.