Introduce two new route flags: RTF_LOCAL and RTF_BROADCAST.

Nothing use them for the moment, but here is the plan:

Since a route lookup is always necessary to output a packet it makes
sense to store all the information regarding how the packet should be
sent in the routing entry.  This will save us some expensive lookups
on address lists.

But once we have all the information about our addresses in the routing
table, we can even use it in the input path with the hope that the number
of lookups in the forwarding case can be reduce to one.

ok henning@, chris@

1 files changed, 3 insertions, 1 deletions

diff --git a/sbin/route/show.c b/sbin/route/show.c
index 59fe7eae26a..0f9c2e5ba8e 100644
--- a/sbin/route/show.c
+++ b/sbin/route/show.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: show.c,v 1.95 2014/04/17 15:35:35 claudio Exp $	*/
+/*	$OpenBSD: show.c,v 1.96 2014/05/08 09:28:08 mpi Exp $	*/
 /*	$NetBSD: show.c,v 1.1 1996/11/15 18:01:41 gwr Exp $	*/
 
 /*
@@ -93,6 +93,8 @@ static const struct bits bits[] = {
 	{ RTF_CLONED,	'c' },
 	{ RTF_MPATH,	'P' },
 	{ RTF_MPLS,	'T' },
+	{ RTF_LOCAL,	'l' },
+	{ RTF_BROADCAST, 'b' },
 	{ 0 }
 };