Additional IPv6 with vRack
Additional IPv6 with vRack-enabled products
Configure public IPv6 connectivity flexibly over the hybrid cloud vRack networking environment.
Now available in Beta!
💡 Discover Additional IPv6!
Additional IPv6 enables you to offer services using the next-generation Internet Protocol more flexibly.
Lower latency over native IPv6 networks
Gain on recent provider networks that come with IPv6-native addressing, where IPv4 services may add an overhead.
Dualstack fail-over scenarios
Using VRRP protocol inside a vRack network allows you to create a cluster of high-available setups across different machines or locations for both: IPv4 and IPv6 setups.
Free IPv6 addresses
Lower the cost of your infrastructure at scale!
Hierarchical routing of subnets
With the ability to route subnets over the next-hop IPv6 address, you can now delegate whole ranges to your customers hosted inside a given vRack network.
💡 Key Benefits
Take the advantage of IPv6 addressing standard with:
- Big address space offering almost endless possibilities for addressing internet services
- Reliability and lower latency
- Offers native IP auto-configuration with no need for DHCP (Dynamic Host Configuration Protocol)
Moreover, by configuring it together with our global vRack network, you gain the following:
- Flexible configurations across different product lines and region locations
- Ability to set up instant fail-over scenarios for dual-stack (using VRRP)
- Up to 5Gbps of outbound public bandwidth per region
💡 Example Architecture
Below, we're presenting an example configuration for an IP block announced from the HIL region to the Internet, which is then used within vRack for a number of hosts and some VMs on them.
💡 How can I get it?
Please note that during the Beta stage, the first need is to request an Additional IPv6Â block, which can later be managed over the api.us.ovhcloud.com (under the /vrack section).
☛ Request your free Additional IPv6 /56 block
☛ Configure It!
Additional Information
☒ Known Limitations
- During the Beta stage, you can request an Additional IPv6 block using a survey linked above. Later you will be able to order them (for free) in your Control Panel.
- Additional IPv6 addresses can only be used with the vRack network to operate. This is the biggest difference compared to Additional IPv4 that can also be attached to servers or instances directly.
- Due to the nature of the hierarchical design of IPv6 address space, Additional IPv6 blocks are specific to a region. This means there is no possibility to move them between regions (but you can still re-route them to any other vRack-connected backend).
- Customers can request up to 3 Additional IPv6 blocks (/56) per given location. Such blocks can be attached to different vRack networks in the same location.
- Hierarchical routing is available and allows to route subnets (at the size between /57 to /64) using the next-hop address. Such next-hop address must selected from the first (bridged) /64 subnet of your /56 block.
- Multiple /56 blocks can be routed into your vRack (in multiple locations) but SLAAC can be enabled only on one IPv6 block at a time. It will lead to unpredictable results (including losing connectivity) when enabled on multiple IP blocks inside the same vRack.
📄 Need Help?
- Detailed guide on configuring Additional IPv6 block with your vRack network
- Also, if you want to configure public IPv4 with your vRack network, please check: Configuring an IP block in a vRack
Frequently Asked Questions
Can I move my Additional IPv6 block from one region to another?
No. But you can change the backend server to which such block is pointing from one location to another.
Can I use the same vRack with IP blocks in multiple locations?
Yes, but please check the limitations and use them with caution.
Can I delegate prefixes via a specific host inside my vRack?
Yes, this is possible, but for now, there is no DHCPv6-PD available. Such setup must be defined manually using routed subnets and next-hop addresses.
Can I use an Additional IPv6 block with a VPS server?
No, it's only available via the vRack network, so it is not possible to use it with VPS.
Will this product be paid after the testing phases?
No, it will stay free of charge.
Today, I already use IPv6 addresses. Can I attach them to the vRack network?
Additional IPv6 and it's vRack connectivity is a new product. If you use an IPv6 block connected to your server, you still can use it but not with vRack. If you use legacy vrack1.0 IPv6 services, you will need to migrate into new Additional IPv6 as the old services will be deprecated once the new product reaches General Availability.
How can I create a dual-stack setup within vRack with public IPv6 and IPv4 addresses?
This is the default behavior. Just ensure that Additional IPv6 and Additional IPv4 are located in the same region/location and attached to the same vRack.
I prefer to use manual setup for IPv6 addressing and don't want to use SLAAC IP auto-configuration. How can I disable it?
It is enough to disable SLAAC using an API call. If you want to be sure your hosts will not reconfigure IPv6 address automatically in any case when Router Advertisements appear, there are two sysctl configurations to be done (for all interfaces or on a per-interface basis):
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_ra=0
This way your operating system will not reconfigure the interface IPv6 address or the default routes.
Can I route IPv6 subnets into VLANs inside my vRack?
Yes, this is possible but only using a dedicated host. Such a host must be connected to the native VLAN of vRack, which also has access to other VLANs using QinQ.
Will I be able to keep my Additional IPv6 pool(s) once the product reaches General Availability?
Yes, all IP blocks released during the early stages (Alpha/Beta) will continue to operate once reaching GA.