From owner-freebsd-net Fri May 4 8:49:54 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5369437B423; Fri, 4 May 2001 08:49:49 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA17937; Fri, 4 May 2001 11:49:41 -0400 (EDT) (envelope-from wollman) Date: Fri, 4 May 2001 11:49:41 -0400 (EDT) From: Garrett Wollman Message-Id: <200105041549.LAA17937@khavrinen.lcs.mit.edu> To: Ruslan Ermilov Cc: FreeBSD-gnats-submit@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: bin/26970: 4.3 netstat -r output In-Reply-To: <20010504182132.B6501@sunbay.com> References: <200104292329.f3TNTBA01095@jonc.itouch> <20010504182132.B6501@sunbay.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > I have a question for Garrett. Was the original idea behind -a flag is > to hide protocol-cloned routes only but not RTF_CLONING generated routes, > or it was simply caused by the bug that `rt_parent' was not set for > routes generated from RTF_CLONING parent, as documented in rtentry(9)? Let me see if I can reconstruct the history. Originally, 4.4's `netstat -r' showed cloned routes. Then I added the ``protocol cloning'' feature and suddenly there were a lot more cloned routes. Then people complained that this was too much information. Then I added the `-a' flag to hide the stuff that protocol-cloning had added. I'm agnostic on whether `-a' should suppress all cloned routes or just the protocol-cloned routes. POLA suggests that the latter is probably a better choice. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message