This guide describes how to turn off IPsec anti-replay protection on a Check Point Security Gateway for use with Cloudflare WAN anycast IPsec tunnels, and how to validate, troubleshoot, and roll back the change.
Cloudflare recommends turning off anti-replay protection for Cloudflare WAN anycast IPsec tunnels. For an explanation of why, and for security considerations, refer to Anti-replay protection.
If anti-replay protection is turned on in Check Point but turned off in Cloudflare, Check Point drops IKE and IPsec traffic. Connectivity through the tunnels is inconsistent, and the Check Point logs show IKE drops with the following message:
Encryption failure: Warning - possible replay attackFor help with tunnel instability or packet drops, refer to Troubleshoot tunnel health.
This interim procedure was developed with Check Point Support.
This procedure was tested with the following Check Point software versions:
- SmartConsole: R82.10 (82.10.9900.426)
- Check Point Security Management: R82.10 Jumbo Hotfix Take 24 (Gaia — Open Server Platform)
- Check Point Security Gateway: R82.10 Jumbo Hotfix Take 24 (Gaia — Open Server Platform)
Before using this procedure, confirm the following for your deployment:
- Security Gateway and Management Server versions and hotfix levels.
- Which other VPN communities or peers on the gateway will be affected by turning off anti-replay globally.
GuiDBedit exposes advanced properties that are not available in SmartConsole. Before you proceed, read sk13009 - Check Point Database Tool (GuiDBedit Tool) ↗︎ and the Check Point documentation for your version for complete details on how to use GuiDBedit.
Complete these prerequisites:
- Schedule a maintenance window. Resetting the tunnels can interrupt traffic and other VPN tunnels.
- Obtain out-of-band or console access to the affected gateway.
- Back up the Security Management Server or Multi-Domain Security Management Server and verify the backup completed successfully. Refer to sk54100 - How to back up your system ↗︎.
- Record the existing value of
disable_replay_checkand the affected gateway object name. - Record the Cloudflare peer IP addresses and current IKE/IPsec SA state.
- Capture the current tunnel health, packet-loss symptoms, and relevant logs.
- Close SmartConsole before you open GuiDBedit. Keep SmartConsole closed until you exit GuiDBedit.
-
Confirm SmartConsole is closed. Do not open SmartConsole again until you exit GuiDBedit.
-
Open
GuiDBedit.exefrom the installed SmartConsole version and build:C:\Program Files (x86)\CheckPoint\SmartConsole\{VERSION}\{BUILD}\GuiDBedit.exeReplace
{VERSION}and{BUILD}with the installed SmartConsole version and build (visible in SmartConsole under Help > About), for exampleR82.10\82.10.9900.426. -
Go to Network Objects > network_objects.
-
Locate the object for the affected Check Point Security Gateway, for example
chkp-sgw. -
Select the gateway record under Object Name.
-
Press Ctrl+F and search for
disable_replay_check. Select Find Next until you reach the exactdisable_replay_checkproperty on the selected Security Gateway object. Other configuration elements may contain similar anti-replay references and must not be changed. -
Record the existing value. The default is
false, but prior administrative changes may have set it otherwise. -
Double-click
disable_replay_checkand set the value totrue.
-
Select File > Save All, or select the disk icon in the toolbar.
-
Select File > Exit and confirm GuiDBedit exits cleanly.
-
Open SmartConsole. Do not open GuiDBedit again while SmartConsole is open.
-
Install policy on the affected Security Gateway.
If directed by Check Point Support, right-click the gateway in the Install Policy window and select Do not use Install Policy Acceleration for all targets. This forces a full policy compilation and installation.
-
Confirm the policy installation completes successfully.
-
Use TunnelUtil (
vpn tunnelutilorvpn tu) ↗︎ to delete the IKE and IPsec SAs on the Security Gateway:-
Connect to the Security Gateway via SSH.
-
Enter expert mode (
expertfollowed by the expert password). -
Run
vpn tuto run the utility interactively. -
Select option
1(List all IKE SAs) to display active IKE SAs. -
Select option
2(List all IPsec SAs) to display active IPsec SAs. -
Delete the Phase 1 (IKE) and Phase 2 (IPsec) Security Associations to force the tunnels to re-establish. Choose one of the following:
- Option
7— delete IKE and IPsec SAs for a specific peer (preferred when only the Cloudflare tunnels need to renegotiate). - Option
0— delete IKE and IPsec SAs for all peers and users (interrupts every VPN peer on the gateway).
Using
vpn tunnelutilto delete the Phase 1 and Phase 2 SAs forces the tunnels to renegotiate. Deleting the SAs removes the need to restart firewall services on the Security Gateway. - Option
-
From Expert mode on the affected Security Gateway, verify the installed local object definition:
grep -n "disable_replay_check" "$FWDIR/database/myself_objects.C"Expected value:
:disable_replay_check: (true)If the value remains false:
- Close SmartConsole.
- Open GuiDBedit and confirm the property was changed on the correct Security Gateway object.
- Save and exit GuiDBedit.
- Reopen SmartConsole and reinstall policy.
- Repeat the verification command.
The configuration-file check confirms that the setting was installed. It does not, by itself, prove that packet drops have stopped.
Anti-replay protection is turned off on Cloudflare IPsec tunnels by default. It may have been turned on when you first deployed your Check Point IPsec tunnels. You can safely turn it off after you change disable_replay_check from false to true and apply the change on the Check Point side.
Replay protection is configured per IPsec tunnel. Repeat these steps for every IPsec tunnel that terminates on the affected Check Point Security Gateway. A tunnel left with replay protection turned on can continue to cause packet drops.
- Log in to the Cloudflare dashboard ↗︎ and go to Networking > Connectors > IPsec/GRE tunnels.
- Find the IPsec tunnel that terminates on the affected Check Point Security Gateway and select Edit.
- Go to Security settings.
- Set Turn on replay protection to off.
- Save your changes.
- Repeat steps 2-5 for every other IPsec tunnel that terminates on the same Security Gateway.
- Confirm the IKE and IPsec SAs re-establish for each Cloudflare peer.
- Confirm bidirectional traffic passes through each tunnel.
- Confirm the Cloudflare dashboard reports the expected tunnel health.
- Compare packet loss and application behavior with the pre-change baseline.
- After you apply the changes on both Check Point and Cloudflare, confirm the Check Point logs no longer show IKE drops with the message
Encryption failure: Warning - possible replay attack. - Monitor through at least one expected rekey event when practical.
Cloudflare tunnel health can remain degraded briefly after traffic recovers due to health-check hysteresis. Evaluate actual traffic and logs in addition to the dashboard state.
Roll back if policy installation fails, tunnels do not recover, unexpected traffic is affected, or the security impact is unacceptable.
- Close SmartConsole.
- Open GuiDBedit. Do not open SmartConsole again until you exit GuiDBedit.
- Select the same Security Gateway object under Network Objects > network_objects.
- Set
disable_replay_checkto its recorded original value, normallyfalse. - Save all changes and exit GuiDBedit cleanly.
- Open SmartConsole and install policy on the affected gateway.
- Use
vpn tunnelutilto delete the IKE and IPsec SAs, which forces the tunnels to renegotiate. Where possible, delete only the SAs for the affected Cloudflare peers. Deleting the SAs removes the need to restart firewall services on the Security Gateway. - Verify the installed value, tunnel state, traffic flow, and gateway health.
If the management database is damaged or the gateway does not recover, stop the procedure. Use the verified backup to restore the Security Management Server.
Run these commands from Expert mode on the Security Gateway. Commands that delete SAs or turn on kernel debugging can affect production traffic and system performance.
vpn tuCommon interactive options include:
- Option
1: List all IKE SAs. - Option
2: List all IPsec SAs. - Option
7: Delete IKE and IPsec SAs for one peer. - Option
0: Delete IKE and IPsec SAs for all peers and users.
Prefer the peer-specific option. Option 0 interrupts every VPN peer and user, so use it only when you need to renegotiate every SA on the gateway.
References:
- sk33853 - How to use the vpn tu command ↗︎
- Check Point Site-to-Site VPN Administration Guide - vpn tu ↗︎
vpn tu tlistReplace <PEER_IP> with the Cloudflare peer IP address:
vpn tu del <PEER_IP>This deletes the IKE and IPsec SAs for the specified peer. Repeat only for the Cloudflare peers affected by the change.
vpn tu del allRun drop debugging only for the minimum time needed to reproduce the issue. Output can be high-volume on a busy gateway, and fw ctl zdebug can increase CPU load. Avoid running during peak hours on production systems.
fw ctl zdebug + dropPress Ctrl+C after collecting the required output, then explicitly stop kernel debugging:
fw ctl debug 0Resetting kernel debugging options can take time. Confirm debugging is stopped before ending the troubleshooting session.
For assistance with gateway configuration, database recovery, clusters, or VSX, contact Check Point Support:
When contacting Check Point Support, include sanitized gateway and management versions, the affected peer IPs, UTC timestamps, policy installation results, tunnel status, and relevant logs. Never include pre-shared keys or other secrets.
Cloudflare documentation:
- Anti-replay protection
- IPsec tunnel instability or packet drops
- Health checks fail at a low, steady rate
- Configure tunnel endpoints
Check Point documentation: