SD-WAN stops enforcing rules that use "My VPN Domain" or "Peer VPN Domain" objects

Product: SD-WAN
Version: R81.20, R82, R82.10
OS: Gaia
Last Modified: 2026-05-26

Symptoms

• After enforcing an SD-WAN policy, VPN traffic no longer passes.
• Running fw ctl zdebug + drop shows the following drop log:

dropped by vpn_drop_and_log Reason: Failed to process the first VPN packet

• The command dynamic_objects -l shows that the My_VPN_Domain and Peer_VPN_Domain dynamic objects are not populated.

Solution

This problem was fixed. The fix is included in:

• Jumbo Hotfix Accumulator for R82.10 starting from Take 19
• Jumbo Hotfix Accumulator for R82 starting from Take 103

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

Workaround

As a temporary workaround, modify SD-WAN rules to use static encryption domain group objects in the source and destination columns instead of "My VPN Domain" or "Peer VPN Domain".

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General
Status: Approved by TAC
Date Created: 2026-04-27
Last Modified: 2026-05-26