Networks

Network creation

In the Control Panel go to the “Cloud” / “Networks” section.
To create a new network, click the “Create” button which will take you to the network creation page. Here, you have the option to create either an external or an internal network. Note that in each region, you can only have one external network.
Set the Network Name. It is acceptable to use letters of the Latin alphabet, numbers and symbols (within reasonable limits).
Select region. The network will be available in all availability zones of the selected region. As described above, the following regions are available:

Warsaw, Poland;
Miami, USA;
Dallas, USA;
Manila, Philippines;
Almaty, Kazakhstan.

Network parameters. Select the proper items or leave them by default (later through the “More” button you will be able to enable the necessary network settings).

Turn on network - the network will be immediately enabled after creation.
Create subnet - creates a subnet associated with the network.

To create a new subnet mark the checkbox Create subnet. After this action the additional subnet settings will open.
Select a tab for the future subnet - IPv4 or IPv6.
In case of IPv4 subnet configuring set the Subnet name - It is acceptable to use letters of the Latin alphabet, numbers and symbols (within reasonable limits)
Enter the required Subnet Address. Network address in CIDR format (e.g. 192.168.0.1/24).
IP Gateway - in the list select the item that is most suitable for the subnet from the list:

Do not specify a gateway;
Set the default gateway;
Set the IP gateway manually (an additional field will appear where you need to enter the IP address of the gateway).

If the subnet needs a DHCP server, mark the corresponding checkbox and specify the IP addresses of the beginning and of the end of the pool as well as the issued DNS servers.
To create an IPv6 subnet the settings are the same.
To finish click the “Create Network” button.
The created internal network can be found in the Control Panel under “Cloud” / “Networks”.

Connection the network to the server

In the Control Panel go to the “Cloud” / “Virtual Servers” section.
Select the required server and click “More”.
In the Ports section, click the “Create” button.
Select the required network from the appeared list. The list will contain only networks of the region where the server was created.
You can connect to the server either an existing free port or a new one. The IP address field is optional. If a DHCP server is configured in the subnet, it will assign the IP address.
Click the “Save” button.
A new entry, featuring the allocated IP address, will be added to the Ports section. Simultaneously, a new interface will be created automatically on the server, eliminating the need for a server reboot.

Port Management

Navigate to the network page in the “Ports” section through the Control Panel under “Cloud” / “Networks”. Select the desired network and click “More”.

Adding a Port

On the page that opens, under the “Ports” tab, click “Add Port”.
Select from the list the server you wish to connect the new port to, or select a dash for an free port. Optionally, enter an IP address.
Click “Add”.

Hint

An existing port can be connected to a server during the creation of a new server or to an existing server in the “Ports” section.

Connecting a Port

On the “Ports” tab, select the desired available port from the list. Such port has no device connected and a “Connect” button active.
Click “Connect”.
From the list, select the server to which you want to connect the port.
Click “Connect”.

Disconnecting a Port

Select the desired port from the list under the “Ports” tab.
Click “Disconnect”. The port will be disconnected immediately.

Important

A port with IPv4 and IPv6 addresses will remain in the list and be available for connection to another virtual machine.

Attention

When disconnecting a port in an external network, the public IPv4 address will continue to incur charges until it is removed.

Deleting a Port

From the “Ports” tab on the opened page, select the desired port from the list.
Click the trash can icon. The port will be immediately removed.

Setting up an internal network on a Linux virtual server

After adding the ports on a virtual server with an internal network it is important to make sure that interfaces appear on the server. it’s necessary to enter the ip a command:

root@test-ubu:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
   link/ether fa:16:3e:a7:06:e8 brd ff:ff:ff:ff:ff:ff
   inet 45.139.24.57/24 brd 45.139.24.255 scope global dynamic eth0
      valid_lft 85975sec preferred_lft 85975sec
   inet6 2a0f:1140:100::65/128 scope global dynamic noprefixroute
      valid_lft 85977sec preferred_lft 85977sec
   inet6 fe80::f816:3eff:fea7:6e8/64 scope link
      valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
   link/ether fa:16:3e:f0:d9:27 brd ff:ff:ff:ff:ff:ff
   inet 192.168.0.32/24 brd 192.168.0.255 scope global dynamic eth1
      valid_lft 85975sec preferred_lft 85975sec
   inet6 fe80::f816:3eff:fef0:d927/64 scope link
      valid_lft forever preferred_lft forever

The eth1 interface is the internal network in this case.

It is a possible case when the eth1 interface has not run.

root@test-ubu:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00eth1:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
   link/ether fa:16:3e:a7:06:e8 brd ff:ff:ff:ff:ff:ff
   inet 45.139.24.57/24 brd 45.139.24.255 scope global dynamic eth0
      valid_lft 86390sec preferred_lft 86390sec
   inet6 2a0f:1140:100::65/128 scope global dynamic noprefixroute
      valid_lft 86391sec preferred_lft 86391sec
   inet6 fe80::f816:3eff:fea7:6e8/64 scope link
      valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
   link/ether fa:16:3e:f0:d9:27 brd ff:ff:ff:ff:ff:ff

In this case it’s necessary to make changes to the /etc/netplan/01-netcfg.yaml file using any text editor.

An example of a file with standard settings.

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
 version: 2
 renderer: networkd
 ethernets:
   enp0s3:
     dhcp4: yes
     dhcp6: yes

Make changes using the nano text editor:

nano /etc/netplan/01-netcfg.yaml

Open the file and make changes for eth1:

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
 version: 2
 renderer: networkd
 ethernets:
   enp0s3:
     dhcp4: yes
     dhcp6: yes
   eth1:
     dhcp4: yes

Next, save the file with the Ctrl+O key combination and exit the text editor with the Ctrl+X key combination.
In order to save the netplan settings and do not reset it after a reboot enter the netplan apply command.

netplan apply

After that it is possible to see using the ip a command if the local network managed to run the eth1 interface or not.

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
   link/ether fa:16:3e:a7:06:e8 brd ff:ff:ff:ff:ff:ff
   inet 45.139.24.57/24 brd 45.139.24.255 scope global dynamic eth0
      valid_lft 86396sec preferred_lft 86396sec
   inet6 2a0f:1140:100::65/128 scope global dynamic noprefixroute
      valid_lft 86398sec preferred_lft 86398sec
   inet6 fe80::f816:3eff:fea7:6e8/64 scope link
      valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
   link/ether fa:16:3e:f0:d9:27 brd ff:ff:ff:ff:ff:ff
   inet 192.168.0.32/24 brd 192.168.0.255 scope global dynamic eth1
      valid_lft 86396sec preferred_lft 86396sec
   inet6 fe80::f816:3eff:fef0:d927/64 scope link
      valid_lft forever preferred_lft forever

The same solution if it’s necessary to run the Static ip on the eth1 interface.

nano /etc/netplan/01-netcfg.yaml

Open the file and make changes for eth1:

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
 version: 2
 renderer: networkd
 ethernets:
   enp0s3:
     dhcp4: yes
     dhcp6: yes
   eth1:
     dhcp4: no
     addresses: [192.168.0.30/24]
     routes:
       - to: default
         via: 192.168.0.1
     mtu: 1500
     nameservers:
         addresses: [IP DNS Сервера 1, IP DNS сервера 2]

Also, in order to save the netplan settings and not to let them being reset after reboot, enter the netplan apply command.