Defining a static MNI subnet
You can define an MNI subnetwork through which traffic can be routed publicly.
Before you begin
About this task
Procedure
-
Determine whether you need an alternative subnet mask. If the subnetwork mask that is applied
to the MNI is too restrictive, you can assign an alternate subnet mask to extend the subnet range
for SafeLinx Clients that attach through the MNI. To assign an alternate subnet,from the MNI
properties, click the Network tab, select Use alternate subnet mask
on client, and then specify the new mask. The alternate subnet mask overrides the MNI's
default subnet mask.
Note: Some networks reserve the lowest and highest addresses in the subnet range for use as network broadcast addresses. On networks that reserve addresses, do not assign the reserved addresses to SafeLinx Clients or mobile devices.
- Update the routing tables of your organization to include the SafeLinx Server's IP address.
- Update the routing tables of your organization to route the MNI address range to the IP address of the SafeLinx Server.
- Verify that traffic is routed securely between a SafeLinx Client and mobile access services.
- Optionally set up filters, packet mappings, or routing aliases for the MNI.