fix(tuto): update tutorial with more configuration details

Author: bene2k1

tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx

@@ -59,7 +59,7 @@ Once the server has rebooted, the Proxmox web interface is available.
 
 ## Configuring the Private Network
 
-Instead of [configuring the Private Network interface directly from your server's command line](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks), we must configure it using the Proxmox interface.
+Instead of [configuring the Private Network interface directly from your server's command line](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks), it is required to configure it using the Proxmox interface.
 
 1. Click the Proxmox host in the data center menu on the left. The server's dashboard displays.
 2. Click **Network** in the **System** section of the menu. The network dashboard displays.
@@ -69,15 +69,52 @@ Instead of [configuring the Private Network interface directly from your server'
     <Lightbox src="scaleway-proxmox-vlan-details.webp" alt="" />
 
     * **Name**: The name of your primary network interface followed by a dot and the VLAN ID of your Private Network (e.g. `eno1.1918` for the primary network interface `eno1` and the VLAN ID `1918`)
-    * **IPv4/CIDR**: The IP address of the machine in your Private Network followed by its CIDR netmask (e.g. `192.168.1.101/24`)
+    * **(Optional) IPv4/CIDR**: The IP address of the machine in your Private Network followed by its CIDR netmask (e.g. `192.168.1.101/24`). The private IP of your server will be configured through DHCP if IPAM is configured correctly.
     * **(Optional) Gateway (IPv4)**: The IP address of your [Public Gateway](/public-gateways/concepts/#public-gateway), if you want to use one.
     * **Autostart**: Tick this box to automatically bring up the interface during system startup.
 5. Click **Create** to create the Private Network interface.
+6. Click **Apply configuration** to activate the Private Network and to save the configuration.
     <Message type="note">
       Repeat the steps above on each node (in our case, each Elastic Metal server) you want to add to your Private Network.
     </Message>
 
-## Creating a cluster 
+### Network configuration on the console
+
+1. Open the file `/etc/network/interfaces` in a text editor and update any lines generated by Proxmox. Change lines such as `iface eno1.3010 inet manual` to `iface eno1.3010 inet dhcp`.
+2. In the same file, ensure that all lines generated by the Proxmox web UI are placed after the `vmbr0` interface declaration. Failing to do so will prevent both static and DHCP configurations from working correctly.
+3. Save the file and exit the text editor.
+    - Example of a `/etc/network/interfaces` file:
+    ```
+    auto lo
+    iface lo inet loopback
+
+    iface eno1 inet manual
+
+    iface eno2 inet manual
+
+    iface eno3 inet manual
+
+    iface eno4 inet manual
+
+    auto vmbr0
+    iface vmbr0 inet static
+            address 51.159.111.2/24
+            gateway 51.159.111.1
+            bridge-ports eno1
+            bridge-stp off
+            bridge-fd 0
+            hwaddress 44:a8:42:44:38:b4
+
+    # generated configuration that must be after vmbr0 declaration
+    auto eno1.3010
+    iface eno1.3010 inet dhcp
+    ```
+    <Message type="note">
+      If you choose to use DHCP, note that no DHCP client process runs automatically on the newly added interface. To resolve this, either run `dhclient` on the interface manually or reboot the server.
+    </Message>
+
+
+## Creating a cluster
 
 1. Click **Cluster** in the data center view of the Promox interface of your first node. The cluster dashboard displays.
     <Lightbox src="scaleway-proxmox-cluster-overview.webp" alt="" />