@@ -37,6 +37,39 @@ In an IPv6-enabled network:
3737 provider. In such environments, IPv6 must be deployed in a dual-stack
3838 configuration.
3939
40+ IPv6 Address Assignment and Routing
41+ ====================================
42+
43+ In Shared Networks, IPv6 address assignment and routing are provided by the upstream network infrastructure, not by the CloudStack Virtual Router.
44+
45+ When IPv6 is enabled on a Shared Network:
46+
47+ - Instances automatically generate a link-local IPv6 address.
48+ - IPv6 global or ULA addresses are typically assigned via:
49+
50+ - SLAAC (Router Advertisements) from the upstream router, or
51+ - An external DHCPv6 server (if present in the upstream network).
52+
53+ - CloudStack does not provide DHCPv6 services in Shared Networks via the Virtual Router.
54+
55+ Important Notes
56+ ~~~~~~~~~~~~~~~
57+
58+ - In Shared Networks, the Virtual Router does not act as the IPv6 gateway.
59+ - IPv6 default routing is determined entirely by upstream infrastructure.
60+ - CloudStack does not control IPv6 Router Advertisements in Shared Networks.
61+ - IPv6-only Shared Networks using the Virtual Router provider are not supported.
62+
63+ Operational Implications
64+ ~~~~~~~~~~~~~~~~~~~~~~~~
65+
66+ For IPv6 to function correctly in a Shared Network:
67+
68+ - The upstream network must advertise the IPv6 prefix using Router Advertisements (SLAAC), or
69+ - An external DHCPv6 server must be present.
70+ - The upstream router must provide the IPv6 default gateway.
71+ - CloudStack will not automatically generate or manage IPv6 gateway functionality in this mode.
72+
4073IPv6 is supported only on KVM and XenServer hypervisors. The IPv6
4174support is only an experimental feature.
4275
0 commit comments