Routes remain in routing table after vpn client disconnect
I am facing this issue for my easy vpn server and clients.
My Cisco 3825 has an easy vpn server configuration with an ip pool. When one of the client disconnects and his isakmp and ipsec sa deleted by router itself. The route pointing to the ip pool's ip address is still in routing table!!! This time another vpn client connects and get the same ip pool's ip address. But, this new connected vpn client is located on another interface of the router. So, an extreme problem occur! A route pointing to 2 next hops is created! So bad!
Can another help me? How can I delete the bad route?
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...