From: Hadmut Danisch <hadmut@danisch.de>
To: David Miller <davem@davemloft.net>
Cc: 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:12:30 +0100 [thread overview]
Message-ID: <4D51BFCE.2070405@msgid.danisch.de> (raw)
In-Reply-To: <20110208.134421.39185637.davem@davemloft.net>
On 08.02.2011 22:44, David Miller wrote:
>
> This is a case where we're probably just following what the RFC documents
> state we should do, which means unless you can provide clear reference to
> a specification that states we should behave otherwise this isn't changing.
Could you cite where exactly this is stated in the RFC documents? (Would
save me the time to dig through all the RFCs to find that particular
statement and help avoid misunderstanding.)
It appears to me to be a contradiction in terms. IPv6 interfaces must be
able to have several IP addresses, and IPv6 does not have a default
route (or 0::0/0). IPv6 interfaces are designed to participate in
multiple independend logical networks (and several address ranges have
been reserved for future extensions and uses). It therefore does not
make sense if autoconfiguration for one network and routing for another
are mutually exclusive. I'd like to check this (and maybe file a bug in
the RFC).
regards
Hadmut
next prev parent reply other threads:[~2011-02-08 22:19 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 [this message]
2011-02-08 22:30 ` David Miller
2011-02-08 22:44 ` Francois Romieu
2011-02-08 22:59 ` Hadmut Danisch
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=4D51BFCE.2070405@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 \
/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.