When my router A routes locally generated icmp packets (local PBR) it always puts ip address of it's interface fa1 as the source address for those PBR routed packets. Traffic is policy routed trough tunnel interface 0 using next hop of router's B tunnel interface 0. This is what I want to accomplish and it works, but I noticed that router A always generates packets with source IP address of its fa1 interface. Now, I'm curious why is that so...
Router A: int fa1 ip add 10.0.0.2 ! int vlan 2 description GRE tunnel source ip add 10.0.0.10 crypto-map vpn ! int tunnel 0 description GRE with router B ip add 126.96.36.199 tunnel-source vlan 2 tunnel-destination 10.0.0.14 ! ip route 0.0.0.0 0.0.0.0 fa1 ip local policy route-map tracker ! route-map tracker permit match ip add 171 set ip next-hop 188.8.131.52 - this is IP of tunnel interface on router B ! access-list 171 permit icmp any host 184.108.40.206 echo
Router B config is irrelevant because debug ip policy on router A shows that there is always fa1 ip address used as the source for locally generated traffic. Now if I want to be able to ping 220.127.116.11 from router A I need to put static route to router's A fa1 interface address on router B which is something that I would like to avoid.