From: Yuji Sekiya <sekiya@sfc.wide.ad.jp>
To: Derek Fawcus <dfawcus@cisco.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Cc: usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses
Date: Thu, 10 Oct 2002 06:46:16 +0900 [thread overview]
Message-ID: <uwuor9tg7.wl@sfc.wide.ad.jp> (raw)
In-Reply-To: <20021009170018.H29133@edinburgh.cisco.com>
At Wed, 9 Oct 2002 17:00:18 +0100,
Derek Fawcus <dfawcus@cisco.com> 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
next prev parent reply other threads:[~2002-10-09 21:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 15:05 [PATCH] IPv6: Fix Prefix Length of Link-local Addresses YOSHIFUJI Hideaki / 吉藤英明
2002-10-07 18:55 ` David S. Miller
2002-10-08 0:37 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-08 19:40 ` David S. Miller
2002-10-09 16:00 ` Derek Fawcus
2002-10-09 16:54 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-09 17:11 ` Derek Fawcus
2002-10-09 17:16 ` Pekka Savola
2002-10-09 19:03 ` kuznet
2002-10-09 19:23 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-09 20:47 ` kuznet
2002-10-09 21:46 ` Yuji Sekiya [this message]
2002-10-09 22:44 ` Derek Fawcus
2002-10-09 23:14 ` David S. Miller
2002-10-09 23:29 ` Derek Fawcus
2002-10-09 23:24 ` David S. Miller
2002-10-09 23:36 ` Derek Fawcus
2002-10-09 23:41 ` Yuji Sekiya
2002-10-09 23:45 ` David S. Miller
2002-10-10 0:00 ` Yuji Sekiya
2002-10-10 0:04 ` Derek Fawcus
2002-10-10 0:14 ` Yuji Sekiya
2002-10-10 0:21 ` Derek Fawcus
2002-10-10 0:35 ` Yuji Sekiya
2002-10-10 0:42 ` Derek Fawcus
2002-10-10 0:56 ` Yuji Sekiya
2002-10-10 1:11 ` Derek Fawcus
2002-10-10 0:10 ` Derek Fawcus
2002-10-10 0:02 ` Derek Fawcus
2002-10-09 23:51 ` Derek Fawcus
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=uwuor9tg7.wl@sfc.wide.ad.jp \
--to=sekiya@sfc.wide.ad.jp \
--cc=dfawcus@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.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).