netdev
[Top] [All Lists]

Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses

To: Derek Fawcus <dfawcus@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses
From: Yuji Sekiya <sekiya@xxxxxxxxxxxxxx>
Date: Thu, 10 Oct 2002 06:46:16 +0900
Cc: usagi@xxxxxxxxxxxxxx
In-reply-to: <20021009170018.H29133@xxxxxxxxxxxxxxxxxxx>
Organization: Keio University
References: <20021008.000559.17528416.yoshfuji@xxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Wanderlust/2.8.1 (Something) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (Kashiharajingū-mae) APEL/10.3 Emacs/20.7 (i386-*-nt5.1.2600) MULE/4.1 (AOI) Meadow/1.15pre1-IPv6 (SHOUBU:63)
At Wed, 9 Oct 2002 17:00:18 +0100,
Derek Fawcus <dfawcus@xxxxxxxxx> 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


<Prev in Thread] Current Thread [Next in Thread>