Hi Scott, I believe if you use an ip prefix-list as opposed to a standard ACL it might accomplish what you want for your route-map (this syntax works on Cisco for sure, believe it should be the same for Foundry) :
ip prefix-list default-route permit 0.0.0.0/0 ! route-map bgp-from-asXXXXXX-primary permit 40 match ip address prefix-list default-route set metric 100 set local-preference 105 set community 35954:1000 35954:1006 35954:10061 additive ! end I believe the 0.0.0.0/0 standard acl permit is destination based and the Foundry rightly inteprets it as 'any' whereas the prefix-list is matching the actual prefix announced to you from your provider. -paul -----Original Message----- From: Scott "Tuc" Ellentuch at T-B-O-H [mailto:[EMAIL PROTECTED] Sent: Friday, June 02, 2006 10:34 AM To: foundry-nsp at puck.nether.net Subject: [f-nsp] How to route-map default route Hi, I'm trying to set a route-map for my BGP that when I get the default route from one of my transit providers, I can handle it differently than the rest of my BGP. I tried something like : ip access-list standard default-route permit 0.0.0.0/0 but when I do a "sho run" I see : ip access-list standard test permit any which isn't what I want... I'd like to then use it in : route-map bgp-from-asXXXXXX-primary permit 40 match ip address default-route !I'm not sure about the syntax of that, I usually use match community. !I'll set metric 100 set local-preference 105 set community 35954:1000 35954:1006 35954:10061 additive Thanks, Tuc _______________________________________________ foundry-nsp mailing list foundry-nsp at puck.nether.net http://puck.nether.net/mailman/listinfo/foundry-nsp -------------- next part -------------- An HTML attachment was scrubbed... URL: https://puck.nether.net/pipermail/foundry-nsp/attachments/20060602/6c060184/attachment.html
