Billion Electric Company 30 user manual Before Fail Over, After Fail Over, Inbound Load Balancing

192.168.2.2

		ftp ftp.billion.dydns.org
FTP	ftp.billion.dyndns.org
192.168.2.3
HTTP	Before Fail Over	Remote Access from Internet
192.168.2.2		ftp ftp.billion.dydns.org
FTP
192.168.2.3	ftp.billion.dyndns.org
HTTP	After Fail Over	Remote Access from Internet

In the above example, an FTP Server (IP_192.168.2.2) and an HTTP Server

(IP_192.168.2.3) are connected to the Internet via WAN1 (ftp.billion.dyndns.org) on BiGuard 30. A remote computer is trying to access these servers via the Internet. Under normal circumstances, the remote computer will gain access to the network via WAN1. Should WAN1 fail, Inbound Fail Over tells BiGuard 30 to reroute incoming traffic to WAN2 by using the Dynamic DNS mechanism. Configuring your BiGuard 30 for Inbound Fail Over provides a more reliable connection for your incoming traffic.

Please refer to appendix H for example settings.

2.4.2Inbound Load Balancing

Inbound Load Balancing allows BiGuard 30 to intelligently manage inbound traffic based on the amount of load of each WAN connection.

24