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

# sk184154 - IPv6 Traffic Blocked by Bridge VS in VSX

| Property | Value |
|----------|-------|
| Solution ID | sk184154 |
| Date Created | 2025-10-10 |
| Last Modified | 2025-10-12 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.10 (EOS) |
| OS | Gaia |
| Platform | Open Server |

## Symptoms

- * IPv6 traffic fails to go through the bridge Virtual System (VS4) in the VSX environment, while IPv4 traffic works as expected.
* IPv6 address can ping the VS1 port but cannot reach the server farm through VS4.
* Packet captures show IPv6 packets arrive on eth2-02 but are not forwarded to eth2-01.
* fw6 monitor shows no output on VS4.
* ICMPv6 Neighbor Solicitation packets are dropped by the bridge interface
* IPv6 debug commands return errors or no output.

## Cause

The registry value FireWallIPv6 for the VS is set to 0, disabling IPv6 kernel modules. This prevents IPv6 traffic and NDP (Neighbor Discovery Protocol) packets from being processed, despite correct configuration in SmartConsole and Clish.

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