scaleway · RoRoJ · Jan 29, 2025 · Jan 28, 2025
@@ -1,13 +1,13 @@
 ---
 meta:
   title: How to activate DHCP on a legacy Private Network
-  description: This page explains how to activate DHCP on a legacy Private Network
+  description: Learn how to activate DHCP for your Scaleway VPC with this step-by-step guide. Ensure seamless IP address management and efficient network configuration.
 content:
   h1: How to activate DHCP on a legacy Private Network
-  paragraph: This page explains how to activate DHCP on a legacy Private Network
+  paragraph: Learn how to activate DHCP for your Scaleway VPC with this step-by-step guide. Ensure seamless IP address management and efficient network configuration.
 tags: regional-private-network private-network vpc virtual-private-cloud dhcp activate old migrate migration
 dates:
-  validation: 2024-07-15
+  validation: 2025-01-28
   posted: 2023-07-06
 categories:
   - network
@@ -26,7 +26,7 @@ We highly recommend activating DHCP on all of your Private Networks, to let us t
 <Message type="important">
 **Activating DHCP is permanent, and there is no way to undo the activation.** <br/><br/>
 
-Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network. Attached resources will receive new dynamically assigned private IP addresses (one IPv4 and one IPv6) from the network's pre-defined CIDR block. The CIDR block will be displayed at the time of activation (see step 5 below), and you will be able to [view your resources' newly assigned IP addresses](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) after activation.
+Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network. Attached resources will receive new dynamically assigned private IP addresses (one IPv4 and one IPv6) from the network's pre-defined CIDR block. The CIDR block will be displayed at the time of activation (see step 5 below), and you will be able to [view your resources' newly assigned IP addresses](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) after activation. These IP addresses do not risk changing unless you detach your resource from the Private Network. You can also use IPAM's [reserve an IP](/ipam/how-to/reserve-ip/) function to reserve a specific IP address, and use that when attaching your resource.
 </Message>
 
 <Macro id="requirements" />

@@ -1,13 +1,13 @@
 ---
 meta:
   title: My Instance is attached to a Private Network but auto-configuration is not working
-  description: This page helps you troubleshoot problems when auto-configuration of your Instance on a Private Network is not working
+  description: Troubleshoot VPC autoconfiguration issues with this guide. Find solutions to common problems and ensure smooth network setup on Scaleway.
 content:
   h1: My Instance is attached to a Private Network but auto-configuration is not working
-  paragraph: This page helps you troubleshoot problems when auto-configuration of your Instance on a Private Network is not working
+  paragraph: Troubleshoot VPC autoconfiguration issues with this guide. Find solutions to common problems and ensure smooth network setup on Scaleway.
 tags: resource instance private-network auto-configuration auto configuration dhcp default-route
 dates:
-  validation: 2024-07-17
+  validation: 2025-01-28
   posted: 2023-07-05
 categories:
   - network
@@ -21,7 +21,7 @@ They leverage helper scripts provided by the `scaleway-ecosystem` package. These
 - When Instances are attached to Private Networks plugged into Public Gateways, make the default route received by DHCP the primary route for all traffic on the Instance
 - Keep the route to the Scaleway Metadata API more specific (see below).
 
-If your Instance does not get auto-configured, it may be that you are using an old version of the `scaleway-ecosyste`m package. `scaleway-ecosystem` version 0.0.4 or later is required. Use the following command to update it:
+If your Instance does not get auto-configured, it may be that you are using an old version of the `scaleway-ecosystem` package. `scaleway-ecosystem` version 0.0.4 or later is required. Use the following command to update it:
 
 - On Ubuntu (Focal and Jammy) or Debian (Stretch and Buster):
 

@@ -7,7 +7,7 @@ content:
   paragraph: This page helps you troubleshoot problems when you have a resource attached to a Private Network, but it has no reserved or configured IP private IP address on the network
 tags: resource instance private-network vpc ipv4 ipv6 ip-address IPAM reserved configured old nics
 dates:
-  validation: 2024-07-15
+  validation: 2025-01-28
   posted: 2023-07-05
 categories:
   - network
@@ -17,6 +17,7 @@ When you attach a resource to a Private Network, the Private Network's built-in
 
 - [Find out how to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network)
 - [Find out how to view your resource's IP address on the Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address)
+- [Find out how to specify the IP address to use when attaching a resource](/ipam/how-to/reserve-ip/)
 
 IP addresses are allocated asynchronously from the attachment of the resource in most cases. The IP will therefore not be immediately returned upon attaching a resource via the API, and there may be a brief delay before it displays in the console, as shown below: