This behavior is observed because, after Open Shortest Path First (OSPF) routes are exchanged and the OSPF table is full, the default route is no longer used to reach the remote peer for VPN.
This problem is caused by Cisco bug ID CSCsc65636.
To resolve this issue, configure a static route on the Adaptive Security Appliance (ASA). The static route must indicate that in order to reach the remote peer, the default gateway of the Internet Service Provider (ISP) must be used.
I am having an issue with incoming rules. Here is my running config. : Saved:: Serial Number: JAD21290D2D: Hardware: ASA5506, 4096 MB RAM, CPU Atom C2000 series 1250 MHz, 1 CPU (4 cores):ASA Version 9.8(1)!hostname ciscoasaenable password $sha512$500...
Question - Where is the "posture requirement policy" from the headend stored on the endpoint? How accessible is it, what security controls do we have to prevent this data from being maliciously used by an attacker if he/she gets access to the endpoint an...
Hello, I have a couple of firewalls on FMC 1000, and two internet routers in front of the firewalls.I have enabled anyconnect VPN and a nat was added to use anyconnect and RA VPN.then i have configured PBR to use one internet link for some vlans and ...