From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuji Sekiya Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses Date: Thu, 10 Oct 2002 06:46:16 +0900 Sender: netdev-bounce@oss.sgi.com Message-ID: References: <20021008.000559.17528416.yoshfuji@linux-ipv6.org> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Cc: usagi@linux-ipv6.org Return-path: To: Derek Fawcus , linux-kernel@vger.kernel.org, netdev@oss.sgi.com In-Reply-To: <20021009170018.H29133@edinburgh.cisco.com> Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org At Wed, 9 Oct 2002 17:00:18 +0100, Derek Fawcus wrote: > Without reading the kernel routing table code a bit more, I'm not certain > what that change does, but it looks as if it might be changing the > connected route for a link local from fe80::/10 to fe80::/64. Why do you want to use /10 prefix for link-local address ? RFC2373 defines link-local address format as below. | 10 | | bits | 54 bits | 64 bits | +----------+-------------------------+----------------------------+ |1111111010| 0 | interface ID | +----------+-------------------------+----------------------------+ > All link local's are currently supposed to have those top bits > ('tween 10 and 64) zero'd, however any address within the link local > prefix _is_ on link / connected and should go to the interface. If you wan to use /10 prefix for link-local address, you can add the link-local address with /10 prefix to interfaces and routing table manually at your own risk, but it should not be a default behavior. -- Yuji Sekiya