You give us the information about the ASA and how it is configured to generate the default route. And that looks ok to me. It would help us a lot to understand the problem if you told us whether the routing table on your inside router has the default route or not.
I do see one thing that is problematic. I see configuration statements about network 192.168.20.0 for NAT and split tunnel. But I do not see anything that tells the ASA where network 192.168.20.0 is. I believe that you need a route statement that tells the ASA to use the inside interface to get to that network.
Thank you for posting back to the forum and indicating that you had solved the problem and what the problem was. It makes the forum more useful when people can read about a problem and can read about what solved the problem. This is a somewhat unusual and interesting problem. If I had asked you about the routing table on the ASA we would have figured out that the route was already in the routing table. I am not used to running a routing protocol on the firewall and did not think of this possibility. I hope I will remember this next time something like this comes up.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...