[c-nsp] BGP Q
Scott Granados
sgranados at jeteye.com
Tue Oct 24 14:06:54 EDT 2006
Sure, this is where prefix lists come in. So something like this would
work.
Ip pref tenblock seq 5 perm 10.0.0.0/16 le 24
Anything matching /16 to /24 should work here but anything like a /25 or
so on should be blocked. Does this help?
G. Scott Granados
Sr. Network Operations Specialist
OFFICE: 415-946-2112 EXT. 222
CELL: 408-569-4017
URL: http://www.jeteye.com
-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
fredrik.jacobsson at seb.se
Sent: Tuesday, October 24, 2006 10:55 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] BGP Q
Hi!
Time for a newbie BGP question...
We like to have control over which networks that are announced to us,
so we're using prefix-lists associated to the neighbors. This is a
corporate
network using BGP with private AS's. No internet and such.
All fine, but it's a bit too much administration with the exact matches
needed by the prefix-lists.
Is there a way to allow all advertisements within for example
10.0.0.0/16 ?
Meaning that I don't have to care about what's specifically announced?
(aggregate-address on the other end is not an option)
So that they may add for example 10.0.20.0/24 to their list of a
other /24's announced to us without any administration at my end...
Best regards
/Fredrik
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list