Fortinet black logo

Mapping the virtual NICs (vNICs) to physical NICs

Mapping the virtual NICs (vNICs) to physical NICs

When you import the FortiWeb-VM package, the import process creates 4 bridging vNICs and automatically maps them to a port group on 1 virtual switch (vSwitch) within the hypervisor (the default name of this vSwitch is vmnet). Each of the 4 network interfaces in FortiWeb-VM uses one of these vNICs. (Alternatively, you can configure some or all of the network interfaces to use the same vNIC.) vSwitches are themselves mapped to physical ports on the server.

In many cases, you do not need to change the default mappings of the FortiWeb-VM network adapter ports to the host computer’s physical ports.

You can change the mapping, or map other vNICs, if either your VM environment requires it or you want the FortiWeb-VM to operate in either True Transparent Proxy or Transparent Inspection mode. (See Configuring the vNetwork for the transparent modes.)

If you are unsure of your network mappings, try bridging before you attempt non-default vNIC modes such as NAT or host-only networks. The default bridging vNIC mappings are appropriate for configurations where each of the host’s guest virtual machines have their own IP addresses on your network.

Mapping the virtual NICs (vNICs) to physical NICs

When you import the FortiWeb-VM package, the import process creates 4 bridging vNICs and automatically maps them to a port group on 1 virtual switch (vSwitch) within the hypervisor (the default name of this vSwitch is vmnet). Each of the 4 network interfaces in FortiWeb-VM uses one of these vNICs. (Alternatively, you can configure some or all of the network interfaces to use the same vNIC.) vSwitches are themselves mapped to physical ports on the server.

In many cases, you do not need to change the default mappings of the FortiWeb-VM network adapter ports to the host computer’s physical ports.

You can change the mapping, or map other vNICs, if either your VM environment requires it or you want the FortiWeb-VM to operate in either True Transparent Proxy or Transparent Inspection mode. (See Configuring the vNetwork for the transparent modes.)

If you are unsure of your network mappings, try bridging before you attempt non-default vNIC modes such as NAT or host-only networks. The default bridging vNIC mappings are appropriate for configurations where each of the host’s guest virtual machines have their own IP addresses on your network.