Basic OVH Scale networking config for static IPs

[J0hny]

I recently purchased Scale range of dedicated server with OVH, and am on my second day trying to start networking correctly. Originally I followed guide https://support.us.ovhcloud.com/hc/en-us/articles/4408052730387 fully, but to no avail.

Host static IP: H.H.H.H
Host Gateway: G.G.G.G
Bought IP range R.R.R.128/29

I am Using Proxmox 8 with following setup:

Host /etc/network/interfaces

auto lo
iface lo inet loopback

# public interface 1
auto ens3f0np0
iface ens3f0np0 inet manual
    bond-master bond0

# public interface 2
auto ens3f1np1
iface ens3f1np1 inet manual
    bond-master bond0

# private interface 1
auto enp129s0f0np0
iface enp129s0f1np0 inet manual

# private interface 2
auto enp129s0f1np1
iface enp129s0f1np1 inet manual

auto bond0
iface bond0 inet static
    address H.H.H.H/32
    gateway G.G.G.G
    bond-slaves ens3f0np0 ens3f1np1
    bond-miimon 100
    bond-mode 802.3ad
    post-up echo 1 > /proc/sys/net/ipv4/conf/bond0/proxy_arp
    post-up echo 1 > /proc/sys/net/ipv4/ip_forward
#WAN IP (not FO IP)


auto vmbr0
iface vmbr0 inet static
    address 192.168.0.1/32
    bridge-ports none
    bridge-stp off
    bridge-fd 0
    post-up ip route add R.R.R.128/29 dev vmbr0
#bridge for FO IP subnet

VM /etc/network/interfaces:

auto lo ens18
iface lo inet loopback

# The primary network interface
iface ens18 inet static
    address R.R.R.130/32
    gateway 192.168.0.1
    netmask 255.255.255.255

I haven't configured anything aside these two files. VM is Debian 12.

I cant ping from VM anywhere. Do you spot any deadly bug?

 

[J0hny]

I am posting working config here for whomever would run into the same issues.

auto lo
iface lo inet loopback
  # Enable IP forwarding
  up echo "1" > /proc/sys/net/ipv4/ip_forward
  # Enable proxy-arp only for public bond
  up echo "1" > /proc/sys/net/ipv4/conf/bond0/proxy_arp


# public interface 1
auto ens3f0np0
iface ens3f0np0 inet manual
    bond-master bond0


# public interface 2
auto ens3f1np1
iface ens3f1np1 inet manual
    bond-master bond0


# private interface 1
auto enp129s0f0np0
iface enp129s0f1np0 inet manual


# private interface 2
auto enp129s0f1np1
iface enp129s0f1np1 inet manual


# LACP aggregate on public interfaces
# configured in static mode on this example
# Has the server's public IP
auto bond0
iface bond0 inet static
    address H.H.H.H/32
    gateway G.G.G.G
    bond-slaves ens3f0np0 ens3f1np1
    bond-mode 4
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200
    bond-lacp-rate 1
    bond-xmit-hash-policy layer3+4
    # Use the mac address of the first public interface
    hwaddress HWADDRESS


#Private
auto bond1
iface bond1 inet static
    bond-slaves enp129s0f1np0 enp129s0f1np1
    bond-mode 4
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200
    bond-lacp-rate 1
    bond-xmit-hash-policy layer3+4
    # Use the mac address of the first private interface
    hwaddress HWADDRESS2


auto vmbr0
iface vmbr0 inet manual
    # Define a private IP, it should not overlap your existing private networks on the vrack for example
    address 192.168.0.1/24
    bridge-ports none
    bridge-stp off
    bridge-fd 0
    up ip route add R.R.R.130/32 dev vmbr0
    up ip route add R.R.R.131/32 dev vmbr0
    up ip route add R.R.R.132/32 dev vmbr0
    up ip route add R.R.R.133/32 dev vmbr0


# Bridge used for private networks on vRack
# The VLAN feature is enabled
auto vmbr1
iface vmbr1 inet manual
        bridge-ports bond1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

The problem was that the OVH guide was telling us to restart networking service. That apparently effects the bridge and make it unusable by VMs connected to it. In our case restarting machines solved the issue.

VM config from up there was fine:

auto lo ens18
iface lo inet loopback

# The primary network interface
iface ens18 inet static
    address R.R.R.130/32
    gateway 192.168.0.1
    netmask 255.255.255.255

 

[Christalive]

This really helped me, thanks. I'm struggling to get the config working on a Ubuntu VM though as it uses netplan. Do you know what the config would look like on Ubuntu?

 

[Christalive]

OK for the benefit of posterity I figured this out. You need to use on-link https://netplan.readthedocs.io/en/0.106/examples/#reaching-a-directly-connected-gateway

network:
  version: 2
  renderer: networkd
  ethernets:
    ens18:
      addresses:
       - R.R.R.130/32
      dhcp4: no
      routes:
       - to: default
         via: 192.168.0.1
         on-link: true
      nameservers:
         addresses: [8.8.8.8, 8.8.4.4]

 

[J0hny]

Glad you found it useful. I think that the addition of nameservers is also an important bit. We needed to set these manually as well.