https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-to-AWS-DPD-responder/m-p/189788#M34973 <P>This should be safe to do.<BR />If one of your VPN peers requires responder mode, this can be forced per-peer through Guidbedit.</P> Thu, 17 Aug 2023 15:19:03 GMT PhoneBoy 2023-08-17T15:19:03Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-to-AWS-DPD-responder/m-p/189783#M34969 <P>sk108600 VPN Site-to-Site with 3rd party - Scenario 5</P><P>AWS side has DPD enabled. They report issues where two tunnels come up, one initiator and one as responder. The tunnel works fine until it locks up. The remote side has to reset their side to bring back up.</P><P>I am looking at "Passive DPD Responder Mode". This is a registry edit on my Check Point firewalls.</P><P>If I understand correctly, the would allow the Check Point to respond to the AWS side's probing.</P><P>Question: Is this generally safe to enable this registry setting on my gateway without impacting the other IPSec tunnels I have? (which are working)</P><P>I am aware of enabling permanent tunnel and modifying the interoperable device with GuiDBEdit; however that apparently allows my gateway to initiate tunnels to AWS which is the problem I'm trying to solve.</P> Thu, 17 Aug 2023 14:59:13 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-to-AWS-DPD-responder/m-p/189783#M34969 SecNetEng 2023-08-17T14:59:13Z https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-to-AWS-DPD-responder/m-p/189788#M34973 <P>This should be safe to do.<BR />If one of your VPN peers requires responder mode, this can be forced per-peer through Guidbedit.</P> Thu, 17 Aug 2023 15:19:03 GMT https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-to-AWS-DPD-responder/m-p/189788#M34973 PhoneBoy 2023-08-17T15:19:03Z