Bug ID 749051: Traffic match criteria with both IPv4 and IPv6 may not allow any traffic

Last Modified: Oct 27, 2025

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

Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3

Opened: Nov 06, 2018

Severity: 3-Major

Symptoms

When a certain traffic-matching-criteria with both IPv4 and IPv6 in the destination-address-list and source-address-list will not allow traffic.

Impact

Lack of connectivity

Conditions

A mix of ipv4 & ipv6 on a dest-addr-list will only work with a source-addr-list of wildcard ipv4 (0.0.0.0/0) or ipv6 (::/0). It will not work match the listener when both IPv4 and IPv6 are present in the source-address-list For example: source-address-list /Common/ipv4-ipv6-list-wildcard net address-list /Common/list-wildcard { addresses { 0.0.0.0/0 { } ::/0 { } } } needs to replace with net address-list /Common/list-wildcard { addresses { ::/0 { } } } In short: Any source-addr-list, except IPv4 wildcard only OR ipv6 wildcard only, fails if the dest-addr-list has both ipv4 & ipv6

Workaround

Use only one while type of IP address for wildcard

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips