Bug ID 808409: Unable to specify if giaddr will be modified in DHCP relay chain

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 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,,,,,,,,, 14.1.3, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 16.0.0,, 16.0.1

Fixed In:
16.1.0,, 15.1.2,,,

Opened: Jul 23, 2019

Severity: 4-Minor


ID746077 changed the dhcprelay behavior in order to comply with RFC 1542 Clarifications and Extensions for BOOTP. However, as the change also encompasses the DHCP-to-DHCP relay scope, the behavior cannot be configurable with a db key.


You are unable to specify whether giaddr will be changed.


DHCP Relay deployments where the giaddr needs to be changed.



Fix Information

A new sys db tmm.dhcp.relay.giaddr.overwrite is introduced The default is : sys db tmm.dhcp.relay.giaddr.overwrite { value "enable" } On versions with a fix to 746077, the sys db DOES NOT exist and BIG-IP will always retain the source IP On versions with both this fix and ID748333 fix, this fix overrides the fix for 746077. To change the default, set to "disable" to retain

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips