GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: Policy routing - directly connected interfaces [7:45628] posted 06/05/2002
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


my results seem to disagree with your thought.


172.31.1.1 ---- loop0-------router----------WAN----------172.31.5.0 network
                                                 |
                                                 --------------WAN----------
172.31.3.0 network



the route-map I used went something like this

access-list 101 permit ip 172.31.5.0 0.0.0.255 172.31.1.0 0.0.0.255
access-list 101 permit ip 172.31.5.0 0.0.0.255 172.31.3.0 0.0.0.255

route-map filter permit 10
match ip address 101
set interface null0

when I pinged from the 172.31.5.0 net to 172.31.3.0 net, the debug ip policy
showed packets matching the policy and being forwarded to null0

when I pinged from 172.31.1.1 there was no debug generated, and the
172.31.5.0 network received ICMP replies.

that's why I asked the question.


----- Original Message -----
From: ""Kris Keen"" 
Newsgroups: groupstudy.cisco
Sent: Tuesday, 04 June, 2002 8:34 PM
Subject: Re: Policy routing - directly connected interfaces [7:45628]


> You asking if its directly connected would it be switched and not effected
> by policy routing? i think not. To my understanding any packet destined
for
> a remote desination that is directly connected or via a next hop would be
> routed and subject to your policy. This is strange.
>
> Ip local policy will only effect packets orginated by the router, this
> wouldnt effect the directly connected scenario.
> Perhaps you can add another match for packets going to a directly
connected
> interface to be subjected to the policy?
> I'd be intrested to see how you get on
""Kris Keen""  wrote in message
news:200206050334.XAA28497@xxxxxxxxxxxxxxxxx
> You asking if its directly connected would it be switched and not effected
> by policy routing? i think not. To my understanding any packet destined
for
> a remote desination that is directly connected or via a next hop would be
> routed and subject to your policy. This is strange.
>
> Ip local policy will only effect packets orginated by the router, this
> wouldnt effect the directly connected scenario.
> Perhaps you can add another match for packets going to a directly
connected
> interface to be subjected to the policy?
> I'd be intrested to see how you get on




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=45807&t=45628
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to abuse@xxxxxxxxxxxxxx