feat(em): networking

Author: bene2k1

pages/elastic-metal/reference-content/elastic-metal-networking.mdx

@@ -15,20 +15,20 @@ categories:
 
 Each Scaleway Elastic Metal server is configured with a single physical Network Interface Card (NIC), pre-configured by default. This NIC handles both public internet traffic and private network communication, sharing the total available bandwidth.
 
-<Lightbox src="scaleway-elastic-metal-networking-schema.webp" size="large" alt="Schema displaying a theoretical network configuration of an Elastic Metal server" />
-
-## Private Networks
+</Message type="note">
+    A second physical Network Interface Card (NIC) might be installed in your server, however it is not in use.
+</Message>
 
-Private Networks are an optional feature that can be enabled per server. For each attached private network, a dedicated VLAN with a private IP is created on the NIC. This setup enables secure, isolated communication between Elastic Metal servers and other resources (e.g. Instances, Load Balancer's) within the same Private Network.
-
-[How to use Private Networks with Elastic Metal servers](https://www.scaleway.com/en/docs/elastic-metal/how-to/use-private-networks/)
+<Lightbox src="scaleway-elastic-metal-networking-schema.webp" size="large" alt="Schema displaying a theoretical network configuration of an Elastic Metal server" />
 
 ## Public bandwidth and flexible IPs
 
 Public bandwidth on Elastic Metal servers is limited by default and typically lower than the maximum capacity of the NIC. It may be increased depending on your server plan and configuration.
 
 A public IPv4 is provided by default with each Elastic Metal server, it is configured by default on the machine after OS installation from the Scaleway console. If you decide to manually install your OS you can the OS let it configure automatically using DHCP.
-The default IPv4 is statically assigned to the physical machine and can not be moved to another Elastic Metal server
+The default IPv4 is statically assigned to the physical machine and can not be moved to another Elastic Metal server.
+
+[How to adjust the available public bandwidth for an Elastic Metal server](/elastic-metal/how-to/adjust-available-bandwidth/)
 
 ### Flexible IPs
 
@@ -39,20 +39,28 @@ There are two scenarios for additional Flexible IPs:
 * Without virtualization: Assign the additional IP directly to the host OS interface. No virtual MAC or interface is required.
 * With virtualization: A virtual interface must be added to the network interface using an hypervisor (e.g. QEMU/KVM), and attached to a single virtual MAC address.
 
-[How to configure a Flexible IP on Elastic Metal](https://www.scaleway.com/en/docs/elastic-metal/how-to/configure-flexible-ip/)
+[How to configure a Flexible IP on Elastic Metal](/elastic-metal/how-to/configure-flexible-ip/)
 
 ### Flexible IPv6
 
 Scaleway supports flexible IPv6 addresses on Elastic Metal servers. These operate similarly to flexible IPv4 addresses and must also be manually configured.
 
-[How to configure a Flexible IPv6 on Elastic Metal](https://www.scaleway.com/en/docs/elastic-metal/how-to/configure-flexible-ipv6/)
+[How to configure a Flexible IPv6 on Elastic Metal](/elastic-metal/how-to/configure-flexible-ipv6/)
+
+
+## Private Networks
+
+Private Networks are an optional feature that can be enabled per server. For each attached private network, a dedicated VLAN with a private IP is created on the NIC. This setup enables secure, isolated communication between Elastic Metal servers and other resources (e.g. Instances, Load Balancer's) within the same Private Network.
+For each 
+
+[How to use Private Networks with Elastic Metal servers](/elastic-metal/how-to/use-private-networks/)
 
 ## KVM public IP
 
 The KVM public IP is the IP address used to access the KVM-over-IP device of the machine.
 This IP address is used to provide remote access to the server in case the machine can't be reached anymore on the public IP or to install a custom OS using the KVM over IP device. It is configured on the same physical NIC but is not visible from the OS.
 The KVM public IP uses a special connection handled by the Baseboard Management Controller (BMC) and Scaleway's internal network.
 
-[How to activate remote access on an Elastic Metal server](https://www.scaleway.com/en/docs/elastic-metal/how-to/activate-remote-access/)
+[How to activate remote access on an Elastic Metal server](/elastic-metal/how-to/activate-remote-access/)