Hello All I've got a mini lab setup using dynamips so I can practice all configs, I'm having a little trouble with my ACL's on BGP. If I use a route-map I still get the routes I don't want (bogons) but if I use the prefix-list the route-map calls it works as expected.
non-working :-( neighbor 213.x.x.x remote-as 99999 neighbor 213.x.x.x description eBGP neighbor 213.x.x.x route-map transit-in in neighbor 213..x.x.x route-map announce out Working :-) neighbor 213.x.x.x remote-as 99999 neighbor 213.x.x.x description eBGP neighbor 213.x.x.x prefix-list transit-in in neighbor 213..x.x.x route-map announce out route-maps and prefix-lists used on both configs ip prefix-list announce description Our Allowed routing announcements ip prefix-list announce seq 5 permit 8x.xxx.0.0/19 ip prefix-list announce seq 10 permit 8x.xxx.0.0/19 ip prefix-list announce seq 15 permit 2xx.xxx.0.0/20 ip prefix-list transit-in seq 1 deny 8x.xxx.x.0/19 ip prefix-list transit-in seq 2 deny 8x.xxx.0.0/19 ip prefix-list transit-in seq 3 deny 2xx.xxx.0.0/20 ip prefix-list transit-in seq 50 deny 0.0.0.0/8 le 32 ip prefix-list transit-in seq 51 deny 10.0.0.0/8 ip prefix-list transit-in seq 52 deny 127.0.0.0/8 ip prefix-list transit-in seq 53 deny 172.16.0.0/16 ip prefix-list transit-in seq 54 deny 192.168.0.0/16 ip prefix-list transit-in seq 100 permit 0.0.0.0/0 le 24 ! route-map announce permit 10 match ip address prefix-list announce ! route-map transit-in deny 5 match ip address prefix-list transit-in ! route-map transit-in permit 10 set local-preference 100 The current working/live config is using standard access-lists but I would like to migrate over to a route-map/prefix-list based setup Thanks for your time Wayne _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
