ipv6 redirect-reverse

Function

The ipv6 redirect-reverse command enables the IPv6 packets and response IPv6 packets to be transferred on the same interface.

The undo ipv6 redirect-reverse command cancels the configuration.

Format

ipv6 redirect-reverse next-hop ipv6-address [ per-packet ]

ipv6 redirect-reverse

undo ipv6 redirect-reverse [ per-packet ]

Parameters

Parameter	Description	Value
next-hop ipv6-address	Specifies the IPv6 address of the next hop. When you run the redirect-reverse command in the view of a GE interface, GE subinterfaces, Eth-Trunk interface, Eth-Trunk subinterfaces, VLAN interfaces, or VXLAN interfaces, you must specify the next-hop ipv6-address parameter. When you run the command in the view of a dialer, tunnel interface, do not specify the next-hop ipv6-address parameter.	-
per-packet	Indicates per-packet sticky load balancing. Only Ethernet interfaces and subinterfaces, Eth-Trunk interfaces and subinterfaces support this parameter.	-

Parameter

Description

Value

next-hop ipv6-address

Specifies the IPv6 address of the next hop.

When you run the redirect-reverse command in the view of a GE interface, GE subinterfaces, Eth-Trunk interface, Eth-Trunk subinterfaces, VLAN interfaces, or VXLAN interfaces, you must specify the next-hop ipv6-address parameter. When you run the command in the view of a dialer, tunnel interface, do not specify the next-hop ipv6-address parameter.

per-packet

Indicates per-packet sticky load balancing. Only Ethernet interfaces and subinterfaces, Eth-Trunk interfaces and subinterfaces support this parameter.

Views

Interface view

Default Level

2: Configuration level

Usage Guidelines

Application Scenarios

The FW uses the incoming interface of the forward packets as the outgoing interface of return packets instead of looking up the routing table.

In the multi-ISP load balancing scenario, the FW looks up the routing table for an outgoing interface to send the return traffic from a server. As a result, the return traffic from the server may take a path on ISP2, although the request to the server takes a link on ISP1. The inconsistent forward and return paths may slow down or even interrupt services. To resolve this issue, configure the sticky load balancing function on the incoming interface of ISP1.

Precautions

If you run the ipv6 redirect-reverse command in the view of a subinterface, you must add the subinterface to a VLAN. Otherwise, the next hop specified in the command does not take effect.

The priority of direct routes is higher than that of the sticky load balancing function. The device preferentially forwards response packets based on direct routes even if the sticky load balancing function is configured.

If equal-cost multipath (ECMP) routes are configured, the sticky load balancing function is enabled by default. In case of non-equal-cost routes, the sticky load balancing function is disabled by default, and you need to run this command to enable the function.

Considering the actual application scenarios, the IPv6 sticky load balancing function does not take effect for IPv6 tunnels (excluding IPv6 over IPv4 GRE tunnels).

Example

# Enable packets to be received by and sent from the same interface, namely, GE0/0/2.

<sysname> system-view
[sysname] interface GigabitEthernet 0/0/2
[sysname-GigabitEthernet0/0/2] ipv6 enable
[sysname-GigabitEthernet0/0/2] ipv6 address 2001:db8:1::1 64
[sysname-GigabitEthernet0/0/2] ipv6 redirect-reverse next-hop 2001:db8:1::2