Bug ID 669888: No distinction between IPv4 addresses and IPv6 subnet ::ffff:0:0/96

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Jun 19, 2017
Severity: 3-Major


The BIG-IP does not differentiate between IPv4 addresses (such as and IPv6 addresses in the prefix ::ffff:0:0/96 (such as ::ffff:102:304, also written ::ffff: If you enter such an IPv6 address, the equivalent IPv4 address will be rendered and used.


The BIG-IP system will operate as if you entered the IPv4 address.


Any attempt to use an IPv6 address in that subnet.


No workaround at this time.

Fix Information

The differing addresses now are handled correctly. For most modules, this does not change the functionality at all. AFM is one exception; IPv6 traffic in the ::ffff:0:0/96 subnet will be treated differently than IPv4 traffic.

Behavior Change