Bug ID 811033: MRF: BiDirectional pesistence does not work in reverse direction if different transport protocols are used

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0, 14.1.2.5, 13.1.3.4

Opened: Jul 30, 2019
Severity: 3-Major

Symptoms

If a message is routed from one transport protocol (for example TCP) to another transport protocol (for example UDP), messages traveling from the destination to the source of the persistence entry are incorrectly delivered to the destination.

Impact

Messages are forwarded to an incorrect endpoint.

Conditions

-- A message is routed from one transport protocol (for example TCP) to another transport protocol (for example UDP). -- Messages are traveling from the destination to the source of the persistence entry.

Workaround

None.

Fix Information

For all bi-directional persistence records the transport protocol of the connection is not used in the key used to store the record.

Behavior Change