This article describes Reverse Split Tunnel use case in XenMobile Server and NetScaler, and its configuration steps.
Sending all user device originating traffic, including Internet traffic, through VPN tunnel might not be desirable in most cases. Internet traffic going to NetScaler Gateway adds lot more hops in reaching the servers and thus in getting the response back on user device.
In some cases, organization would like to secure their internal network from any kind of attack by making sure that all traffic originating from user device goes though it’s network. By this they make sure that all Internet traffic goes through their forward proxy and (web) firewall and thus any possibility of compromising the user device to gain access to internal network is eliminated.
NetScaler Gateway’s split tunnel capability allows the Gateway plug-in to decide which traffic to send to VPN tunnel and which not. When the NetScaler Gateway Plug-in starts, it obtains the list of intranet applications from NetScaler Gateway. The NetScaler Gateway Plug-in examines all packets transmitted on the network from the user device and compares the addresses within the packets to the list of intranet applications.
Split tunnel on NetScaler Gateway can be configured as OFF, ON or REVERSE. Accordingly the Gateway plug-in takes the forwarding decision.Configure Split Tunneling Reverse mode on the NetScaler Gateway.
To configure Reverse mode for the Split Tunneling feature, navigate to Policies > Session Policy. Choose the Secure Hub Policy and navigate to Client Experience > Split Tunnel. Select REVERSE. Please note that REVERSE split tunnel only supports intranet applications added using IP Addresses versus FQDN. Therefore, the corresponding IP Addresses that belong to the FQDN's can be added as Intranet Applications.
Configure MDX Policy on XenMobile Server .
XenMobile 10.3.5 or later introduces a new MDX policy titled "Reverse Split Tunnel Mode Exclusion List”. This is configured with the 'Exclusion' range based on a comma-separated list of DNS suffixes and FQDN, which defines the URLs for which traffic must be sent out on the local area network (LAN) of the device and would not be sent to the NetScaler.