- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- R77.30 VPN to AWS - Manually defined encryption do...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R77.30 VPN to AWS - Manually defined encryption domain (subnet clash)
Hi Folks,
I was hoping you could help me out with a query. I'm in the process of setting up a VPN to Amazon AWS. Following the checkpoint guide below.
Solution ID: sk100726
I had a question around the statement below:
What needs to be done in the instance that a local network that will be served by the AWS VPN is already defined manually as part of another existing VPN domain on the R77.30 cluster?
I am unable to remove it from the existing VPN domain as per the instruction because the local subnet will continue to require access via the existing VPN.
Thanks in advance guys.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can try some of the solutions listed here:
Troubleshooting Overlapping Encryption Domains Issues
If I recall correctly, I've used some crazy NAT rules to phantom objects to overcome similar issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can try some of the solutions listed here:
Troubleshooting Overlapping Encryption Domains Issues
If I recall correctly, I've used some crazy NAT rules to phantom objects to overcome similar issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank Vladimir, I'll dig through that article.
Denis
![](/skins/images/A53DAF99EDBAFE11A1FC6E62F510C235/responsive_peak/images/icon_anonymous_message.png)