make netstat distinguish broadcast and blackhole routes where they appear.

(RTF_BLACKHOLE was already documented as being shown, but the code ignored
it)

Sumbitted by: Greg Lehey <grog@lemis.de>
This commit is contained in:
Peter Wemm 1996-06-15 17:08:40 +00:00
parent 1a1fde273c
commit 1336da0dea
2 changed files with 4 additions and 1 deletions

View File

@ -231,6 +231,7 @@ The mapping between letters and flags is:
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)

View File

@ -36,7 +36,7 @@
static char sccsid[] = "From: @(#)route.c 8.6 (Berkeley) 4/28/95";
#endif
static const char rcsid[] =
"$Id: route.c,v 1.14 1996/06/08 00:20:42 julian Exp $";
"$Id: route.c,v 1.15 1996/06/10 21:03:38 julian Exp $";
#endif /* not lint */
#include <sys/param.h>
@ -96,6 +96,8 @@ struct bits {
{ RTF_WASCLONED,'W' },
{ RTF_PRCLONING,'c' },
{ RTF_PROTO3, '3' },
{ RTF_BLACKHOLE,'B' },
{ RTF_BROADCAST,'b' },
{ 0 }
};