From owner-freebsd-hackers Wed Apr 12 11:26:34 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA19667 for hackers-outgoing; Wed, 12 Apr 1995 11:26:34 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA19661 for ; Wed, 12 Apr 1995 11:26:33 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14515(3)>; Wed, 12 Apr 1995 11:25:35 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <49864>; Wed, 12 Apr 1995 11:25:25 -0700 X-Mailer: exmh version 1.6gamma 3/30/95 To: John Lind cc: hackers@FreeBSD.org (FreeBSD hackers) Subject: Re: undocumented features of route and netstat in FreeBSD 2.0(-950322-SNAP) In-reply-to: Your message of "Tue, 11 Apr 95 23:18:39 PDT." <199504120618.BAA02125@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Apr 1995 11:25:17 PDT From: Bill Fenner Message-Id: <95Apr12.112525pdt.49864@crevenia.parc.xerox.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk Sounds like netstat has the same bug that netstat -M had -- not printing out netmasks ends up making you guess what netmask is stored in the kernel, meaning that you will probably guess what you expect instead of what is there. Between the time that I discovered the bug and the time that we went to host routes for multicast, I printed out subnets as "x.y.z/n", where n is the number of 1-bits in the netmask. It adds at most 3 characters to the address, and perhaps a "/32" could be left off, to optimize for host-routes. If nobody does this by the time I get around to fixing netstat -M, I will do it. Bill