Adding a routing alias to route traffic through a SafeLinx Client to a subnetwork

A mobile access service can route data to a designated subnetwork through a multihomed SafeLinx Client. To enable subnetwork routing through a SafeLinx Client, define a routing alias that specifies the IP addresses of the client and of the destination subnetwork.

You must obtain a static IP address for the SafeLinx Client interface that you define as the routing alias.

To define the range of IP addresses for the destination subnetwork, you specify a destination IP address and a subnet mask.

The SafeLinx Server delivers all traffic that is destined for the specified subnetwork to the SafeLinx Client's IP address. The SafeLinx Client then acts as a destination gateway and routes the data to the destination address. To create a routing alias for a SafeLinx Client, complete the following procedure.

  1. On the SafeLinx Client computer, enable IP routing between network interfaces so that data can flow between networks.
  2. From the Resources page of the SafeLinx Administrator, right-click the mobile access services to which you want to add the routing alias, and then click Add Routing alias.
  3. Complete the following fields in the Add a New Routing Alias wizard, and then click Finish:
    Destination IP address
    The first address in the network to which you want the SafeLinx Server to route traffic through the alias.
    Destination mask
    The network mask to apply to the Destination IP address to define the range of the destination subnetwork.
    Destination gateway
    The fixed IP address of the SafeLinx Client that you want to use as the destination gateway to route traffic to the subnetwork.