Date: Tue, 29 Jul 2003 09:38:30 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: net@freebsd.org Subject: Re: RTF_CLONING vs RTF_PRCLONING Message-ID: <20030729063830.GD76774@sunbay.com> In-Reply-To: <200307282151.h6SLpSoZ025344@khavrinen.lcs.mit.edu> References: <200307282345.28228.vjardin@wanadoo.fr> <200307282151.h6SLpSoZ025344@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--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: > <<On Mon, 28 Jul 2003 23:45:28 +0200, Vincent Jardin <vjardin@wanadoo.fr>= 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030729063830.GD76774>