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

# sk101448 - Traffic is originating from a VS (virtual system) with the VSX internal communication address

| Property | Value |
|----------|-------|
| Solution ID | sk101448 |
| Date Created | 2014-07-08 |
| Last Modified | 2025-02-26 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82, R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- Connections that are originating from a Virtual System are using a Source IP address of the VSX internal communication network.
By design, these IP addresses should not be seen on the internal network.

## Cause

A manual "no-NAT" rule or a change to `no_hide_services_ports` in the *table.def*is blocking the required NAT.

In VSX, all interfaces in a Virtual System are assigned an IP address from the VSX Internal Communication Network (192.168.196.0/22). Special NAT is performed by the kernel using the configured addresses from the topology table.

## 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