From: Timothy Ouellette (timoue@cogeco.ca)
Date: Mon Oct 14 2002 - 09:20:24 GMT-3
Can't find any doco on this issue. Can anyone help?
R1------ethernet-------R2
r1 has a loopback 1.1.1.1/24, r2 has a loopback 2.2.2.2/24, ethernet
between them is 172.16.1.x/24 (.1 for R1, . 2 for R2)
r1 has a static route for r2's loopback (2.2.2.2/24) pointing to the
ethernet ip (172.16.1.2) of r2 and can successfully ping it!
I tried to put a "ip local policy" on r2 rather than a static so that r2
can get to the loopback of r1.
I applied the local policy, created my route map using an extended ACL
saying "any" to "host 1.1.1.1" and I "set ip next-hop 172.16.1.1" of
the ethernet address of r1
I did a debug ip policy, and sent some pings. For some reason, r2
sourced it's pings from 2.2.2.2 (it's loopback). I thought it would
source it from the ethernet ip as any other packet.
when I changed it from source=any destination=1.1.1.1 to
source=172.16.1.2 (r2's ethernet), the policy route broke and was
normal forwarded per debug ip policy
from what I hear, or assume, when do do policy routing. It uses the
lowest loopback on the router as the source.
Can anyone confirm?
Tim
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:46 GMT-3