Configuring interfaces for Virtual Engines

Physical interfaces in the properties of a Virtual Engine represent interfaces allocated to the Virtual Engine in the Master Engine.

All communication between Virtual Engine and the Secure SD-WAN Manager is proxied by the Master Engine.

Physical interfaces for Virtual Engines are automatically created based on the interface configuration in the Master Engine properties. The number of physical interfaces depends on the number of interfaces allocated to the Virtual Engine in the Master Engine. You can optionally edit the automatically created physical interfaces.

You can add VLAN interfaces if the creation of VLAN interfaces for Virtual Engines is enabled in the properties of the physical interface on the Master Engine.

Both IPv4 and IPv6 addresses are supported on Virtual Firewalls. You can define one or more static IP addresses for Virtual Firewall interfaces. On Virtual Firewalls, you can also optionally add tunnel interfaces for route-based VPNs.

You can optionally add loopback IP addresses to the Virtual Firewall. Loopback IP addresses allow you to assign IP addresses that do not belong to any directly connected networks to the Virtual Firewall. Loopback IP addresses are not connected to any physical interface and they do not create connectivity to any network. Any IP address that is not already used on another physical or VLAN interface in the same Virtual Firewall can be used as a loopback IP address. The same IP address can be used as a loopback IP address and as the IP address of a tunnel interface. Loopback IP addresses can be used as the IPv4 Identity for Authentication Requests or IPv6 Identity for Authentication Requests, the IPv4 Source for Authentication Requests or IPv6 Source for Authentication Requests, and the Default IP Address for Outgoing Traffic.

By default, the interface definitions for the Virtual Engine are mapped to interfaces on the Master Engine in the order in which the interfaces are created on the Master Engine.