From owner-freebsd-net@FreeBSD.ORG Mon Jul 28 23:38:49 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 0467737B401 for ; Mon, 28 Jul 2003 23:38:49 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4935643F75 for ; Mon, 28 Jul 2003 23:38:45 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h6T6ca0U087217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jul 2003 09:38:36 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h6T6cUl0087211; Tue, 29 Jul 2003 09:38:30 +0300 (EEST) (envelope-from ru) Date: Tue, 29 Jul 2003 09:38:30 +0300 From: Ruslan Ermilov To: Garrett Wollman Message-ID: <20030729063830.GD76774@sunbay.com> References: <200307282345.28228.vjardin@wanadoo.fr> <200307282151.h6SLpSoZ025344@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C+ts3FVlLX8+P6JN" Content-Disposition: inline In-Reply-To: <200307282151.h6SLpSoZ025344@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.5.4i cc: net@freebsd.org Subject: Re: 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: Tue, 29 Jul 2003 06:38:49 -0000 --C+ts3FVlLX8+P6JN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 28, 2003 at 05:51:28PM -0400, Garrett Wollman wrote: > <= said: >=20 > > I agree, then... Isn't it already the purpose of RTF_CLONING ? > > When should RTF_PRCLONIG be set ? >=20 > RTF_PRCLONING is set automatically by the protocol to cause host > routes to be generated on every unique lookup. >=20 > 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. >=20 Yes, RTF_CLONING routes also accept the netmask (RTA_GENMASK). I don't remember if it also applies to RTF_PRCLONING routes, but I suspect so. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --C+ts3FVlLX8+P6JN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/JhZmUkv4P6juNwoRAnASAJ93qIScEiDecVKLUI+Doy3moIQt3ACdG3zO vL07ur/D1bL4pKv4PxUPDEU= =ASe8 -----END PGP SIGNATURE----- --C+ts3FVlLX8+P6JN--