Bug ID 665972: TFTP_DATA_SETUP/TFTP_DATA_TEARDOWN messages may not be logged if client and server reuse the ports

Last Modified: Oct 17, 2023

Affected Product(s):
BIG-IP TMOS(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.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, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Opened: May 22, 2017

Severity: 4-Minor

Symptoms

TFTP_DATA_SETUP/TFTP_DATA_TEARDOWN messages may not be logged if client and server reuse the ports

Impact

Some TFTP data transfers are not logged.

Conditions

Client and server must reuse the ports quickly for this to occur. When TFTP data transfer is started TMM creates a new flow for it and logs a "TFTP_DATA_SETUP" message if ALG logging is enabled. "TFTP_DATA_TEARDOWN" message is logged when the flow expires. The flow established to transfer the data expires after idletimeout configure in the TFTP profile. While the flow is alive if a new data transfer is initiated between the same client,server and if they use reuse the source,destination ports then TMM will not create a new for this data transfer. The existing flow will be reuse and the log messages will not be logged.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips