From owner-freebsd-net@FreeBSD.ORG Mon May 22 18:25:48 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 D1AFA16A510; Mon, 22 May 2006 18:25:48 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DC2B43D46; Mon, 22 May 2006 18:25:48 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1-b.corp.dcn.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4MIPOhW024727; Mon, 22 May 2006 11:25:24 -0700 (PDT) Date: Mon, 22 May 2006 09:50:37 -0700 Message-ID: From: "George V. Neville-Neil" To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) 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: Mon, 22 May 2006 18:25:48 -0000 At Mon, 22 May 2006 18:40:48 +0900, jinmei wrote: > 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. Late,r George