Date: Mon, 22 May 2006 09:50:37 -0700 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> Cc: "Bruce A. Mah" <bmah@FreeBSD.org>, Ed Schouten <ed@fxq.nl>, FreeBSD Net <freebsd-net@FreeBSD.org> Subject: Re: nd6_lookup prints bogus messages with point to point devices Message-ID: <m2hd3i3swy.wl%gnn@neville-neil.com> In-Reply-To: <y7vk68eqtwf.wl%jinmei@isl.rdc.toshiba.co.jp> References: <20060506172742.GM15353@hoeg.nl> <445EC341.60406@freebsd.org> <20060508065841.GN15353@hoeg.nl> <y7v7j4k623s.wl%jinmei@isl.rdc.toshiba.co.jp> <y7vk68eqtwf.wl%jinmei@isl.rdc.toshiba.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2hd3i3swy.wl%gnn>