IPv6 support is activated by setting

ipv6=1

in dpi config file

Subscriber Management is optimized for IPv6 fixed size subnets. The size of the IPV6 subnet prefix (issued to the subscriber by default /64) can be changed by setting

ipv6_subnetwork=64

Simultaneous support for subnets that are other than the size specified in the configuration is not yet supported.

A subscriber can simultaneously be given an arbitrary number of IPv4 addresses ("public" and "private") and IPv6 subnets. Special simplified semantics of control commands is provided for subscribers with one IPv4 address and one IPv6 subnet.

SSG will not get started if there is not enough standard resource allocation parameters for ipv6 on servers with high-performance interfaces, giving an error like this "[flow_strg6] Can't allocate start_block : i=1, start_alloc_blocks=2, global_blocks=125"

In this case, you will need to change the configuration, add parameters:

mem_ipv6_tracking_flow=16000000
mem_ipv6_tracking_ip=16000000

IPv6 support requires additional memory and CPU resources, so if you don't provide IPv6 addresses to subscribers, then activating IPv6 support in DPI is not recommended