Fix lost IPv6 connectivity on old Debian Buster images when migrating to routed IP

Reviewed on February 11, 2025

On older Debian Buster images, the installed custom version of cloud-init may interfere with IPv6 connectivity when the Instance transitions to using routed IP. To avoid this, you should install a newer version of cloud-init before the migration to routed IP. This procedure also recovers connectivity for an Instance already using routed IP.

Note

This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our main migration guide and the related FAQ.

Install the new debian-stable PPA. The URL of the PPA may be configured to use the noble series. Replace noble with bionic in the URL.

rm -f /etc/apt/sources.list.d/scaleway-ubuntu-stable-bionic.list
add-apt-repository ppa:scaleway/debian-staging
nano /etc/apt/sources.list.d/scaleway-ubuntu-debian-staging-noble.list

In the file opened with nano, replace noble with bionic.

Install the new version of scaleway-ecosystem and cloud-init. It is important to clean the previous cloud-init data as the new version has a structure that may cause a failure at the next boot.
```
apt update
apt -y install scaleway-ecosystem cloud-init
cloud-init clean
```
Reboot the Instance to apply the changes.
```
reboot
```

Still need help?

Create a support ticket