[c-nsp] as path filtering in route map policy

[Brian Feeny]

Alain,

You can't use BGP attributes (AS_PATH or otherwise) to filter normal 
ip/ethernet packets.  You use the BGP Attributes to filter BGP routes, 
learned from a BGP neighbor session.  So what your doing is not 
possible.

Brian

On Sep 21, 2004, at 7:40 PM, Alain Cocconi wrote:

> Hello,
>
> I'm trying to do a route selection on a bgp prefix but when I use the 
> config below, all the packets are matched by the
> first route-map. Is it possible to use the ip as-path access list in 
> this case ?
>
> tia
>
> interface GigabitEthernet0/3
>  ip address 192.168.100.100 255.255.255.0
>  no ip redirects
>  no ip unreachables
>  no ip proxy-arp
>  ip accounting access-violations
>  ip load-sharing per-packet
>  ip route-cache policy
>  ip route-cache flow
>  no ip mroute-cache
>  ip policy route-map test-out
>  no negotiation auto
>  no cdp enable
> !
> ip as-path access-list 1 permit ^17480$
> !
> access-list 150 permit ip 192.168.68.0 0.0.3.255 any
> !
> route-map test-out permit 10
>  match as-path 1
>  set ip next-hop 192.168.128.213
> !
> route-map test-out permit 20
>  match ip address 150
>  set ip next-hop 192.168.128.209
> !
> route-map test-out deny 30
> !
>
> _______________________________________________
> 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/
>
---------------------------------------------
Brian Feeny, CCIE #8036, CISSP
Network Engineer
ShreveNet Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : https://puck.nether.net/pipermail/cisco-nsp/attachments/20040921/427b4e4b/PGP.bin