Bug ID 621465: The minimum IP packet fragment size is now 1 and not 24

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2

Fixed In:
11.5.4 HF3

Opened: Oct 08, 2016
Severity: 3-Major

Symptoms

The minimum IP packet fragment size, set via DB Var [TM.MinIPfragSize], is 24 and that causes problems if you need to use smaller fragments in your network.

Impact

You are unable to configure fragment sizes smaller than 24 in your network.

Conditions

You are trying to configure TM.MinIPfragSize and need it to be set to a value smaller than 24.

Workaround

NA

Fix Information

Changed DB Var [TM.MinIPfragSize] minimum value from 24 to 1.

Behavior Change