Bug ID 676518: BIG-IP in a DHCP relay chain does not replace the DHCP server details in the DHCP OFFER packet with its own details.

Last Modified: Apr 28, 2025

Affected Product(s):
BIG-IP LTM, PEM(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, 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, 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, 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

Opened: Aug 01, 2017

Severity: 3-Major

Symptoms

DHCP renew and DHCP release packets from the DHCP client will fail if going through the BIG-IP.

Impact

DHCP client may lose its IP address and would need to go through the DHCP request process again. Subscribers on this device derived through DHCP may go down if the DHCP renew packet is not snooped.

Conditions

BIG-IP with a DHCP virtual in relay mode needs to be the last relay before the DHCP server in a DHCP relay chain.

Workaround

Add a catch-all UDP virtual on the DHCP client side VLAN.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips