From owner-freebsd-net@FreeBSD.ORG Mon Jul 28 14:51:33 2003 Return-Path: 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 8B17037B401 for ; Mon, 28 Jul 2003 14:51:33 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAD8E43F75 for ; Mon, 28 Jul 2003 14:51:32 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.nic.fr [IPv6:::1] (may be forged)) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h6SLpT96025347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 28 Jul 2003 17:51:29 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id h6SLpSoZ025344; Mon, 28 Jul 2003 17:51:28 -0400 (EDT) (envelope-from wollman) Date: Mon, 28 Jul 2003 17:51:28 -0400 (EDT) From: Garrett Wollman Message-Id: <200307282151.h6SLpSoZ025344@khavrinen.lcs.mit.edu> To: Vincent Jardin In-Reply-To: <200307282345.28228.vjardin@wanadoo.fr> References: <200307282345.28228.vjardin@wanadoo.fr> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) cc: net@freebsd.org Subject: RTF_CLONING vs RTF_PRCLONING X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 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, 28 Jul 2003 21:51:33 -0000 < said: > I agree, then... Isn't it already the purpose of RTF_CLONING ? > When should RTF_PRCLONIG be set ? RTF_PRCLONING is set automatically by the protocol to cause host routes to be generated on every unique lookup. RTF_CLONING is set when the route is added (either manually, or automatically for interface routes) to indicate that a more specific route (possibly a host route) needs to be generated on every unique lookup. RTF_XRESOLVE is set when the target of the newly cloned route is not known by the kernel and must be set up by a user process. I'm not sure if anything ever used this, although I guess it could be used to implement ISIS. -GAWollman