AnsweredAssumed Answered

R77.30 VPN to AWS - Manually defined encryption domain (subnet clash)

Question asked by Denis Clancy on Jan 19, 2018
Latest reply on Jan 22, 2018 by Denis Clancy

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

How to configure IPsec VPN tunnel between Check Point Security Gateway and Amazon Web Services VPC using static routes 

 

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.

Outcomes