Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:dpi_components:platform:dpi_ipv6:start [2023/10/10 08:25] – external edit 127.0.0.1 | en:dpi:dpi_components:platform:dpi_ipv6:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== IPv6 support ====== | ||
| - | {{indexmenu_n> | ||
| - | IPv6 support is activated by setting | ||
| - | < | ||
| - | 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 | ||
| - | < | ||
| - | 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 (" | ||
| - | 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 " | ||
| - | |||
| - | In this case, you will need to change the configuration, | ||
| - | |||
| - | < | ||
| - | mem_ipv6_tracking_ip=16000000 | ||
| - | </ | ||
| - | |||
| - | :!: IPv6 support requires additional memory and CPU resources, so if you don't provide IPv6 addresses to subscribers, | ||