Is there any way to change the administrative distance on the reverse-route feature of VPN tunnels? When using reverse-route it installs it as static, which gives it an admin distance of 1 it seems, so makes it very hard to use that as a backup route, when I have a static route pointing to a connected interface on the ASA, which I would like to be primary.
If you do not use reverse route, would a static route take preference?
I guess I would need to use some type of tracking so that if the interface that the static route was pointing to was unavailable, it would pull it out, and than the vpn tunnel would be used.
The connected interface on the ASA goes to a Ethernet leased lined service. I thought of moving the VPN tunnel off of the ASA, and onto some other device, and then I could just have 2 static routes on the ASA, with different admin distances, but was hoping there was a better way.
Thanks for any advice.