Bug ID 668459: Asymmetric transparent nexthop traffic only updates ingress interface

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,, 15.0.0, 15.0.1,,,,

Fixed In:

Opened: Jun 08, 2017
Severity: 3-Major


When transparent nexthop traffic from server to client uses a different VLAN group than client-to-server traffic, the server-to-client traffic is sent out the VLAN group that handles the client-to-server traffic. The destination MAC address on the server-to-client traffic is preserved even though the VLAN group is not.


Return traffic may be transmitted on a VLAN group with a destination MAC that does not match any host on that group.


-- Transparent nexthop virtual server configured. -- VLAN-keyed connections disabled. -- Asymmetric traffic between two VLAN groups.



Fix Information

When vlan-keyed connections is disabled and transparent nexthop is in use, each packet received will be sent the VLAN group which received it, even if this doesn't match the VLAN group passing traffic in the other direction. This is preferred behavior.

Behavior Change