From owner-freebsd-bugs Fri May 4 8:50:11 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6E1D637B422 for ; Fri, 4 May 2001 08:50:09 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f44Fo9p34587; Fri, 4 May 2001 08:50:09 -0700 (PDT) (envelope-from gnats) Date: Fri, 4 May 2001 08:50:09 -0700 (PDT) Message-Id: <200105041550.f44Fo9p34587@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: Re: bin/26970: 4.3 netstat -r output Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/26970; it has been noted by GNATS. From: Garrett Wollman To: Ruslan Ermilov Cc: FreeBSD-gnats-submit@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: bin/26970: 4.3 netstat -r output Date: Fri, 4 May 2001 11:49:41 -0400 (EDT) < 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-bugs" in the body of the message