Hi,
I meant to send this a while ago, but better to be late then never.
If I may, I would suggest to following changes in the example in the
bgpd.conf man page that actually reflect the possible use of shorter
version of filter statement in the configuration just like we have it in
pf.conf as well.
This is to follow up on a question that I had about it and that Henning
confirmed as it was possible, intended as such and that it was going to
stay as well.
Reference and confirmation here:
http://marc.info/?l=openbsd-misc&m=123840595931523&w=2
So, may as well add the possibility in the example in the bgpd.conf no?
I did the changes as small as possible, but that would show the
possibility as being there for sure.
Index: bgpd.conf.5
===================================================================
RCS file: /cvs/src/usr.sbin/bgpd/bgpd.conf.5,v
retrieving revision 1.92
diff -N -u -p bgpd.conf.5
--- bgpd.conf.5 27 May 2009 04:18:21 -0000 1.92
+++ bgpd.conf.5 3 Jun 2009 02:27:07 -0000
@@ -941,15 +941,15 @@ entries may be specified,
separated by commas or whitespace,
if enclosed in curly brackets:
.Bd -literal -offset indent
-deny from any prefix { 192.168.0.0/16, 10.0.0.0/8 }
+deny from any prefix { 192.168.0.0/16, 10/8 }
.Ed
.Pp
Multiple lists can also be specified, which is useful for
macro expansion:
.Bd -literal -offset indent
-good="{ 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8 }"
-bad="{ 224.0.0.0/4, 240.0.0.0/4 }"
-ugly="{ 127.0.0.1/8, 169.254.0.0/16 }"
+good="{ 192.168.0.0/16, 172.16.0.0/12, 10/8 }"
+bad="{ 224.0.0.0/4, 240/4 }"
+ugly="{ 127.0.0.1/8, 169.254/16 }"
deny from any prefix { $good $bad $ugly }
.Ed
