Bug ID 806825: Align the behavior of NAT44 and NAT64 when translate-address is disabled under Virtual Configuration with LTM Pool and LSN Pool

Last Modified: Sep 27, 2019

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 15.0.0, 15.0.1

Opened: Jul 17, 2019
Severity: 3-Major

Symptoms

Configure translate-address disabled under Virtual with LTM pool configured. In the NAT44 case, LTM pool is used as next-hop and packets are L2 forwarded to LTM pool members without destination address translated. In NAT64 case, packets are dropped if there is no route available to reach the IPv4 destinations (derived from original IPv6 destination). Packets are not L2 forwarded to LTM pool members.

Impact

If there is no route available to reach the destination, NAT64 packets are dropped.

Conditions

-- Virtual server with LTM pool configured. -- CGNAT LSN pool configured. -- Translate-address disabled.

Workaround

Configure default gateways/routes to reach the IPv4 destination in NAT64 case.

Fix Information

None

Behavior Change