Fortinet black logo

VM Installation Guide

Step 1: Bridge to one of the Xen server physical network interfaces

5.3.0
Copy Link
Copy Doc ID 96c7833d-d34d-11e9-8977-00505692583a:411974
Download PDF

Step 1: Bridge to one of the Xen server physical network interfaces

If you have not yet installed the network bridge utilities required by Xen in order to bridge the virtual machine vNICs to the hypervisor 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 examples, 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.

Example: Network mapping for reverse proxy mode

Xen Project FortiADC-VM
Physical Network Adapter Network Mapping (vSwitch Port Group) Virtual Network Adapter for FortiADC‑VM Network Interface Name in Web UI/CLI
eth0 xenbr0 Management port1
eth1 xenbr1 External port2
xenbr2 Internal port3

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

Step 1: Bridge to one of the Xen server physical network interfaces

If you have not yet installed the network bridge utilities required by Xen in order to bridge the virtual machine vNICs to the hypervisor 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 examples, 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.

Example: Network mapping for reverse proxy mode

Xen Project FortiADC-VM
Physical Network Adapter Network Mapping (vSwitch Port Group) Virtual Network Adapter for FortiADC‑VM Network Interface Name in Web UI/CLI
eth0 xenbr0 Management port1
eth1 xenbr1 External port2
xenbr2 Internal port3

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