From owner-freebsd-hackers  Sat Jun 15 05:47:37 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA23322
          for hackers-outgoing; Sat, 15 Jun 1996 05:47:37 -0700 (PDT)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA23317
          for <hackers@freebsd.org>; Sat, 15 Jun 1996 05:47:34 -0700 (PDT)
Received: from allegro.lemis.de by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0uUujo-000QaYC; Sat, 15 Jun 96 14:46 MET DST
From: grog@lemis.de (Greg Lehey)
Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax:   +49-6637-919122
Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) 
	id OAA00575 for hackers@freebsd.org; Sat, 15 Jun 1996 14:28:14 +0200
Message-Id: <199606151228.OAA00575@allegro.lemis.de>
Subject: Mods for netstat
To: hackers@freebsd.org (FreeBSD Hackers)
Date: Sat, 15 Jun 1996 13:45:23 +0200 (MET DST)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm currently following a problem with broadcast messages, and
discover that netstat -r doesn't indicate whether the route is a
broadcast address or not.  At the same time, I discover that the man
page claims to flag black holes, but the mod must have fallen into a
black hole...

Here are a couple of patches which address both these points.  Is
there a more formal way of submitting this sort of thing?

Greg

RCS file: RCS/route.c,v
retrieving revision 1.15
diff -wu -r1.15 route.c
--- route.c     1996/06/10 21:03:38     1.15
+++ route.c     1996/06/15 11:41:59
@@ -96,6 +96,8 @@
        { RTF_WASCLONED,'W' },
        { RTF_PRCLONING,'c' },
        { RTF_PROTO3,   '3' },
+       { RTF_BLACKHOLE,'B' },
+       { RTF_BROADCAST,'b' },
        { 0 }
 };
RCS file: RCS/netstat.1,v
retrieving revision 1.8
diff -wu -r1.8 netstat.1
--- netstat.1   1996/06/08 00:54:18     1.8
+++ netstat.1   1996/06/15 11:41:42
@@ -231,6 +231,7 @@
 2      RTF_PROTO1      Protocol specific routing flag #2 
 3      RTF_PROTO3      Protocol specific routing flag #3
 B      RTF_BLACKHOLE   Just discard pkts (during updates) 
+b      RTF_BROADCAST   The route represents a broadcast address
 C      RTF_CLONING     Generate new routes on use 
 c      RTF_PRCLONING   Protocol-specified generate new routes on use
 D      RTF_DYNAMIC     Created dynamically (by redirect)