I have 2 spokes that get NATed onto the same public IP address. The spokes both get their external IP from the same dhcp pool. Both spokes have separate configs and internal IP ranges and work fine on their own.
#1 works fine, but if #2 is turned on the connection is lost on #1 (vpn light stays on), once #1 recovers (20-40min) #2 loses connection and the game repeats.
I have no control over the dhcp ranges or the NAT router.
Yeah, the way i figure the hub IDs the spokes based on IP. Is there a way around this behavior as I don't have access to the NAT router. I'm going to run into other events in the future where I'm going to be presented with similar provided NAT setups and based on event restrictions (network, space, location, etc) have to use multiple DMVPN routers.
RADIUS and Symantec VIP.
I will use screenshots of ASDM, and at the end I will add the required CLI commands. the diagram below show a diagram of the steps the FW goes through when using 2FA authentication:
As you can see in Fig. 1&nbs...
Unable to get signature update from cisco.com
1. Make sure the router can get name resolution. Configure the router with a proper DNS name server.
ISR4451#utd threat-inspection signature update server cisco username xxxxx password yyyyy