Skip to main content
Each VPS receives an IPv6 allocation equivalent in size to a /64. The gateway is on the location’s shared /48 network, so configure your assigned address with a /48 prefix and use the gateway shown in the control panel.
The /48 setting does not give you the whole location’s address range. Use only your assigned allocation. You may configure up to 20 stable IPv6 addresses at the same time. Rotating or random-address IPv6 proxy services are prohibited by the AUP.

​
Find your IPv6 settings

Open Services → My Services, select your VPS, then open Network. The IPv6 Configuration section is below IPv4 Configuration.
EDBB Network tab overview showing the IPv4 and IPv6 configuration sections

Open Network to find your assigned IPv6 range and gateway. Addresses shown are examples.

Copy the IPv6 assignment and Gateway from your own panel. The Prefix column describes the assigned range; the note below the table explains the prefix to configure inside your operating system.
Closeup of IPv6 assignment, prefix and gateway, with the required /48 configuration note highlighted

Your assigned range is /64 equivalent. Configure an address from that range with /48 to reach the gateway. Example addresses shown.

Open the VNC console before changing networking. The following examples use documentation addresses and eth0. Replace them with an address from your allocation, your location’s gateway and the actual interface name. Check your IPv6 firewall rules as well; IPv4 rules do not automatically cover IPv6.

​
Test the settings on Linux

Check what is already configured:
If the address and default route are missing, add them:
Do not add a duplicate address or default route. If a wrong route is already present, review the saved configuration before replacing it. Test your actual gateway and an external IPv6 destination:
A filtered ping does not prove connectivity is broken. See IPv6 troubleshooting for DNS, route and application checks.

​
Keep the settings after a reboot

Temporary ip commands disappear after a reboot. Back up the configuration and use the network manager already controlling the interface. Keep all working IPv4 settings.
Edit the active file in /etc/netplan/. Append your IPv6 address to the existing addresses list and the IPv6 default route to routes. Preserve the existing IPv4 entries and other settings.The relevant additions look like this; they are not a complete replacement file:
Check the YAML, then test with rollback available:
Test IPv4 and IPv6 from a second connection before confirming. If the attempt rolls back, verify the previous settings were restored.
After a planned reboot, repeat the address, route and connectivity checks. If a generated configuration overwrites your changes, update the tool that generates it, such as Cloud-Init, instead of maintaining a competing file.