Each virtual system managed by Cloudmin has at least one network interface / IP address, which the system's hostname typically resolved to in DNS. On the virtual machine this usually appears as eth0 - how it appears on the host system differs depending on the type of virtualization being used.
It is possible for virtual system to have multiple network interfaces. For Xen and KVM instances on host systems with more than one bridge, the virtual machines can have one ethN interface per bridge. Typically each is connected to a different physical network or VLAN on the host system.
Cloudmin lets you add extra IP addresses to a virtual system, although these will usually be virtual interfaces like eth0:5. This is useful if you want a VPS to host multiple SSL-protected websites, each of which needs its own IP address.
System owners can be either completely denied access to page for managing network interfaces, or limited in how many IP addresses they can use across all their virtual machines. This can be done either at the plan level, or on an owner-by-owner basis.
Cloudmin can fully manage network interfaces on any system running Webmin, or with a Debian-based or Redhat-based Linux distribution installed. It can even manage interfaces on a down system, assuming it is running Debian, Ubuntu, RHEL, Fedora or CentOS. This allows you to fix networking errors even if a system is in-accessible, by first shutting it down and then using Cloudmin to edit interfaces.
On systems running Windows, BSD or an un-supported Linux distribution without Webmin, Cloudmin cannot manage the IP addresses assigned to network interfaces - instead, these must be set within the virtual system. However, it can configure the MAC address and network bridges assigned to each interface.
To create a new network interface, the steps to follow are :
The new IP address should be immediately activated and pingable, and will be added to both the networking configuration files on the virtual system, and any virtualization config files on the host system.
Xen and KVM virtual systems also support creation of non-virtual interfaces, which appear like eth1 on the virtual machine. If the host system has multiple network bridges you can select which bridge each new real interface is connected to - it is also possible to have multiple real interfaces bridged to the same real interface on the host.
To create a new real network interface, the steps to follow are :
ethN device on the virtual system.The new IP address should be immediately activated and pingable, and will be added to both the networking configuration files on the virtual system, and any virtualization config files on the host system.
To change or remove an interface, do the following :
eth0:5) or a real interface other than the first, you can click the Delete button to remove it.Again, all changes will be activated immediately with the exception of a change in the MAC address. That will only take effect when the virtual system is shut down and started up again. Only Xen and KVM systems can have their MAC addresses changed, and only for non-virtual interfaces.
Cloudmin can edit the default router on a running system with Webmin installed, or a down system with a support Linux distribution (Redhat or Debian based). The steps to do this are :
Be careful doing this on a running virtual system though, as you may cut off access to the Cloudmin master.
If the virtual system supports IPv6, you can also set a default gateway for IPv6 routing using this same form.
Cloudmin can be configured to setup the DHCP server on your master system to supply virtual machines with IP addresses. This can be useful if you want to use system images for operating systems that Cloudmin cannot configure the network on directly, such as Windows or FreeBSD.
The steps to setup a DHCP server are as follows :
yum install dhcp
On Debian or Ubuntu, the command is :
apt-get install dhcp3-serverWhen managing KVM, Xen or real systems running Linux with Cloudmin 5.6 or later, you can also enter IPv6 addresses for non-virtual network interfaces. However, only systems running Debian, Ubuntu, CentOS, Redhat or Fedora Linux are supported currently. IPv6 addresses can be added as follows :
eth0.2001:db8:0:f101::77 and a netmask like 64 into the IPv6 addresses table. Make sure it is within a range that has been routed to your network.