Example: Using NAT rules to forward traffic

The example company has decided to screen HTTP and HTTPS connections using a proxy service hosted in the cloud.

The company uses NAT rules to control application-specific link selection, to send traffic over high-quality network links if the traffic is critical to their business and to less expensive network links if the traffic is not critical.

The administrators have already set up the proxy and configured it to process HTTP and HTTPS traffic according to the company’s policy. To configure the forwarding, the administrators:

  1. Create a Proxy Server element to represent their proxy service.
  2. Create a NAT rule that forwards traffic to the proxy service using a high-quality link if the traffic contains network applications that are critical to the business.
  3. Create a second NAT rule that forwards traffic to the proxy service using another, low-cost link if the traffic contains non-critical network applications.
ID Source Destination Service Action
2.1 Original source address of the traffic. For example, clients in the internal network. Original destination address of the traffic. For example, a web server. Network Applications that are critical to the business. For example, Salesforce.

On the Source Translation tab, select Dynamic as the Translation Type, then select a high-quality Outbound Multi-Link element.

On the Destination translation tab, select Forward to Proxy as the Translation Type, then select your Proxy Server element.
2.2 Original source address of the traffic. For example, clients in the internal network. Original destination address of the traffic. For example, a web server. Network Applications that are not critical to the business. For example, YouTube.

On the Source Translation tab, select Static as the Translation Type, then select a low-cost Outbound Multi-Link element.

On the Destination translation tab, select Forward to Proxy as the Translation Type, then select your Proxy Server element.