From: Rich Collins (nilsi2002@gmail.com)
Date: Wed Oct 17 2007 - 16:12:52 ART
The filter list will never see the prepend since it comes before the
route-map.
For outbound updates the order of preference is:
1. prefix-list, distribute-list
2. filter-list
3. route-map
Let's say you were filtering on the inbound. You could use the below
statement for filtering one or more prepends of 123. This version _123$ is
not tight enough.
ip as-path access-list 1 permit ^(123_)+$
-Rich
On 10/17/07, Joe Gagznos <kemphall@yahoo.com> wrote:
>
> Just want to check this. I have the following bgp
> configuration:
>
> router bgp 123
> network 1.2.3.0 mask 255.255.255.0
> neighbor 221.122.10.1 remote as 2131
> neighbor 221.122.10.1 route-map pathprepend out
> neighbor 221.122.10.1 filter-list 1 out
>
> route-map pathprepend permit 10
> set as-path prepend 123 123
> route-map pathprepend permit 20
>
> ip as-path access-list 1 permit ^$
> ip as-path access-list 1 permit ^123$
> ip as-path access-list 1 deny .*
>
> Is the as path access list going to fail this route
> advertisement? If I changed the access list to the
> following would I still only be allowing routes
> originating from 123 and allow as much prepending as I
> want?
>
> ip as-path access-list 1 permit ^$
> ip as-path access-list 1 permit _123$
> ip as-path access-list 1 deny .*
>
> Thanks for your help!
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:15 ART