Bridging to one of the Xen server’s physical network interfaces
If you have not yet installed the network bridge utilities required by Xen in order to bridge virtual machines’ vNICs to the hypervisor’s network connection, you must do that by installing the bridge network utilities and then editing the network interface configuration.
sudo apt-get install bridge-utils
sudo nano /etc/network/interfaces
When editing the network interface configuration, usually you should bind the bridge (in the vif example in Deploying via Virtual Machine Manager or Deploying via dom0 command line, the bridge is xenbr0) to one of your network interfaces (e.g. eth0) in /etc/network/interfaces. Depending on the number of physical interfaces on the server and how you will map them to vNetworks, you may need to create multiple bridges.
The following table provides an example of how vNICs could be mapped to the physical network ports on a server with two physical NICs for a FortiWeb operating in reverse proxy mode.
Example: Network mapping for Reverse Proxy mode
Below is a configuration example assuming the server has only one physical NIC, eth0:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto xenbr0
iface xenbr0 inet static
address 192.0.2.10
netmask 255.255.255.0
gateway 192.0.2.1
#Enable line below for vSwitch with FortiWeb transparent mode
#allow-hotplug xenbr0