Last Modified: Oct 16, 2023
Known Affected Versions:
14.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.2, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.0.0, 15.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Jul 17, 2019 Severity: 3-Major
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.
If there is no route available to reach the destination, NAT64 packets are dropped.
-- Virtual server with LTM pool configured. -- CGNAT LSN pool configured. -- Translate-address disabled.
Configure default gateways/routes to reach the IPv4 destination in NAT64 case.
Aligned the behavior of NAT44 and NAT64 when translate-address is disabled under Virtual Configuration with LTM Pool and LSN Pool. Use LTM pool as next hop for L2 forwarding the NAT64 packets when translate-address is disabled.