“Forcing application developers to rewrite legacy IPv4 backend code for IPv6 compatibility takes years. Using A10 ADC NAT-PT translates IPv6 frontend queries to IPv4 backend servers in sub-milliseconds.”

During an enterprise e-commerce platform upgrade at Wipro, executive mandate required enabling dual-stack IPv6 hosting to satisfy global mobile carrier standards.

However, the core billing and transaction backend applications were hardcoded around IPv4 socket addresses (10.150.0.0/16). Rewriting the application code would have delayed the launch by 14 months.

Architecture: Protocol Translation on A10 ADC

We engineered an IPv6-to-IPv4 NAT-PT (Protocol Translation) pipeline on A10 Thunder 3030S ADCs.

1. IPv6 Virtual Server: Listens on public IPv6 address (2406:da00:1::100).
2. NAT64 Stateful Translation: Translates incoming IPv6 SYN packets to internal IPv4 source addresses mapped from an isolated NAT pool (10.200.1.0/24).
3. Legacy IPv4 Real Servers: Application servers receive standard IPv4 traffic on port 443 without any code or network stack changes.

[!NOTE] Ensure A10 ADC health checks query both the IPv6 Virtual Server VIP and the underlying IPv4 real server health monitors (http-get /healthz).

# # A10 ADC CLI Configuration Snippet for NAT-PT Dual-Stack
slb server app-node01 10.150.10.15
  port 80 tcp
  port 443 tcp

slb service-group sg-web-ipv4 tcp
  member app-node01:443

slb virtual-server VIP-IPv6 2406:da00:1::100
  port 443 https
    service-group sg-web-ipv4
    source-nat pool nat-pool-v4
    template client-ssl wildcard-cert-template

The Verdict

Key Takeaway

Use ADC Protocol Translation (NAT-PT) to Decouple Frontend IPv6 Migration from Backend Application Code.

Enabling A10 ADC NAT-PT allows organizations to achieve 100% IPv6 compliance on public endpoints while leaving internal IPv4 backend infrastructure untouched.