>
    Configure a Split Tunnel Based on the Domain and Application
    Focus
    Download PDF
    Focus
    1. Home
    2. GlobalProtect
    3. GlobalProtect Gateways
    4. Split Tunnel Traffic on GlobalProtect Gateways
    5. Configure a Split Tunnel Based on the Domain and Application
    Download PDF
    GlobalProtect

    Configure a Split Tunnel Based on the Domain and Application

    Table of Contents
    End-of-Life (EoL)

    Configure a Split Tunnel Based on the Domain and Application

    Configure a split tunnel based on the destination domain and application.
    When you configure a split tunnel to include all traffic—IPv4 and IPv6—based the destination domain and port (optional) or application, all traffic going to that specific domain or application is sent through the VPN tunnel for inspection and policy enforcement. For example, you can allow all Salesforce traffic to go through the VPN tunnel using the *Salesforce.com destination domain. By including all Salesforce traffic in the VPN tunnel, you can provide secure access to the entire Salesforce domain and subdomains. You can configure a split tunnel without specifying a destination IP address subnet, which extends the split tunnel capability to domains and applications with dynamic public IP addresses, such as SaaS and public cloud applications.
    When you configure a split tunnel to exclude traffic—IPv4 and IPv6—based on the destination domain and port (optional) or application, all traffic for that specific application or domain is sent directly to the physical adapter on the endpoint without inspection. For example, you can exclude all Skype traffic from the VPN tunnel using the C:\Program Files (x86)\Skype\Phone\Skype application process name.
    Follow these recommendations when configuring a split tunnel based on the destination domain and application:
    • With a GlobalProtect license, you can enforce or apply split tunnel rules based on the destination domain and application to Windows and macOS endpoints.
    • On Windows devices, domain-based tunneling supports TCP traffic only; UDP traffic is not supported in domain-based split tunneling on Windows.
    • ICMP requests such as for latency, jitter, trace route tests are not supported for split tunneling based on the destination domain.
    • Supported on endpoints with Windows 7 Service Pack 2 and later releases and macOS 10.10 and later releases.
    • Supported on endpoints with Linux.
    Use the following steps to configure a split tunnel to include or exclude traffic based on the destination domain or application process name.
    1. Before you begin:
      1. Configure a GlobalProtect gateway.
      2. Select NetworkGlobalProtectGateways<gateway-config> to modify an existing gateway or add a new one.
    2. Enable a split tunnel.
      1. In the GlobalProtect Gateway Configuration dialog, select AgentTunnel Settings to enable Tunnel Mode.
      2. Configure the tunnel parameters for the GlobalProtect app.
    3. (Tunnel Mode only) Configure split tunnel settings based on the destination domain. These settings are assigned to the virtual network adapter on the endpoint when the GlobalProtect app establishes a tunnel with the gateway.
      You might experience some incompatibility issues when using a third-party endpoint security product such as Sophos on macOS endpoints.
      1. In the GlobalProtect Gateway Configuration dialog, select AgentClient Settings<client-setting-config> to select an existing client settings configuration or add a new one.
      2. (Optional) Add the SaaS or public cloud applications that you want to route to GlobalProtect through the VPN connection using the destination domain and port (Split TunnelDomain and ApplicationInclude Domain). You can add up to 200 entries to the list. For example, add *.gmail.com to allow all Gmail traffic to go through the VPN tunnel.
      3. (Optional) Add the SaaS or public cloud applications that you want to exclude from the VPN tunnel using the destination domain and port (Split TunnelDomain and ApplicationExclude Domain). You can add up to 200 entries to the list. For example, add *.target.com to exclude all Target traffic from the VPN tunnel.
      4. Click OK to save the split tunnel settings.
    4. (Tunnel Mode only) Configure split tunnel settings based on the application.
      Safari traffic cannot be added to the application-based split tunnel rule on macOS endpoints.
      You can use environment variables to configure a split tunnel based on the application on Windows and macOS endpoints.
      1. In the GlobalProtect Gateway Configuration dialog, select AgentClient Settings<client-setting-config> to select an existing client settings configuration or add a new one.
      2. (Optional) Add the SaaS or public cloud applications that you want to route to GlobalProtect through the VPN connection using the application process name (Split TunnelDomain and ApplicationInclude Client Application Process Name. You can add up to 200 entries to the list. For example, add /Applications/RingCentral for Mac.app/Contents/MacOS/Softphone to allow all RingCentral-based traffic to go through the VPN tunnel on macOS endpoints.
      3. (Optional) Add the SaaS or public cloud applications that you want to exclude from the VPN tunnel using the application process name (Split TunnelDomain and ApplicationExclude Client Application Process Name). You can add up to 200 entries to the list. For example, add /Applications/Microsoft Lync.app/Contents/MacOS/Microsoft Lync to exclude all Microsoft Lync application traffic from the VPN tunnel.
      4. Click OK to save the split tunnel settings.
    5. Save the gateway configuration.
      1. Click OK to save the gateway configuration.
      2. Commit your changes.

    © 2024 Palo Alto Networks, Inc. All rights reserved.