Also, realised I'd mentioned above that SITE2 was using 10.0.0.0/16 - They're not, its 10.0.0.0/8 and hence the requirement to NAT our 10.1.1.0/24 subnet as 192.168.40.0/24 for all traffic destined to/from SITE2.
Hi Burtsbees,
Yup, already tried that (adding 10.1.1.0 -> 192.168.40.0 into INTERNAL-OVERLOAD-TO-INTERNET) - Same thing - IPsec works but not overload NAT. (not even an entry logged when I added the log statement)
I'm using a pool because I expect they're going to eventually have a larger...
Hi all,
Have been bashing my head against this for the last couple of days and was wondering if anyone might be able to take a look at the config and point where I might be approaching this wrong...
My current lab is configured as:
Two sites (SITE1/SITE2) connected via a third third router...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.