> Source: [sk155953](https://support.checkpoint.com/results/sk/sk155953)

# sk155953 - IKE packets dropped with "vpn_inbound_policy_chain Reason: vpn inbound nat after vm failed;"

| Property | Value |
|----------|-------|
| Solution ID | sk155953 |
| Date Created | 2019-06-13 |
| Last Modified | 2023-01-03 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81 (EOS) |

## Symptoms

- * IKE packets are dropped with error message:

  ```
  "dropped by vpn_inbound_policy_chain Reason: vpn inbound nat after vm failed;"
  ```

* Kernel debugs `(fw ctl debug -m fw + conn drop && fw ctl debug -m VPN all)` shows:  

  ```
  [cpu_x];[fw4_0];IKE_Utils_FillIKEInfo: setting entry in dynamic_ipsec_source_address table;
  [cpu_x];[fw_0];IKE_Utils_FillIKEInfo: failed to set dynamic_ipsec_source_address table;
  [cpu_x];[fw_0];IKE_Handling_Inbound_ex: Failed to retrieve info from chain;
  [cpu_x];[fw_0];IKE_Handling_Inbound_ex: XXX=============
  ;
  [cpu_x];[fw_0];vpn_nat_inbound_after_vm_ex: Error - (InBound) IKE/RDP address manipulation failed;
  [cpu_x];[fw_0];vpn_inbound_policy_chain: failed in vpn nat after vm inbound;
  ```

## Cause

There is a leak in the "dynamic_ipsec_source_address" kernel table.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk166715)
* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 45
* [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 213
* [Jumbo Hotfix Accumulator for R80.20](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk137592) starting from Take 161
* [Jumbo Hotfix Accumulator for R80.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk116380) starting from Take 278

Check Point recommends to always upgrade to the most recent version   
([upgrade Security Gateway](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=435) / [upgrade Security Management Server](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=184) / [upgrade Multi-Domain Security Management](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doShowproductpage&productTab=overview&product=166)).

<br />

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-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](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

<br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content