ZyXEL Communications 110, 1100, 310 7.9 Virtual Interfaces

Chapter 7 Interfaces

Table 58 Configuration > Network > Interface > Bridge > Create Virtual Interface (continued)

LABEL	DESCRIPTION
Enable	Select this to turn on the connection check.
Connectivity
Check
Check Method	Select the method that the gateway allows.
	Select icmp to have the ZyWALL regularly ping the gateway you specify to make sure it
	is still available.
	Select tcp to have the ZyWALL regularly perform a TCP handshake with the gateway
	you specify to make sure it is still available.
Check Period	Enter the number of seconds between connection check attempts.
Check Timeout	Enter the number of seconds to wait for a response before the attempt is a failure.
Check Fail	Enter the number of consecutive failures before the ZyWALL stops routing through the
Tolerance	gateway.
Check Default	Select this to use the default gateway for the connectivity check.
Gateway
Check this	Select this to specify a domain name or IP address for the connectivity check. Enter
address	that domain name or IP address in the field next to it.
Check Port	This field only displays when you set the Check Method to tcp. Specify the port
	number to use for a TCP connectivity check.
Related Setting
Configure WAN	Click WAN TRUNK to go to a screen where you can configure the interface as part of a
TRUNK	WAN trunk for load balancing.
Configure Policy	Click Policy Route to go to the screen where you can manually configure a policy
Route	route to associate traffic with this bridge interface.
OK	Click OK to save your changes back to the ZyWALL.
Cancel	Click Cancel to exit this screen without saving.

7.9 Virtual Interfaces

Use virtual interfaces to tell the ZyWALL where to route packets. Virtual interfaces can also be used in VPN gateways (see Chapter 20 on page 281) and VRRP groups (see Chapter 26 on page 359).

Virtual interfaces can be created on top of Ethernet interfaces, VLAN interfaces, or bridge interfaces. Virtual VLAN interfaces recognize and use the same VLAN ID. Otherwise, there is no difference between each type of virtual interface. Network policies (for example, firewall rules) that apply to the underlying interface automatically apply to the virtual interface as well.

Like other interfaces, virtual interfaces have an IP address, subnet mask, and gateway used to make routing decisions. However, you have to manually specify the IP address and subnet mask; virtual interfaces cannot be DHCP clients. Like other interfaces, you can restrict bandwidth through virtual interfaces, but you cannot change the MTU. The virtual interface uses the same MTU that the underlying interface uses. Unlike other interfaces, virtual interfaces do not provide DHCP services, and they do not verify that the gateway is available.

170
	ZyWALL 110/310/1100 Series User’s Guide