From owner-freebsd-net@FreeBSD.ORG Mon Oct 2 13:56:03 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 5A19F16A40F for ; Mon, 2 Oct 2006 13:56:03 +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 7C9A843D58 for ; Mon, 2 Oct 2006 13:56:02 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (shuttle.wide.toshiba.co.jp [2001:200:1b1::35]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 5EBE11521B; Mon, 2 Oct 2006 22:56:01 +0900 (JST) Date: Mon, 02 Oct 2006 22:55:58 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: John Hay In-Reply-To: <20061002115606.GA14698@zibbi.meraka.csir.co.za> References: <20060907100944.GA68587@zibbi.meraka.csir.co.za> <20060907141019.91998.qmail@web26604.mail.ukl.yahoo.com> <20060908161514.GA42016@zibbi.meraka.csir.co.za> <20061002115606.GA14698@zibbi.meraka.csir.co.za> 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: freebsd-net@freebsd.org Subject: Re: ipv6 host routes 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, 02 Oct 2006 13:56:03 -0000 >>>>> On Mon, 2 Oct 2006 13:56:06 +0200, >>>>> John Hay said: >> The key point here is whether the route is statically created or not. >> And, if I understand your intent correctly, the host route you want to >> install is not really "static" in that it can (or should) be removed >> when it's detected to be unreachable, right? > Maybe I should state what I want to achieve again. I believe I already knew that. Perhaps I was not really clear about the point, but the important part is: + the code currently committed in the repository is not correct in that it has a bad side-effect (so whether my patch is correct or not it should be removed or fixed anyway) + the proposed change in my previous post should provide what you want to achieve without the side-effect One subtle point is that the host route (a neighbor *cache* entry) will be removed automatically in the kernel when that host is detected to be unreachable via the Neighbor Unreachability Detection process. This should be the case for the current code and for my patch. The process (daemon) that installed the host route will thus be responsible for taking care of the automatic removal event, by re-installing the route, or synchronizing internal data with the kernel, etc. This is what I intended to point out by saying it's not really 'static'. Am I now clear enough? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp