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

# sk164592 - Stateless NAT46 does not work as expected

| Property | Value |
|----------|-------|
| Solution ID | sk164592 |
| Date Created | 2020-03-19 |
| Last Modified | 2020-03-23 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * After manually configuring stateless NAT46 according to R80.30 Administration Guide, NAT46 does not work as expected .  
  NAT46 use case scenario:  
  \[IPv4 Network\] --- (Internet) --- eth0\[Security Gateway\]eth1 --- \[IPv6 Network\].  
  Adding a static route from IPv4 side to IPv6 side by setting static route 1.1.1.0/24 nexthop gateway logical eth1 on.
* 'fw monitor' is showing the packet in the inbound (i, I) but is not showing it in the outbound (o, O).

## Cause

There was no a valid route entry (static route 1.1.1.0/24 nexthop gateway logical eth1 on ) from IPv4 stack to IPv6 stack. Because IPv6 side does not have IPv4 stack which led to the issue.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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