Bug ID 425580: RFC3927 address space (169.254.0.0/16) restriction relaxed

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.2.0, 11.2.1, 11.3.0, 11.4.0

Fixed In:
11.5.0, 11.4.1, 11.3.0 HF8, 11.2.1 HF10

Opened: Jul 18, 2013

Severity: 3-Major

Related Article: K14960

Symptoms

01020062:3: IP Address 169.254.0.5 is invalid, link-local address not allowed.

Impact

169.254.0.0/16 network cannot be used with TMOS for non-management addresses

Conditions

Trying to configure an address in the 169.254.0.0/16 network for any address other than management.

Workaround

None

Fix Information

By setting the confg.allow.rfc3927 database variable to "enable," addresses in the 169.254.0.0/16 range can be configured on a BIG-IP.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips