---
title: "Configuring Additional IPs in bridge mode on your virtual machines"
description: "Find out how to configure your virtual machines for access to the public internet"
url: https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/network-bridging
lang: en
lastUpdated: 2026-01-06
---
# Configuring Additional IPs in bridge mode on your virtual machines
:::info
This article is about Additional IPv4 configuration on a public interface. You can also configure IPv6 addresses on your virtual machines using [this guide](/en/guides/bare-metal-cloud/dedicated-servers/configure-an-ipv6-on-a-vm.md).
Please note that Additional IP addresses can also be configured in a vRack (private network), which allows interconnection over a wide range of OVHcloud services, offering more flexibility.
Learn how to configure Additional IP addresses in a vRack with our guides for [IPv4](/en/guides/bare-metal-cloud/dedicated-servers/configuring-an-ip-block-in-a-vrack.md) and [IPv6](/en/guides/bare-metal-cloud/dedicated-servers/configure-ipv6-in-vrack.md).
:::
## Objective
Bridged networking can be used to configure your virtual machines. Some tweaking is necessary to make the network configuration work on our network.
## Requirements
- A dedicated server with a hypervisor installed (e.g. Citrix Xen Server, Proxmox, etc.)
- At least one [Additional IP address](https://www.ovhcloud.com/en-gb/network/additional-ip/) routed to the server.
***
### OVHcloud Control Panel Access
- **Direct link:** Public IP
- **Navigation path:** Network > Public IP Addresses
***
:::warning
This feature might be unavailable or limited on servers of the [**Eco** product line](https://eco.ovhcloud.com/en-gb/about/).
Please visit our [comparison page](https://eco.ovhcloud.com/en-gb/compare/) for more information.
As of May 2025, this guide can be used for servers of the [Scale](https://www.ovhcloud.com/en-gb/bare-metal/scale/) and [High Grade](https://www.ovhcloud.com/en-gb/bare-metal/high-grade/) ranges.
Alternatively, to configure Additional IPs using in routed mode or in a vRack, please refer to [Configuring the network on Proxmox VE on the High Grade & Scale ranges](/en/guides/bare-metal-cloud/dedicated-servers/proxmox-network-hg-scale.md) or [Configuring the network on Windows Server with Hyper-V on the High Grade & Scale ranges](/en/guides/bare-metal-cloud/dedicated-servers/hyperv-network-hg-scale.md).
:::
## Instructions
The basic steps are always the same, independent of the underlying system:
- creating a virtual MAC address for an [Additional IP](https://www.ovhcloud.com/en-gb/network/additional-ip/)
- creating a VM on a host
- setting the MAC address of the VM to that new virtual MAC address
- configuring the **IP address**, **netmask**, **gateway** and **route to the gateway** inside the VM
Code samples in the following instructions have to be replaced with your own values:
- SERVER\_IP = The main IP address of your server
- ADDITIONAL\_IP = The address of your Additional IP
- GATEWAY\_IP = The address of your default gateway
### Assign a virtual MAC address
:::warning
In the case of a block of IPs, virtual MAC addresses are created on each individual IP in the block.
:::
You can use the drop-down menu underneath **My public IP addresses and associated services** and select **All Additional IPs** to filter your services accordingly, or directly type the desired IP address in the search bar.
Next, locate your Additional IP address in the table and click the `⁝
` button to open the menu. Select `Add a virtual MAC
`.
Choose `ovh
` from the "Type" drop-down menu unless you are using VMware ESXi - in that case choose `vmware
`. Type a name in the “Name of virtual machine” field, and click on `Confirm
`.
After a few seconds, a virtual MAC will appear in the "Virtual MAC" column of your Additional IP row. This virtual MAC will be required when configuring your VM on the host.
### Determine the gateway address [](#)
To configure your virtual machines for Internet access, you need to know the gateway of your host machine, i.e. your dedicated server.
You can retrieve the gateway address via [your customer area](#viacontrolpanel) or the [OVHcloud API](#viaapi).
**Via the OVHcloud Control Panel**
The IPv4 gateway assigned to your server will appear in the `Network` section of the General Information tab. Once you have copied it, continue with applying the configuration.
**Via the OVHcloud API**
On the [OVHcloud API page](https://eu.api.ovh.com/console/), click on Login in the top right-hand corner. On the next page, enter your OVHcloud credentials.
Execute the following API call, indicating the internal server name (example: `ns3956771.ip-169-254-10.eu`):
🇪🇺EU▾
[GET/dedicated/server/{serviceName}/specifications/network](https://eu.api.ovh.com/console/?section=/dedicated/server&branch=v1#get-/dedicated/server/-serviceName-/specifications/network)
### Prepare the host
:::info
For all operating systems and distributions, you **must** configure your virtual machine with the virtual MAC address you have created in the OVHcloud Control Panel.
:::
**Proxmox**
:::warning
The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the options on the [Qemu/KVM Virtual Machine](https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines) page by Proxmox.
:::
After creating the VM and while it is still powered off, right-click the VM and click `Edit settings`.
1. Select the VM.
2. Open the `Hardware` section.
3. Select `Network Device`.
4. Click the `Edit` button.
Then add the virtual MAC address created previously.
Now you can start the VM and proceed with the [configuration steps](#configurationsteps), depending on the operating system installed.
**VMware ESXi**
:::warning
The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page.
:::
After you've created the virtual machine and while it's powered off, right click the VM and click `Edit settings`.
Fold out `Network Adapter 1`, change the value in the `MAC Address` drop-down menu to `Manual` and enter the virtual MAC address created previously.
Now you can start the VM and proceed with the [configuration steps](#configurationsteps), depending on the operating system installed.
### Configure the virtual machines [](#)
:::warning
Please note that the following examples assume that you are logged in as a user with limited privileges, hence the use of _sudo_ in front of each command. If you are logged in as _root_, you will not need to do this.
:::
:::tip
Select the tab corresponding to your operating system.
:::
**Debian**
By default, the virtual machine's network configuration file is located in `/etc/network/interfaces`.
Once you are connected to the shell of your virtual machine, run the following command to identify your interface name:
```bash
ls /sys/class/net
```
Next, make a copy of the configuration file, so that you can revert at any time:
```bash
sudo cp /etc/network/interfaces /etc/network/interfaces.bak
```
In case of a mistake, you will be able to revert the changes, using the commands below:
```bash
sudo rm -f /etc/network/interfaces
sudo cp /etc/network/interfaces.bak /etc/network/interfaces
```
Edit the file so that it reflects the configuration below, replace `INTERFACE_NAME`, `ADDITIONAL_IP` and `GATEWAY_IP` with your own values.
```bash
sudo nano /etc/network/interfaces
```
```console
auto lo
iface lo inet loopback
# The primary network interface
auto INTERFACE_NAME
iface INTERFACE_NAME inet static
address ADDITIONAL_IP
netmask 255.255.255.255
gateway GATEWAY_IP
```
Configuration example
```console
auto lo
iface lo inet loopback
# The primary network interface
auto ens192
iface ens192 inet static
address 192.0.2.1
netmask 255.255.255.255
gateway 203.0.113.254
```
Save and close the file.
Next, edit or create the file `/etc/resolv.conf`:
```bash
sudo nano /etc/resolv.conf
```
Add the following line:
```console
nameserver 213.186.33.99
```
Save and close the file.
Now you will need to bring your network interface online. To do so, enter the following command (replace `ens192` with your own values):
```bash
sudo ip link set ens192 up
```
Finally, restart your networking service using the following command:
```bash
sudo systemctl restart networking
```
**Red Hat and Red Hat-based operating systems**
CentOS, Rocky Linux 8/9, Alma Linux 8/9, etc.
By default, the virtual machine's network configuration file is located in `/etc/sysconfig/network-scripts/`.
Once logged into your virtual machine shell, run the following command to identify the name of your interface:
```bash
ip a
```
Then make a copy of the configuration file, so that you can go back at any time:
```bash
sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0.bak
```
In the event of an error, you can go back to the beginning using the commands below:
```bash
sudo rm -f etc/sysconfig/network-scripts/ifcfg-eth0
sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0.bak etc/sysconfig/network-scripts/ifcfg-eth0
```
You can then edit this file using the `nmcli` handler, replacing `ADDITIONAL_IP` and `GATEWAY_IP` with your own values.
- Add the IP address:
```bash
sudo nmcli connection modify interface_name IPv4.address ADDITIONAL_IP/32
```
- Add the Gateway:
```bash
sudo nmcli connection modify interface_name IPv4.gateway GATEWAY_IP
```
- Add a DNS server:
```bash
sudo nmcli connection modify interface_name IPv4.dns 213.186.33.99
```
- Change the configuration to manual:
```bash
sudo nmcli connection modify interface_name IPv4.method manual
```
- Make the configuration persistent:
```bash
sudo nmcli con mod interface_name connection.autoconnect true
```
- Reboot your network with the following command:
```bash
sudo nmcli device down interface_name;nmcli device up interface_name
```
For more information on `nmcli`, consult [this page](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/networking_guide/sec-configuring_ip_networking_with_nmcli).
**FreeBSD**
By default, the virtual machine's network configuration file is located in `/etc/rc.conf`.
Once you are connected to the shell of your virtual machine, run the following command to identify your interface name:
```bash
ifconfig
```
Next, make a copy of the configuration file, so that you can revert at any time:
```bash
sudo cp /etc/rc.conf /etc/rc.conf.bak
```
In case of a mistake, you will be able to revert the changes, using the commands below:
```bash
sudo rm -f /etc/rc.conf
sudo cp /etc/rc.conf.bak /etc/rc.conf
```
Edit the file so that it reflects the configuration below, replace `ADDITIONAL_IP` and `GATEWAY_IP` with your own values. In this example, the interface name is `em0`. Replace this value if it does not apply.
```console
ifconfig_em0="inet ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP"
static_routes="net1 net2"
route_net1="-net GATEWAY_IP/32 -interface em0"
route_net2="default GATEWAY_IP"
```
Save and close the file.
Next, edit or create the file `/etc/resolv.conf` and add this line.
```console
nameserver 213.186.33.99
```
Save and close the file, then reboot your virtual machine.
**Ubuntu**
First, disable cloud-init:
```bash
touch /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
```
:::warning
If you want to configure your VM with cloud-init, go to [this page](https://cloud-init.io/)
:::
Add this line to the `99-disable-network-config.cfg` file:
```bash
network: {config: disabled}
```
Then create the network configuration file in `/etc/netplan/` with the following command:
```bash
touch /etc/netplan/00-installer-config.yaml
```
Then apply these permissions on `/etc/netplan`:
```bash
cd /etc/netplan
sudo chmod 600 *.yaml
```
Run the following command to identify the name of your interface:
```bash
ip addr
```
Next, make a copy of the configuration file, so that you can revert at any time. For demonstration purposes, our file is called `00-installer-config.yaml`:
```bash
sudo cp /etc/netplan/00-installer-config.yaml /etc/netplan/00-installer-config.yaml.bak
```
In case of a mistake, you will be able to revert the changes, using the commands below:
```bash
sudo rm -f /etc/netplan/00-installer-config.yaml
sudo cp /etc/netplan/00-installer-config.yaml.bak /etc/netplan/00-installer-config.yaml
```
Next, open the network configuration file:
```bash
sudo nano /etc/netplan/00-installer-config.yaml
```
Edit the file so that it reflects the configuration below, replace `INTERFACE-NAME`, `ADDITIONAL_IP` and `GATEWAY_IP` with your own values.
```yaml
network:
ethernets:
INTERFACE-NAME:
dhcp4: true
addresses:
- ADDITIONAL_IP/32
nameservers:
addresses:
- 213.186.33.99
routes:
- to: 0.0.0.0/0
via: GATEWAY_IP
on-link: true
version: 2
```
Configuration example
```yaml
network:
ethernets:
ens18:
dhcp4: true
addresses:
- 192.0.2.1/32
nameservers:
addresses:
- 213.186.33.99
routes:
- to: 0.0.0.0/0
via: 203.0.113.254
on-link: true
version: 2
```
Save and close the file. You can test the configuration with the following command:
```bash
sudo netplan try
```
If it is correct, apply it using the following command:
```bash
sudo netplan apply
```
**Windows Servers / Hyper-V**
Before configuring your virtual machine, you need to create a virtual switch.
From the command line of your dedicated server, run the following command and note the name of the network adapter that contains the server's main IP address:
```powershell
ipconfig /all
```
In the Hyper-V Manager, create a new virtual switch and set the connection type to External.
Select the adapter with the server’s IP, then tick the option Allow management operating system to share this network adapter.
:::info
This step is only required once for a Hyper-V server. For all VMs, a **virtual switch** is required to connect the VM’s **virtual network adapters** to the server’s **physical adapter**.
:::
Next, select the VM you wish to add the Additional IP to. Use the Hyper-V Manager to change the settings of the VM and shut it down.
Expand the network adapter in the left-hand menu and click on Advanced Features. Change the MAC address to Static, and enter the virtual MAC address for the Additional IP. Once you have entered these settings, press OK to apply the changes.
Next, start the VM and log in as an administrator, then go to the Control Panel's Network and Sharing Center. Click on Ethernet to open the settings and click on the Properties button to view the `Ethernet Properties`.
Select Internet Protocol Version 4 (TCP/IPv4), and then click on the Properties button.
In the IPv4 Properties window, select Use the following IP address. Enter the Additional IP into the IP address field, and enter 255.255.255.255 into the subnet mask.
Fill in your server’s gateway IP address in the appropriate field below and enter 213.186.33.99 into the Preferred DNS Server field.
Finally, click OK, and ignore the warning message about the gateway IP and the assigned IP not being in the same subnet.
After rebooting the server, the VM should be connected to the internet using the Additional IP.
To verify that the virtual machine is fully connected to the Internet, use the following command:
**For Linux**
```bash
ping -c 4 example.com
PING example.com (93.184.215.14) 56(84) bytes of data.
64 bytes from 93.184.215.14 (93.184.215.14): icmp_seq=1 ttl=55 time=29.3 ms
64 bytes from 93.184.215.14 (93.184.215.14): icmp_seq=2 ttl=55 time=24.9 ms
64 bytes from 93.184.215.14 (93.184.215.14): icmp_seq=3 ttl=55 time=30.8 ms
64 bytes from 93.184.215.14 (93.184.215.14): icmp_seq=4 ttl=55 time=27.0 ms
--- example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 24,925/28,028/30,840/2,254 ms
```
**For Windows**
```bash
ping example.com
Pinging example.com [93.184.215.14] with 32 bytes of data:
Reply from 93.184.215.14: bytes=32 time=74ms TTL=50
Reply from 93.184.215.14: bytes=32 time=73ms TTL=50
Reply from 93.184.215.14: bytes=32 time=73ms TTL=50
Reply from 93.184.215.14: bytes=32 time=73ms TTL=50
Ping statistics for 93.184.215.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 74ms, Average = 73ms
```
If you receive a response, this means that the Additional IP has been correctly configured. If not, reboot your virtual machine and retry the ping command.
### Troubleshooting
If you are unable to establish a connection from your VM to the public network and you suspect a networking problem, please reboot the server in rescue mode and set up the bridging network interface directly on the host.
Enter the following command in the rescue mode terminal, in which you replace MAC\_ADDRESS with the vMAC address that you have generated in the Control Panel and ADDITIONAL\_IP with your Additional IP address:
```bash
ip link add name test-bridge link eth0 type macvlan
ip link set dev test-bridge address MAC_ADDRESS
ip link set test-bridge up
ip addr add ADDITIONAL_IP/32 dev test-bridge
```
Next, ping your Additional IP address from an external device.
- If it responds, that probably means that there is a configuration error either on the VM or the host that prevents the Additional IP from working in normal mode.
- If the IP address is still not working, please open a support ticket via the [help center](https://help.ovhcloud.com/csm?id=csm_cases_requests) to relay your test results to our support teams.
## Go further
Join our [community of users](https://community.ovhcloud.com/).