netplan | Geek Tank

This took way too long to figure out and it’s my own fault as I do have a good understanding of networking.

When you order additional IP’s from So You Start, you’re usually giving IP’s in a different range the main IP address of your server. This might confuse some because of how traditional networking states you have to be in the same subnet as your gateway.

This causes problems for deploying virtual machines when using Xen and Ubuntu 18 as it has moved over to netplan. The problem lies in the fact you shouldn’t be able to reach your gateway out of your subnet.

So you have to do the following so that netplan is able to understand how to add the gateway properly.

# This file describes the network interfaces available on your system

# For more information, see netplan(5).

network:
  version: 2
  renderer: networkd
  ethernets:
    ens160:
      dhcp4: no
      dhcp6: no
      addresses: [x.x.x.x/32]
      gateway4: y.y.y.254
        routes:
          - to: y.y.y.254/32
          via: 0.0.0.0
          scope: link
      nameservers:
        addresses: [208.67.222.222,208.67.220.220]

Here’s the wonderful thread it came from

https://askubuntu.com/questions/1062406/ubuntu-18-04-server-vps-on-failover-ip-ovh

So You Start netplan Configuration for Additional IP’s