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.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...