Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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
Opened: May 06, 2019 Severity: 3-Major
When reusing a serverside TIME_WAIT connection, the BIG-IP system: -- Establishes the new connection if clientside/serverside connections are on the same TMM. -- Sends a RST 'Unable to obtain local port' if clientside/serverside connections are on different TMMs.
BIG-IP system behavior is inconsistent. In one case, BIG-IP establishes the connection. In the other case, BIG-IP resets the connection.
This happens in two scenarios: Scenario 1: -- A new serverside connection is requested that matches an existing TIME_WAIT connection (e.g., by using source-port preserve-strict in the virtual server) -- Clientside/serverside connections are on the same TMM. Scenario 2: -- Clientside/serverside connections are on different TMMs.
None.
BIG-IP system reuses serverside TIME_WAIT connections irrespective of clientside/serverside being on the same TMM/different TMMs.