Someone already seen the ASA inserting a wrong route in one connection that was established with it? I'll explain more below:
I've using a Reverse Route Injection. When a Remote Access with IPSEC (CLIENT) connects in the appliance ASA, the ASA create a static route to this Remote Access pointing to the router more near for the ASA to come to this Remote Access. This route is distributed on OSPF. Ok it may be a normal situation. But, the problem is when I ask to another participant from this OSPF area, what is the route to this Remote Access (CLIENT), the answer is to the router more near for the ASA and don't to the ASA. Someone have a solution for this? I've tried create a route-map but didn't work.
I'm sorry if I'm not understanding you, but in your diagram it indicates that the .100 address is the next hop towards the VPN client from the ASA.
Sorry, but I don't understand what you are referring to when you say you are only using one interface. How is your configuration different from the one in the RRI URL that I referenced?
The RRI creates a static route that points to the next hop on the interface to which the crypto map is applied. Have you applied the crypto map to your inside interface?
You're saying that the static route created by RRI on the ASA is pointing to the inside of your network instead of the outside?
Here is an example of using RRI on the ASA. Perhaps it will help you to determine the cause of this problem.
If I understand your question, my question to you is whether the OSPF route to the remote VPN client is sourced by the ASA or by another device?
Is the IP address in the space that I wrote ASA_ROUTER_ID the router ID of the ASA or is it the router ID of another device? What I listed below is an example of the output of "show ip route". The bolded value should be the ASA's router ID if it is originating the route to the VPN client. The other OSPF routers will forward packets destined for the VPN client to the ASA.
#sh ip route 220.127.116.11
Routing entry for 18.104.22.168/24
Known via "ospf 1", distance 110, metric 310, type intra area
Last update from 22.214.171.124 on GigabitEthernet0, 2w ago
Routing Descriptor Blocks:
* 126.96.36.199, from ASA_ROUTER_ID, 2w ago, via GigabitEthernet0
Route metric is 310, traffic share count is 1