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.
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...