Date: Sat, 15 Jun 1996 13:45:23 +0200 (MET DST) From: grog@lemis.de (Greg Lehey) To: hackers@freebsd.org (FreeBSD Hackers) Subject: Mods for netstat Message-ID: <199606151228.OAA00575@allegro.lemis.de>
next in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606151228.OAA00575>