From owner-freebsd-net@FreeBSD.ORG Tue May 23 04:43:15 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4435616A422; Tue, 23 May 2006 04:43:15 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id A85B843D48; Tue, 23 May 2006 04:43:13 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (unknown [3ffe:501:100f:1010:c8fe:96a0:82e2:cdb6]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 7767315218; Tue, 23 May 2006 13:43:12 +0900 (JST) Date: Tue, 23 May 2006 13:43:01 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: "George V. Neville-Neil" In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "Bruce A. Mah" , Ed Schouten , FreeBSD Net Subject: Re: nd6_lookup prints bogus messages with point to point devices X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 04:43:15 -0000 >>>>> On Mon, 22 May 2006 09:50:37 -0700, >>>>> "George V. Neville-Neil" said: >> Could you try the patch attached below? It's for 6.1-RELEASE, but I >> guess it's pretty easy to apply to CURRENT. >> >> The essential reason of this problem is that the latest kernel regards >> the destination address of a point-to-point interface as a "neighbor" >> wrt Neighbor Discovery while a neighbor cache entry is not created on >> configuring the interface with the addresses. I believe it makes >> sense to treat the destination address as a neighbor, so the fix is to >> make sure that the cache entry is created when the interface is >> configured. > I can apply and commit this after a bit of testing. Thanks, please do to. I believe the patch also fixes this problem report: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/93220 So, could you also confirm this and give feedback to (or close) the report? (I'll send a follow-up message to the report by myself it it's appropriate). Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp