Hi, I'm interesing in packets from 172.20.0.50, unfortunately I cannot test with that IP, so I used 172.20.0.49. Now if the ip policy route-map has no effect on 172.20.0.49, I'm wrong!!
Thanks a lot! On 7/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Bear in mind 'ip policy route-map BLAH' has no effect on self generated > packets. > > In your test, are the packets matching the ACL sourced from 172.20.0.49 > (router itself) or 172.20.0.50? > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of omar parihuana > Sent: 03 July 2007 00:17 > To: nsp > Subject: [c-nsp] PBR Strange behavior > > Hi List, > > I've configured an policy routing, however the packets don't match the > policy. I re-checked the configuration and all seems fine, I don't know > why > that configuration don't work!!! (the packets traverse by default route > and > not by Next-hop configured into route-map. > > I've paste my configuration: > > ! > interface FastEthernet0/0.73 > encapsulation dot1Q 73 > ip address 172.20.0.49 255.255.255.252 > no ip redirects > no ip proxy-arp > ip policy route-map NEXT-HOP > no cdp enable > arp timeout 300 > end > ! > > ! > route-map NEXT-HOP permit 10 > match ip address 160 > set interface Serial1/0:0 > set ip next-hop 172.16.1.134 > ! > > ! > access-list 160 permit ip 172.20.0.48 0.0.0.3 any > ! > > Thanks > > *The router is a Cisco 3640 with CEF Enabled that works like MPLS-PE > router. > > -- > Omar E.P.T > ----------------- > Certified Networking Professionals make better Connections! > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Omar E.P.T ----------------- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
