Split Tunnel Profile
A Split Tunnel Profile can be created to
manage corporate and local traffic by sending only corporate traffic to the controller.
A split
tunnel ensures that local traffic does not incur the overhead of the round trip to
the
controller, which decreases traffic on the WAN link and minimizes latency for local
application
traffic. Using a split tunnel, a remote user is associated with a single SSID (rather
than
multiple SSIDs) to access corporate resources, such as a mail server, and local resources
(for
example, a local printer).
Split Tunnel Profile Limitations
Before enabling the Split Tunnel Profile, consider the following limitations:
- The Split Tunnel Profile does not support a zone where Mesh-enabled APs are present.
- The Split Tunnel Profile and Express Wi-Fi are not supported together on the same WLAN.
- For the Split Tunnel Profile and Express Wi-Fi to work properly, the configured IP rules for a split tunnel and a walled garden must be different.
- The Split Tunnel Profile does not support DHCP server or NAT router.
- The Split Tunnel Profile does not support wired clients.
- The limitations applicable to DHCP or NAT also apply to the Split Tunnel Profile.
-
6.0 updateWISPr-related (web-authentication) WLANs are not supported on a split tunnel WLAN.
- ICMP is not supported towards a line buildout (LBO) split path where Source Network Address Translation (SNAT) occurs.
- IPv6 addresses are not supported in the Split Tunnel Profile.
- Multicast discovery of Bonjour devices will not occur over the LBO.
- As the data traffic is established from the server side, TFTP is not supported.
- As the server rejects the data connection that does not have the NAT IP address sent by the client, the FTP active mode is not supported with a split tunnel.