Bug ID 510650: BIG-IP MPTCP Checksum calculation might be incorrect.

Last Modified: Nov 23, 2020

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,, 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,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2

Opened: Mar 04, 2015
Severity: 3-Major


RFC 6824 specifies that a data sequence mapping also contains a checksum of the data that this mapping covers, if use of checksums has been negotiated at the MP_CAPABLE exchange. However, the BIG-IP implementation only calculates a checksum for a mapping of a single packet.


The MPTCP checksum may be computed incorrectly and may cause connection failures if MPTCP checksums have been negotiated.


MPTCP checksum enabled by either client or the BIG-IP system.


There is no workaround available if the client cannot disable checksums and sends a checksum covering a DSS mapping larger than a single packet.

Fix Information


Behavior Change