Inbound Server Balancing

The first is through our VirtualNAT application proxy, which allows for easy inbound balancing of TCP traffic for web, email, and other standard application to a server on the LAN.

The second is through one-to-one or one-to-many NAT mappings. This process, which is required for passive FTP, or any non-TCP based application, requires a separate LAN address for each WAN port tied to a server.

Example:

WebServer 10.10.10.1 -> WAN1 23.65.45.21

WebServer (secondary address) 10.10.10.2 -> WAN2 215.23.65.12

WebServer (secondary address) 10.10.10.3 -> WAN3 65.12.26.120

Each server address must have a corresponding Vector Map and a firewall rule allowing the inbound traffic (if the firewall is enabled).