Nope ... seems to result in a LOT of these
received notification: Cease, max-prefix exceeded
for all our v4 peers / etc
On 27 Mar 2007, at 19:25, Claudio Jeker wrote:
On Tue, Mar 27, 2007 at 07:12:50PM +0100, Jon Morby wrote:
Thanks Claudio ... you guys are super stars! :)
Seems to be working a treat
Now to work out the filters :(
/etc/bgpd.conf:796: king bula sez: AF_INET only
796:allow quick to any prefix 2a01:2c0::/32
What's the correct way to ensure your AF_INET6 prefixes are properly
exported?
Oops looks like some very old leftovers. Could you give this one
here a
whril? I think that's enough to make the filtering of IPv6 prefixes
possible but as you may guess I have no real IPv6 sessions running.
--
:wq Claudio
Index: parse.y
===================================================================
RCS file: /cvs/src/usr.sbin/bgpd/parse.y,v
retrieving revision 1.201
diff -u -p -r1.201 parse.y
--- parse.y 6 Mar 2007 16:52:48 -0000 1.201
+++ parse.y 27 Mar 2007 18:20:59 -0000
@@ -1027,13 +1027,6 @@ encspec : /* nada */ {
filterrule : action quick direction filter_peer_h filter_match_h
filter_set
{
struct filter_rule r;
- struct filter_prefix_l *l;
-
- for (l = $5.prefix_l; l != NULL; l = l->next)
- if (l->p.addr.af && l->p.addr.af != AF_INET) {
- yyerror("king bula sez: AF_INET only");
- YYERROR;
- }
bzero(&r, sizeof(r));
r.action = $1;
