Additional IPv6 with vRack
Additional IPv6 with vRack-enabled products
Configure public IPv6 connectivity in a flexible way 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 in more flexible way.
Lower latency over native IPv6 networks
Gain on recent provider networks that comes 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 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 given vRack network.
💡 Key benefits
Take the advantage of IPv6 addressing standard with:
- Big address space offering almost endless possibilities of 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 global vRack network, you gain on:
- Flexible configurations across different product lines and region locations
- Ability to setup instant fail-over scenarios for dual-stack (using VRRP)
- Up to 5Gbps of outbound public bandwidth per region
💡 Example architecture
Below, we're presenting example configuration for an IP block announced from RBX region to the Internet, which is then used within vRack for number of hosts and some VMs on them.
Such example configuration presents also subnet delegation (to the VM) and cross-region connectivity approach.
💡 How can I get it?
Since Beta product phase Additional IPv6 can be requested from Control Panel, same way as IPv4 addresses:
☛ Configure it!
Once your Additional IPv6 block is delivered, it will be visible under "Your eligible services" section inside vRack-editing page in Control Panel (or under /vrack/{serviceName}/eligibleServices - for those who prefer to use API).
Adding Additional IPv6 block to your vRack
From now on, you can simply add selected block to your vRack and configure it.
More details on different configuration options can be found in our guide linked here.
Additional information
☒ Known limitations
- Additional IPv6 addresses can only be used with 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 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).
- Customer 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 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 loosing connectivity) when enabled on multiple IP blocks inside 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
📣 Share your feedback!
- Best way to share feedback is using quick feedback form or short feedbacks from Control Panel directly:
- For those, who want to participate in technical discussions, we invite to join our Discord channel (#additional-ip)
- For roadmap evolution or feature requests, you can visit our infrastructure roadmap on OVHcloud Github page
FAQ
Can I move my Additional IPv6 block from one region to another
No. But you can change 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 limitations and use with caution.
Can I delegate prefixes via 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 Additional IPv6 block with VPS server?
No, it's only available via vRack network, so not possible to use with VPS.
Will this product be paid after testing phases?
No, it will stay free of charge.
Today, I already use IPv6 addresses. Can I attach them to vRack network?
Additional IPv6 and it's vRack connectivity is a new product. If you use 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 new product reaches General Availability.
How can I create 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 API call. If you want to be sure your hosts will not reconfigure IPv6 address automatically at any case when Router Advertisements appear, there are two sysctl configurations to be done (for all interfaces or on per-interface basis):
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_ra=0
This way your operating system will not reconfigure interface IPv6 address nor the default routes.
Can I route IPv6 subnets into vlans inside my vRack?
Yes, this is possible but only using a dedicated host. Such host must be connected to 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?
-
Alpha
-
Beta
-
General Availability