Gallium is equipped with networking capabilities that are designed to deal with unexpected changes on the network edge. This article elaborates on the fundamental networking aspects of a Gallium Hypervisor.

By default, Gallium generates a Bridge network for each physical network adapter in your server. These Bridge networks are named after the adapter's base MAC address.

When a VM is connected to a Bridge network, it gets directly connected to the corresponding port on the server.

You can add a VLAN tagged network by pressing the Add button on the desired parent Network Adaptor. Once added you can attach Virtual Machine to the newly created network. You cannot delete a VLAN network until all Virtual Machines have been detached.

In addition to Bridge networks, Gallium provides a Default NAT (Network Address Translation) network. This network facilitates IP address translation between the Hypervisor and the VMs. With NAT, a VM shares the Hypervisor's IP address, effectively masking the VM's actual IP address.

Devices on the NAT network can be exposed using the Service Gateway. This allows only specific ports on the VM to exposed to the local network

Gallium Hypervisor requests an IP address via DHCP (Dynamic Host Configuration Protocol) on every physical interface. This setup ensures that the Hypervisor is always ready to establish a connection with the Gallium Console.

The Hypervisor will connect to the Console using any available pathway. If one connection goes offline, the Hypervisor seamlessly switches to the next available connection. This design ensures uninterrupted communication between the Hypervisor and the Console should an unexpected cabling change occur.

The Maximum Transmission Unit for all Networks is set on the parent Network Adaptor. Valid MTU ranges from 1500 to 9000. The MTU can be changed from the Edit Network page.