diff --git a/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx b/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx index 5ca83f55e0..38157bb234 100644 --- a/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx +++ b/pages/dedibox-hardware/how-to/configure-raid-kvm-h310.mdx @@ -3,7 +3,7 @@ title: How to configure the DELL PERC H310 / H700 / H710 / H730-P / LSI9361 RAID description: This page explains how to configure the DELL PERC H310 / H700 / H710 / H730-P / LSI9361 RAID controller on a Scaleway Dedibox from the KVM tags: dell perc h310 h710 h730 raid controller kvm dates: - validation: 2025-05-03 + validation: 2025-11-05 posted: 2021-07-16 --- import Requirements from '@macros/iam/requirements.mdx' diff --git a/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx b/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx index 4fd1e0d2ee..c97fa24bbb 100644 --- a/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx +++ b/pages/dedibox-ipv6/how-to/configure-ipv6-linux.mdx @@ -16,8 +16,8 @@ import Requirements from '@macros/iam/requirements.mdx' - [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix - Follow the IPv6 on Ubuntu configuration if you are on Ubuntu and use Netplan as your default network manager. - Follow the IPv6 on Linux configuration with systemd-networkd if you are on another Linux distribution or prefer to use directly systemd-networkd on Ubuntu. + If you are running Ubuntu and using Netplan, follow the **Ubuntu (Netplan)** section. + If you use systemd-networkd directly, or run a different Linux distribution, follow the **Linux (systemd-networkd)** section. ## How to configure IPv6 on Ubuntu @@ -27,25 +27,25 @@ It replaces the classical network configuration with new configuration files, wr 1. Open the default configuration file `/etc/netplan/01-netcfg.yaml` in a text editor, and edit it as follows: ```yaml - # This file describes the network interfaces available on your system - # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: enp1s0: - dhcp4: no - dhcp6: no + dhcp4: false + dhcp6: false addresses: - - "aaa.bbb.ccc.ddd/24" # The main IP address of your Dedibox server - - "2001:bc8:xxxx:xxx::x/64" # An IP address from your IPv6 block and its subnet mask /64, replace placeholder values - gateway4: aaa.bbb.ccc.1 # The gateway is the IPv4 address of your Dedibox, ending on .1 - nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) + - "AAA.BBB.CCC.DDD/24" # Dedibox IPv4 + - "2001:bc8:xxxx:xxx::1/64" # Assigned IPv6 + gateway4: "AAA.BBB.CCC.1" routes: - - to: 0.0.0.0 - via: aaa.bbb.ccc.1 + - to: 0.0.0.0/0 + via: "AAA.BBB.CCC.1" on-link: true + nameservers: + addresses: + - "51.159.47.28" # Replace with the DNS server closest to your DC + - "51.159.47.26" ``` Remember to replace `enp1s0` with the proper name of your internet interface. @@ -53,73 +53,100 @@ It replaces the classical network configuration with new configuration files, wr The configuration example above is valid for the main IP address of your Dedibox server. If you want to use IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), remember to use the unique gateway for the failover IPv4. -2. Check and validate your configuration file. - ``` - sudo netplan –debug - ``` -3. Activate the new configuration: +2. Apply and verify the configuration: + ```bash + sudo netplan --debug apply + ``` - sudo netplan apply +3. Verify addressing: + ```bash + ip -4 addr + ip -6 addr + ip -6 route ``` ## How to configure IPv6 on Linux with systemd-networkd -`systemd-networkd` is the network manager of [systemd](https://systemd.io/). It is provided natively on most Linux distributions and can be used for the configuration of IPv6 with its DHCPv6 client feature. +`systemd-networkd` is the network manager of [systemd](https://systemd.io/). +Most modern Linux distributions ship with `systemd-networkd`. +This method is appropriate when you: + +* run distributions that do not use Netplan +* prefer low-level network configuration +* configure containers or VMs manually + +Your IPv6 prefix is routed statically; DHCPv6 is used only for lease negotiation and DUID identification — not for address assignment. + When specifying the IP address of your Dedibox, you need to enter it in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing). The netmask for the main IPv4 of a Dedibox server is `/24`, the netmask for a failover IPv4 is `/32`. The netmask for the IPv6 is `/64`. -1. Run the `ip link show` command to find the name of your public internet interface. Make sure to store it, as it will be required in the next steps. -2. Run the following command to create a backup of the current network configuration and configure `systemd-networkd`: - ``` - sudo mv /etc/systemd/network/eno1.network /etc/systemd/network/eno1.network.bkp - ``` -3. Run the following command to enable `systemd-networkd`. - ``` - systemctl enable systemd-networkd.service - ``` -4. Create a new file called `.network` and open it in a text editor. - ``` - sudo nano /etc/systemd/network/eno1.network +1. Run the `ip link show` command to find the name of your public internet interface (Example: `eno1`). Make sure to store it, as it will be required in the next steps. +2. Create a networkd config file: + ```bash + touch /etc/systemd/network/eno1.network ``` 5. Open the file in a text editor and paste the following content. Make sure to replace the values in the example with your own and save them before exiting the text editor. - ``` + ```bash [Match] - #The name must correspond to your interface name Name=eno1 [Network] + # Static IPv4 and IPv6 assignment + Address=AAA.BBB.CCC.DDD/24 + Address=2001:bc8:xxxx:xxx::1/64 + + Gateway=AAA.BBB.CCC.1 + DNS=51.159.47.28 + DNS=51.159.47.26 + + # DHCPv6 only for PD negotiation DHCP=ipv6 IPv6AcceptRA=yes - # IPv4 of the Dedibox, change netmask to /32 if failover IPv4 - Address=/24 - # IPv6 of the Dedibox - Address=2001:bc8:xxxx:xxx::x/64 - - [Route] - # The IPv4 gateway is either your Dedibox IP ending on .1 (i.e. x.y.z.1) for the physical host or 62.210.0.1 for any VM running on a Dedibox - Gateway= - GatewayOnlink=yes [DHCP] - ClientIdentifier=duid-only + ClientIdentifier=duid DUIDType=link-layer - # Scaleway Dedibox DUID without the DUID-LL "00:03" at the beginning - DUIDRawData= - - [DHCPv6] - UseAddress=no - WithoutRA=solicit + # The Scaleway DUID (without DUID-LL prefix "00:03") + DUIDRawData= [IPv6AcceptRA] + # Required to properly accept Prefix Delegation DHCPv6Client=always - UseOnLinkPrefix=False - UseAutonomousPrefix=False + UseOnLinkPrefix=false + UseAutonomousPrefix=false ``` + + + To retrieve the DUID run the follwoing command: + + ``` + journalctl -u systemd-networkd | grep -i duid + ``` + 10. Run the following command to activate the new configuration. + ```bash + sudo systemctl enable --now systemd-networkd ``` - systemctl start systemd-networkd - ``` +## Additional notes + +### IPv6 addressing + +* Your /48 prefix must be subdivided into /64 networks +* The host config generally uses one /64 per interface + +### CIDR quick reference + +| Type | CIDR | +| --------------------- | ---- | +| Main IPv4 | /24 | +| Failover IPv4 | /32 | +| Single IPv6 subnet | /64 | +| Delegated IPv6 prefix | /48 | + +### DNS servers +Scaleway resolvers vary by datacenter. +Refer to [Scaleway network information](https://www.scaleway.com/en/docs/network/reference-content/scaleway-network-information/) for more information. \ No newline at end of file diff --git a/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx b/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx index 5a9e424013..b4b4b989b5 100644 --- a/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx +++ b/pages/dedibox-scaleway/how-to/configure-failover-ip.mdx @@ -3,7 +3,7 @@ title: How to configure a failover IP on a Scaleway Dedibox description: This page explains configure a failover IP on a Scaleway Dedibox tags: dedibox failover ip failover-ip failover-ip dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2022-04-13 --- import DediboxScalewayMigration from '@macros/bare-metal/dedibox-scaleway-migration.mdx' diff --git a/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx b/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx index a39e95a20d..32e2bfee2f 100644 --- a/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx +++ b/pages/dedibox-scaleway/how-to/configure-reverse-failover-ip.mdx @@ -3,7 +3,7 @@ title: How to configure the reverse DNS of a failover IP on Dedibox description: This page explains how to configure the reverse DNS of a failover IP on Scaleway Dedibox tags: dedibox failover ip flexible-ip failover-ip dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2022-04-13 --- import DediboxScalewayMigration from '@macros/bare-metal/dedibox-scaleway-migration.mdx' @@ -12,7 +12,7 @@ import Requirements from '@macros/iam/requirements.mdx' -You can edit the reverse DNS of a failover IP address to a custom value. This can be useful when you want to send emails from your Dedibox, as certain remote mail servers do not accept emails coming from generic reverse hostnames. +You can configure the reverse DNS (rDNS) of a failover IP address with a custom value. This is particularly useful when sending emails from your Dedibox, as some remote mail servers may reject messages originating from generic reverse hostnames. diff --git a/pages/dedibox-scaleway/how-to/install-dedibox.mdx b/pages/dedibox-scaleway/how-to/install-dedibox.mdx index 2ce028dc85..43975cc7a1 100644 --- a/pages/dedibox-scaleway/how-to/install-dedibox.mdx +++ b/pages/dedibox-scaleway/how-to/install-dedibox.mdx @@ -3,7 +3,7 @@ title: How to install a Dedibox description: This page explains how to install a Scaleway Dedibox tags: dedibox install dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2022-01-31 --- import DediboxScalewayMigration from '@macros/bare-metal/dedibox-scaleway-migration.mdx' diff --git a/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx index 6aa85f387f..c806a23d3a 100644 --- a/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx +++ b/pages/dedibox-scaleway/how-to/reinstall-dedibox.mdx @@ -3,7 +3,7 @@ title: How to reinstall a Dedibox from the Scaleway console description: This page explains how to reinstall a Scaleway Dedibox tags: dedibox reinstall raid dates: - validation: 2025-04-22 + validation: 2025-11-05 posted: 2022-03-24 --- import DediboxScalewayMigration from '@macros/bare-metal/dedibox-scaleway-migration.mdx' diff --git a/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx b/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx index 9620b83804..3d79a7ba0f 100644 --- a/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx +++ b/pages/dedibox-scaleway/how-to/terminate-dedibox.mdx @@ -3,7 +3,7 @@ title: How to terminate a Dedibox subscription from the Scaleway console description: This page explains how to delete your Scaleway Dedibox tags: dedibox link scaleway termination dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2022-02-01 --- import DediboxScalewayMigration from '@macros/bare-metal/dedibox-scaleway-migration.mdx' diff --git a/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx b/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx index a67fb9b673..e20b5f31d6 100644 --- a/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx +++ b/pages/instances/reference-content/choosing-shared-vs-dedicated-cpus.mdx @@ -2,7 +2,7 @@ title: Choosing between shared or dedicated vCPUs description: Find out how to choose between shared or dedicated vCPUs depending on your workloads. dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2025-04-18 tags: instance cpu vcpu shared dedicated --- diff --git a/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx b/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx index 368abda2dd..04828f8170 100644 --- a/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx +++ b/pages/instances/troubleshooting/fix-long-delays-booting-without-public-ip.mdx @@ -3,7 +3,7 @@ title: Fix long delays when booting without a public IP description: This page explains how to avoid long delays when booting a Scaleway Instance without a public IP tags: centos-stream rockylinux almalinux network-manager ipv6 routed ip dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2024-04-17 --- diff --git a/pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx b/pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx index 08353536fb..79e926e710 100644 --- a/pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx +++ b/pages/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx @@ -3,7 +3,7 @@ title: Modifying kernel parameters in a Kubernetes cluster using a DaemonSet description: This guide explains how to modify kernel parameters in a Kubernetes cluster using a DaemonSet tags: kubernetes kernel dates: - validation: 2025-04-30 + validation: 2025-11-05 posted: 2024-10-24 ---