I'm using a policy (route-map) applied to locally generated packets. Unfortunately IOS doesn't pick to right source ip address ...
Here's my setup :
- Cisco 877 with Vlan1 connected to the lan (10.0.0.1) and ATM0.1 connected to the wan (126.96.36.199)
- Some other router on the lan (10.0.0.2)
The router config (relevant part) :
ip route 0.0.0.0 0.0.0.0 ATM0.1
access list 101 .... some rules ...
match ip address 101
set ip next-hop 10.0.0.2
interface Vlan 1
ip route-cache policy
ip policy route-map mck-vpn
ip local policy route-map special_stuff
What happens is that :
- Lan client sending packet that match the criteria are correctly sent back to 10.0.0.2 and it works fine
- Local packets generated by the router that match the criteria are sent to 10.0.0.2 as well but with the ATM0.1 IP as source instead of Vlan1 ... And that's the issue ...
The 'why' I have to sent some packets to 10.0.0.2 is that they have to be tunnelled and I don't have control over that, I can only change the cisco box. I only don't use the routing table simply because I have other interface than Vlan1 and those need not to use the 'special' route.
Thanks for any insight you might have ... IMHO it doesn's sound logic for the cisco to send packet on Vlan1 that have the ATM0.1 ip as source ...
Based on this statement in one of the previous posts:
Because even if the dns server that must answer this request has an 'internet' ip, it is not directly reachable and must be tunnelled via 10.0.1.32
I would have thought it was an issue for VLANs 2, 3, and 4 as well as VLAN 1. Is there something that makes VLAN 2, 3, and 4 work that does not make VLAN 1 work?