IPv6 Pass-through

IPv6 will eventually replace IPv4. IPv4 is the current industry standard in TCP/IP networks today and is the de facto Internet routing protocol. IPv6 increases the IP address size from 32 bits to 128 bits, to support more levels of addressing hierarchy. The IPv6 packet header, like the IPv4 packet header, contains a Version part (bits 0 – 4). The packet header tells the network device that the packet is either IPv6 or IPv4. For devices that are not IPv6-compatible (the TCP/IP stack is IPv4), the Version part is the only part that is read by the IPv4 device.

IPv6 packets can pass through the LinkProof device using a VLAN-type IP.

Note	In LinkProof versions prior to LinkProof 3.0, scenarios that involved passing IPv6 packets through the device were configured using Bridge mode with VLAN type OTHER.

The scenario in the following figure shows the following configuration:

Router 2 — For IPv4 device — attached to port G-1 on the LinkProof device.

Router 1 — For IPv6 and IPv4 Traffic — attached to port G-3 on the LinkProof device.

LAN connection — Attached to port G-4 on the LinkProof device.

IPv6 traffic passing inbound or outbound through Router 1 will be bridges across ports G-3 and G-4. This enables traffic to flow from the IPv6 connectivity WAN to the IPv6 server and vice versa, through the LinkProof device.

Figure 3: LinkProof Device with IPv6 Pass-Through

To allow IPv6 traffic to pass through the example LinkProof device

1.	Select Device > VLAN Table. The Virtual Lan Table page is displayed.

2.	Do the following to create a Regular VLAN (bridge) between port G-3 and port G-4.

—	Create a VLAN Port Table that includes VLAN Port Index G-3 and VLAN Interface Index 100001 (type IP).

—	Create a VLAN Port Table that includes VLAN Port Index G-4 and VLAN Interface Index 100001 (type IP).

Notes

>>	If the Regular VLAN is not configured, the IPv6 traffic is discarded.

>>	IPv6 traffic passes through the LinkProof device in Bridge mode (Regular VLAN) only; and the traffic does not participate in routing and/or load-balancing decisions.