weizhouapache commented on issue #8146:
URL: https://github.com/apache/cloudstack/issues/8146#issuecomment-1779795358
> @weizhouapache Thanks for clearing this out! Buying a larger IPv6 range is
definitely not a problem. Another issue I discovered is that I'm still unable
to create a IPv6 network for VPC. Here's what I have:
>
> ```shell
> CIDR4: 10.0.0.64/26
> Gate4: 10.0.0.65
> NetMask4: 255.255.255.192
> CIDR6: 2001:db8:0:1::/64
> Gate6: 2001:db8:0:1::1
> NetMask6: ffff:ffff:ffff:ffff::
> ```
>
> Error: `CloudStack API error 431 (CSExceptionErrorCode: 4350): Can only
support create IPv6 network with a dvance shared network!`
>
> So I can't create IPv6 subnet within VPC, right ? 🙄
@tampler
you may refer to the link
https://docs.cloudstack.apache.org/en/latest/plugins/ipv6.html#isolated-network-and-vpc-tier
```
Here’s the sequence of events when IPv6 is used:
The administrator sets global configuration - ipv6.offering.enabled to true.
The administrator adds a public IPv6 range in an advanced zone.
The administrator adds an IPv6 prefix for guest traffic type for the zone.
The administrator creates a network or VPC offering with IPv4 + IPv6 (Dual
stack) support.
The user deploys an isolated network with the IPv6 supported network
offering. For VPC, user creates a VPC with IPv6 supported VPC offering and then
deploys a network tier with IPv6 supported network offering.
CloudStack assigns a SLAAC based public IPv6 address to the network from the
public IPv6 range of the zone. It also assigns an IPv6 subnet to the network
from the guest IPv6 prefix for the zone. See
[SLAAC](https://datatracker.ietf.org/doc/html/rfc4862)for more information.
The user deploys a guest VM in the network. The VM is assigned a SLAAC based
IPv6 address from the guest IPv6 subnet of the network.
```
also
```
Once a public IPv6 address and guest subnet are assigned to the network or
the network is successfully, the operator must update routing in the upstream
router. For this, CloudStack returns the gateway and subnet for the network
with listNetworks API response.
```
Another option for you is, create a shared network with the IPv6 address
(and dummy IPv4 range), and then attach the VMs in VPC to the shared network.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
