[23645] in North American Network Operators' Group
Cisco Route filtering [was Re: OPS: BGP spew from ASN 7374]
daemon@ATHENA.MIT.EDU (R.P. Aditya)
Wed Apr 7 17:42:36 1999
To: nanog@merit.edu
Cc: Sean Donelan <SEAN@SDG.DRA.COM>
From: "R.P. Aditya" <aditya@dnai.com>
Reply-To: "R.P. Aditya" <aditya@dnai.com>
In-reply-to: Your message of Wed, 07 Apr 1999 15:57:05 -0500.
<990407155705.34b24@SDG.DRA.COM>
Date: Wed, 07 Apr 1999 14:41:14 -0700
Errors-To: owner-nanog-outgoing@merit.edu
This should probably be moved to cisco-nsp if it gets any more in-depth,
however:
> Cisco: could we please have more config memory, so we can load access-lists
> for even huge BGP peers?
Although you're probably asking for exactly what you say, config memory, it
might also be useful to use prefix-lists to filter routing announcements:
http://www.academ.com/nanog/june1998/turner/sld014.htm
and the notes on bug CSCdk93005 seem to indicate that prefix-lists do make a
difference and should be used over access-lists for filtering routes...
Hope that helps,
Adi
