Manual Private Networks
To use your Private Network with a static IP configuration on each instance, you need to choose a subnet and to keep track of the IP assigned to each of your instances. For example, if you chose the 10.3.4.0/24 network and 10.3.4.10 as the IP address of your first instance, you can use any IP address in this network (from 10.3.4.1 to 10.3.4.254).
Interfaces configuration
You will need to configure the corresponding network interfaces - such as
eth1 - with their static IP parameters.
Ubuntu >= 18.04 (Bionic) [netplan]
In /etc/netplan/eth1.yaml:
network:
version: 2
ethernets:
eth1:
addresses:
- 10.3.4.10/24Followed by sudo netplan apply to bring the interface up.
You can find more configuration examples about netplan on their website.
Debian and Ubuntu < 18.04 [ifconfig]
In /etc/network/interfaces.d/eth1.conf:
auto eth1
iface eth1 inet static
address 10.3.4.10/24Followed by ifup eth1 to bring the interface up.
Using Cloud-Init (for Debian or Ubuntu)
To automate your Private Network setup, you may include the ad-hoc configuration
in your instance’s user data, such as for netplan (Ubuntu 18.04):
#cloud-config
write_files:
- path: /etc/netplan/eth1.yaml
content: |
network:
version: 2
ethernets:
eth1:
addresses:
- 10.3.4.10/24
runcmd:
- [ netplan, apply ]Windows
On Windows, go to the Network and Sharing Center. You should see the additional network interface:
Click on the name of the new interface (“Ethernet 2” in ourscreenshot). You will get the following dialog box:
Click on Properties. You will see the following dialog box:
Click on Internet Protocol Version 4 (TCP/IPv4), then on Properties. You will see a new dialog box. Click on Use the following IP address and enter the IP address you assigned for the instance (10.3.4.10). Use 255.255.255.0 for the subnet mask:
OpenBSD
OpenBSD needs to be rebooted for the new interface to show up. After it is rebooted, create the interface configuration file:
echo 'inet 10.3.4.10/24' > /etc/hostname.vio1
sh /etc/netstart vio1