Bug ID 709952: Disallow DHCP relay traffic to traverse between route domains

Last Modified: Dec 13, 2023

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

Known Affected Versions:
12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,

Fixed In:
16.0.0, 15.1.10,

Opened: Mar 13, 2018

Severity: 3-Major


DHCP traffic can traverse between route domains, e.g., when working with a route domain with a parent. Under certain circumstances, this is not desired.


The DHCP server side flow might get established to the parent route domain, and will persist even after the route in its own route domain becomes available again.


DHCP relay in use on a route domain with a parent relationship or strict isolation disabled.


There is no workaround at this time.

Fix Information

A db key has been introduced, tmm.dhcp.routedomain.strictisolate, which allows enforcement of route domain traversal if desired/configured.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips