From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 12:49:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 12:49:09 -0400 Received: from yue.hongo.wide.ad.jp ([203.178.139.94]:56584 "EHLO yue.hongo.wide.ad.jp") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 12:49:08 -0400 Date: Thu, 10 Oct 2002 01:54:32 +0900 (JST) Message-Id: <20021010.015432.63506989.yoshfuji@linux-ipv6.org> To: dfawcus@cisco.com Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, usagi@linux-ipv6.org Subject: Re: [PATCH] IPv6: Fix Prefix Length of Link-local Addresses From: YOSHIFUJI Hideaki / =?iso-2022-jp?B?GyRCNUhGIzFRTEAbKEI=?= In-Reply-To: <20021009170018.H29133@edinburgh.cisco.com> References: <20021008.000559.17528416.yoshfuji@linux-ipv6.org> <20021009170018.H29133@edinburgh.cisco.com> Organization: USAGI Project X-URL: http://www.yoshifuji.org/%7Ehideaki/ X-Fingerprint: 90 22 65 EB 1E CF 3A D1 0B DF 80 D8 48 07 F8 94 E0 62 0E EA X-PGP-Key-URL: http://www.yoshifuji.org/%7Ehideaki/hideaki@yoshifuji.org.asc X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org In article <20021009170018.H29133@edinburgh.cisco.com> (at Wed, 9 Oct 2002 17:00:18 +0100), Derek Fawcus says: > 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. > > i.e. it's perfectly valid for me to assign a link local of fe80:1910::10 > to an interface and expect it to be work, likewise for a packet > destined to any link local address to trigger ND. First of all, please don't use such addresses. By spec, auto-configured link-local address is fe80::/64 and connected route should be /64. If you do really want to use such addresses (like fe80:1920::10), you can put another route by yourself, at your own risk. We should not configure in such way by default. and, we should even have to add "discard" route for them by default for safe. --yoshfuji