OVH Guide

Network Bridging

Bridged networking can be used to configure your Virtual Machines. Some tweaking is necessary to make the network configuration work on our network.


  • A dedicated server with an hypervisor installed (Ex: VMware ESXi, Citrix Xen Server, Proxmox, etc.)
  • Have assigned a mac to a virtual IP FailOver
  • Knowledge about SSH

The configuration examples keywords in capital letters that you must change for your own values. For example; IP_FAIL_OVER which you must change for your failover IP.

The primary IP of your dedicated server.

The Failover IP you want to configure

Your server IP with the last octet replaced by 254


Step 1 : Determining the gateway

To configure Virtual Machines, you need to know the gateway of your host machine (;;; ...). To do this, you must replace the last octet of the IP address assigned to your server with .254.

You can find the IP of your server in the OVH Manager.

For example:

  • IP of your server : 123.456.789.012
  • Gateway's IP is your server's main IP ending in .254
  • So the gateway's IP is: 123.456.789.254

Step 2 : Applying the configuration

The gateway you need to use in your virtual machine should not be, The IP of your dedicated server or IP failover but you must use the gateway provides for your dedicated server. You must in no case use: sh route add default gw dev eth0 Otherwise you may cut your IP for the virtual server. To determine the correct gateway to use: - IP failover is: YYY.YYY.YYY.YYY - Main IP of your dedicated server: XXX.XXX.XXX.XXX - So the IP of the gateway for your virtual machine (GATEWAY_VM) : XXX.XXX.XXX.254

This gateway will be referred as GATEWAY_VM later in the guide.

Debian & derivatives (Ubuntu, CrunchBang, SteamOS...)

File: /etc/network/interfaces

auto lo eth0
iface lo inet loopback
iface eth0 inet static
    address IP.FAIL.OVER
    broadcast IP.FAIL.OVER
    post-up route add GATEWAY_VM dev eth0
    post-up route add default gw GATEWAY_VM
    pre-down route del GATEWAY_VM dev eth0
    pre-down route del default gw GATEWAY_VM

File: /etc/resolv.conf

nameserver # OVH DNS Server

For Debian 6, dns server configuration is done directly in the file /etc/network/interfaces where you have to find this section:


dns-* options are implemented by the resolvconf package, if installed (default)

dns-nameservers # OVH DNS Server dns-search # For faster hosts resolution on the OVH network ```

Don't hesitate to check this guide provided by Debian for a advanced configuration.

Redhat & derivatives (CentOS 6, Scientific Linux, ClearOS...)

File: /etc/sysconfig/network-scripts/ifcfg-eth0


File : /etc/sysconfig/network-scripts/route-eth0

GATEWAY_VM dev eth0
default via GATEWAY_VM dev eth0

File : /etc/resolv.conf

nameserver # OVH DNS Server

CentOS 7

For CentOS 7, the network adapter will vary depending on the installation. You will need to verify what is the adapter name and use it to configure your Virtual Machine. Use the command ipaddr to find your interface name.

File: /etc/sysconfig/network-scripts/ifcfg-(insert interface Name)

DEVICE=(insert interface Name)
If the file route-(insert interface Name) does not exist, you'll have to create it.
For CentOS 7, NETWORK_GW_VM is the main IP of your server where you replace the last octet by 0.

File: /etc/sysconfig/network-scripts/route-(insert interface Name)

GATEWAY_VM - (insert interface Name)
NETWORK_GW_VM - (insert interface Name)
default GATEWAY_VM

File: /etc/resolv.conf



For OpenSUSE, NETWORK_GW_VM is the main IP of your server where you replace the last octet by 0.

If the file ifcfg-ens32 does not exist, you'll have to create it.

File : /etc/sysconfig/network/ifcfg-ens32


If the file ifroute-ens32 does not exist, you'll have to create it.

File : /etc/sysconfig/network/ifroute-ens32

GATEWAY_VM - ens32
default GATEWAY_VM

In /etc/sysconfig/network/config, you need to have:


FreeBSD 8.0

File : /etc/rc.conf

ifconfig_em0="inet IP.FAIL.OVER netmask broadcast IP.FAIL.OVER"
static_routes="net1 net2"
route_net1="-net GATEWAY_VM/32 IP.FAIL.OVER"
route_net2="default GATEWAY_VM"

File : /etc/resolv.conf

nameserver # OVH DNS Server

Windows Server 2012 / Hyper-V

First you need to create Virtual Switch.

  1. On the command line of the host server run IPconfig /ALL
  2. Note the name of the network adapter that contains the IP address of the server's assigned IP.
  3. In Hyper-V manager create the a new virtual switch.
  4. Connection Type is External
  5. Select the adapter with the server's IP
  6. Check Allow management OS to share this network adapter

Virtual Switch Manager

This step only is 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.

Then select the VM that you wish to add the Failover IP. Use the Hyper-V Manager to change the settings of the VM (it needs to be shutdown).

  1. Expand the Network Adapter and click on Advanced Features.
  2. Change the MAC address to Static and enter the Virtual MAC address for Failover IP.
  3. Press OK to apply changes.

Hyper-V Manager

Start the VM and log in as an administrator.

  1. Control Panel > Network and Share Center
  2. Click on the Connections: Ethernet link
  3. Click on Properties Button to show Ethernet Properties
  4. Select Internet Protocol Version 4 (TCP/IPv4)
  5. Click on Properties Button to show IP V4 Properties

Ethernet Properties

On the IPv4 Properties window:

  1. Select the Use the following IP address
  2. Enter the Failover IP into the IP Address
  3. Enter into the Subnet Mask
  4. Enter your server's gateway IP address into the Default Gateway (your server's IP ending with 254)
  5. Enter into the Preferred DNS Server.
  6. Press OK and ignore the warning message about the gateway IP and Assigned IP not being in the same subnet.

Ethernet Properties

Finally, reboot server and the VM should be connected to the internet using the failover IP.

Other distributions

Here is the network configuration required in the Virtual Machine:

  • ip: IP_FAIL_OVER
  • netmask:

It is also required to add a default gateway to the Virtual Machine:

route add GATEWAY_VM dev eth0
route add default gw GATEWAY_VM

You will then need to configure the DNS of your machine so that it can make domain resolution. The IP of the OVH DNS server is