VERDE supports two networking options. If no configuration is done, virtual machines use NAT. Once networking is configured, settings are applied to Gold Images and guest sessions.
NAT networking provides a platform to deliver services securely, without exposing the virtual machine to the network at large or requiring a unique IP address across the subnet. In this mode, the virtual machine does receive an IP address, but that address is visible only to the host server and it is managed automatically by VERDE. Virtual machines do not receive inbound network connections when using NAT networking, which increases the level of security and diminished the need for firewalls inside a guest image. However, outbound traffic has access to all routes on the host.
NAT uses two connection interfaces.
- The primary interface is used for guest-to-host and host-to-guest services and is configured on the private interface, such as
- The secondary network interface uses DNS to route to the external networks connected to the host. By default, a virtual subnet of
192.168.84.x (netmask 255.255.255.0)is assigned.
This interface should not be reconfigured unless one of the following is true:
- The subnet needs to be changed.
- The interface is placed on a VLAN.
- The interface is disabled.
Bridged networking enables full access to a physical network from a virtual machine. Use bridged networking to assign one or more network interfaces to guest session traffic. Bridged networking provides the following:
- Virtual machines have full access to a specific host-attached network, allowing advanced functions such as network share browsing.
- Virtual machines can export shares or allow inbound connections from other clients or virtual machines.
- Virtual machines must receive a unique IP address from a DHCP server, or configure one statically. This IP address must be unique in the subnet.
- VLAN tagging.
As with NAT, bridged networking uses two connection interfaces:
- The primary interface is used for guest-to-host and host-to-guest services, and is configured on a private subnet, such as 10.0.2.x.
- The secondary interface binds to a physical or logical Ethernet interface on the host and maintains real network parameters (IP address, netmask).
Open vSwitch is a multilayer software switch that supports standard management interfaces and is designed for virtual environments. Open vSwitch is a type of bridged networking that enables VERDE to use VLAN tagging and port bonding to enhance security and increase network bandwidth. When configured, it replaces the standard Linux bridge networking.
Open vSwitch functions as a virtual networking switch. When configured with VERDE, the following features are available:
- Standard VLAN model with trunk and access ports.
- NIC bonding.
- Per session bandwidth controls through Session Settings.
If configuring multiple VLAN host interfaces, one interface must have a static IP address. Multiple DHCP interfaces without a static IP interface are not supported. An interface with a static IP address is needed to determine the default route.
One or more network interfaces can be bonded together to act as one physical interface. Interfaces can be bonded to increase networking speed or as a failover mechanism. Once a single network interface is configured, additional networks are configured as "slaves" to the first network bridge.
A VLAN enables one or more virtual networks to travel across a physical interface. Each Ethernet packet contains a field called VLAN tag that, if configured, determines the virtual network on which it will travel. The tag, assigned by the internal Open vSwitch, is used to appropriately route the packet and is removed once the packet reaches the external destination switch. See the standard developed by IEEE 802.1 for more information.
- VLAN assignments for guests are set in Session Settings. The interface name of the network created in VERDE Menu (NETWORK1, or NETWORK2 for example) is defined there. The VLAN number is also defined in Session Settings.
- Server interfaces (storage NFS connection or User Console for example) are assigned a VLAN tag in the VERDE menu.