In this article, we will understand how to configure Netplan for scenarios where the configuration is not automatically set up by your chosen virtualizer.
When launching a machine that will be used as a VaultOne Connector, depending on the virtualizer, version, or configuration used, there may be cases where the Netplan configuration is not automatically applied. In such cases, the configuration must be done manually.
To make the process easier, this guide will show how and where to apply this configuration, along with an example setup.
Step 1: Checking for Configuration Issues
To determine if you are facing the issue described in this guide, you can use commands such as:
IFCONFIG
If no interface is found using the network adapter, the configuration must be done manually.
Step 2: Editing the Netplan Configuration File
The file that needs to be modified for Netplan configuration is located in the /etc/netplan directory.
Below is an example of a Netplan configuration file. Make sure to verify that the interface name is correct, as well as the ADDRESS, GATEWAY, and DNS fields:
network:
version: 2
renderer: networkd
ethernets:
enp3s0:
addresses:
- 10.10.10.2/24
nameservers:
search: [mydomain, otherdomain]
addresses: [10.10.10.1, 1.1.1.1]
routes:
- to: default
via: 10.10.10.1
Step 3: Validating and Applying the Configuration
Before applying the Netplan configuration, it is recommended to verify that the file is correctly configured. You can do this using the following commands:
Validate the configuration file:
SUDO NETPLAN TRY
Apply the configuration:
SUDO NETPLAN APPLY
Now, the network interface should be available, and connectivity should be restored.
Additional Information
For other scenarios such as WiFi networks, DHCP, multiple network interfaces, etc. You can find documentation with example configurations at the following link: