--- title: "Routing client traffic" slug: "routing-client-traffic-v7-0" description: "Learn about multi-tunnel network drivers, client routing, and how to optimize traffic through gateways for secure, efficient network management." tags: ["Client Routing", "Tunneled Traffic"] updated: 2026-08-21T20:19:21Z published: 2026-08-21T20:19:24Z canonical: "support.appgate.com/routing-client-traffic-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Routing client traffic Every entitlement you configure must relate to a default Site, which is that entitlement's home. The multi-tunnel network driver sets up a tunneled connection to each Site following the [Software Defined Perimeter (SDP) model](/v1/docs/tunnel-architectures-v7-0#software-defined-perimeter-network-model). Once a connection is established to a Gateway, the client sets up the client routes to send traffic down the appropriate tunnel. The Gateway then routes the tunneled traffic onto the protected network. AppGate ZTNA supports SNAT and non-SNAT, and includes options for setting a tunneled default route from devices. See [Configuring Sites](/v1/docs/configuring-sites-v7-0) to control how user traffic is handled. --- ## Client routing The multi-tunnel virtual network driver sets routes in two ways: ***Entitlement Based Routing*** and ***Site Based Routing***. A special use case for Site based routing is when you want to use a [default gateway](/v1/docs/routing-client-traffic-v7-0#default-gateway) for traffic. ***Entitlement Based Routing (EBR)***. The Gateway sends resolved entitlements to the client. The client uses these to configure the required routes to the Sites. This is the default setting. It is automated—routes follow the entitlements. ***Subnet Based Routing (SBR)***. The client uses static subnets to configure routes to Sites. SBR can be used with EBR. These routes must be manually added in [System > Sites > Client Routing](/v1/docs/configuring-sites-v7-0#client-routing). Each method has trade-offs; consider route complexity when choosing between them. ### Route complexity EBR is based on entitlements. This means hundreds of individual /32 routes may all fall within one subnet. Mobile operating systems do not handle that level of complexity well. In addition, cloud-based name resolvers produce many frequently changing entitlements that require the mobile VPN service to restart on each change. These issues cause unreliability and a poor user experience. AppGate ZTNA clients therefore use a route optimization algorithm to mitigate these effects. If you plan to deploy on iPadOS, iOS, Android, and ChromeOS, configure the system to use route optimization. Route optimization ignores more specific routes already covered by other routes. For example, if a /22 route is specified, the client does not set up any of the 1,024 /32 routes it contains. To use route optimization, you have two options: - Create an entitlement for your subnet (/22) network using the [block rule](/v1/docs/configuring-entitlements-v7-0). A /22 route is set and all traffic is forwarded to (and blocked at) the Gateway. The EBR-generated /32 allow rules will not need a matching route setting because they are more specific (/32 vs /22). Similarly, the /32 rule is allowed by the Gateway because the most specific rule wins. By adding a condition to the block entitlement, you restrict which users or devices this applies to (such as mobile devices). - Add an SBR /22 subnet (as well as using EBR normally). This applies to all users of the Site. --- ## Routing tunneled traffic Clients establish a secure tunneled connection to an available Gateway on each Site based on preset weighting. The multi-tunnel network driver is assigned an IP address from the IP pool, so tunneled client-to-Gateway connections appear like any other network-connected device. The tunnel supports many protocols, such as TCP, UDP, GRE, and ICMP, as well as both up and down traffic. This allows for the deployment of more complex systems such as IP telephony. AppGate ZTNA provides default IP pools for both IPv4 and IPv6, and supports tunneled traffic of either type. IPv4 tunneled traffic always uses the IPv4 tunnel; IPv6 traffic always uses the IPv6 tunnel. See [IP pools](/v1/docs/ip-pools-v7-0) for more information. Each user or device presents the same IP address on all Sites unless [IP pool mappings](/v1/docs/ip-pools-v7-0#ip-pool-mappings1) are used. Gateways on each Site are seen as virtual routers to the tunneled IP pool address range used by the multi-tunnel virtual network drivers. [*Disable Source NAT on Gateways*](/v1/docs/configuring-sites-v7-0#tunneling) is disabled by default, so Gateways will perform source NAT. This provides immediate compatibility with most network environments. This is not ideal for traceability. To improve traceability, select the *Log NAT-IP and NAT-port* checkbox on the **Edit Site** page at [Sites > Tunneling](/v1/docs/configuring-sites-v7-0#tunneling). Some of the options detailed below work with *Disable Source NAT on Gateways* enabled. In this mode, ensure the Gateways' local network supports ARP (or Neighbor Discovery [ND] in IPv6 networks), which advertises the non-SNATed IP addresses the Gateway handles. > [!NOTE] > **NOTE** > > Most cloud environments do not support ARP/ND. The following sections describe typical scenarios for routing tunneled traffic in AppGate ZTNA deployments. ### Simple single network (using SNAT) In the example below, all user traffic (from IP pool 192.168.100.64–192.168.100.254) appears to come from the Gateways’ IP addresses (192.169.100.10, .11, and .12). All traffic is routable on the local network behind the Gateways because the IP pool and the local network share the same subnet. The IP pool does not overlap with the addresses of the machines on the local network. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/routing1.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A31Z&se=2026-11-21T22%3A29%3A31Z&sr=b&sp=r&sig=Kc6fhTnuYx7pBGUbkoMlbCTDTiiLR7h934Tn5GD65VI%3D) One issue with SNAT is that it breaks the relationship between the user's identity and traffic on the local network. Some security requirements demand that this link be maintained to support a detailed audit trail. A Site option to enable NAT-IP and NAT-port logs adds two additional records to the IP access audit log. ### Multiple, larger routed networks (using SNAT) In enterprises, multiple networks may exist and users require separately-managed IP pools. As long as *Disable Source NAT on Gateways* is disabled, this will work as before with Gateways performing SNAT from the 192.168.100.64-254 address range to the 172.17.111.x IP address (shown in black) of the respective Gateway. In larger networks with 4,000 users, for example, you may need to specify a /20 IP pool. Because *Disable Source NAT on Gateways* is disabled, each user is assigned a unique source port per TCP/UDP stream on the Gateway’s IP address. With 4,000 users on a Gateway, each with 16 actions, the Gateway approaches the 65,535 stream limit per IP address. When Gateway source NAT is in use, the *SNAT pool* feature makes it possible to [add multiple sequential IP address aliases on a Gateway interface](/v1/docs/adding-a-new-appliance-v7-0#system-settings) (shown in gray) to the SNAT pool. This multiplies the SNAT connection stream limit by the number of selected interfaces. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/routing2.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A31Z&se=2026-11-21T22%3A29%3A31Z&sr=b&sp=r&sig=zoX%2FknG65W%2Bt2pmUPSoqKkSzkYb9CYrQ%2FP5u8hrOe9Q%3D) - With only one IP address configured on an interface, there is no requirement to configure the SNAT pool. - With two or more IP addresses configured, the first IP address is always used if SNAT pool is not enabled anywhere. - With two or more IP addresses configured, all the IP addresses configured with SNAT pool are used. - With two or more IP addresses configured, and all but one of the IP addresses configured with SNAT pool, the addresses with SNAT pool enabled are used for outbound connections to the protected hosts leaving the remaining one available for inbound client connections. One issue with SNAT is that it breaks the relationship between the user's identity and traffic on the local network. Some security requirements demand that this link be maintained to support a detailed audit trail. A Site option to enable NAT-IP and NAT-port logs adds two additional records to the IP access audit log. ### Multiple routed networks (without SNAT) If you plan to use down rules (reverse connections) or need an audit trail by IP address, enable *Disable Source NAT on Gateways*. Client IP addresses are then visible on the protected network and appear to come from the 192.168.100.64-254 address range rather than the Gateway's IP address. User traffic 192.168.100.64-254 follows the default gateway routing—set to 172.17.111.1 in the example below. The route added to the router ensures reverse traffic destined for the IP pool routes correctly over the 172.17.111 network to the Gateways. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/routing3.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A31Z&se=2026-11-21T22%3A29%3A31Z&sr=b&sp=r&sig=RkTlzUQyBwdLXY70UyFBzfG4ZBhDzxeTa8OTVOgo%2FHk%3D) The Gateways use proxy ARP to announce these on the local (172.17.111.0/24) network. By adding the route 192.168.100.64-254 to the local network interface IP of the router, the router performs an ARP request on its local network. Each Gateway responds to ARP requests for tunnel IPs currently connected to that Gateway. When a failover event moves the tunnel IP from one Gateway to another, the new Gateway sends a gratuitous ARP (an unsolicited ARP message that a device sends to itself to check for duplicate IP addresses) to notify the router of the change and update its ARP table. Because the tunnel IP can now be announced on any Gateway, all Gateways are active in this setup. > [!NOTE] > **NOTE** > > Gateways do not share state information, which makes them linearly scalable. ### Routing using IP aliases (without SNAT) Some firewalls do not allow you to set additional routes to the local network interface. In this situation, use a slightly different configuration. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/routing4.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A31Z&se=2026-11-21T22%3A29%3A31Z&sr=b&sp=r&sig=GESQ%2FUVF45Sg5XKK1uun1Nm%2FgD50vuihyeWbiOAm6Tg%3D) Add a second IP address alias and subnet mask to the router's local network interface. The IP address and subnet 192.168.100.1/24 must encompass the IP pool address range used by AppGate ZTNA (192.168.100.64-254). By adding this to the local network interface of the router, the router performs an ARP request for IP addresses in the range 192.168.100.2-254 on the local network. Each Gateway responds to these ARP requests for tunnel IPs currently connected to that Gateway, so the behavior is the same as in the previous example. While not required, this example also shows IP address aliases within the same subnet on the Gateways (which must sit outside the IP pool address range to avoid any IP conflicts). ### Default Gateway By default, AppGate ZTNA performs split-tunneling. EBR or SBR captures and routes specific traffic for t protected hosts, and the remaining traffic (such as internet access) is untouched by AppGate ZTNA. You can configure AppGate ZTNA to route all remaining traffic through a tunnel from the user's device to allow the use of a remote default Gateway (accessed through an AppGate ZTNA Site). Use this when a security policy requires a specific network appliance to firewall, filter, or process user traffic. > [!NOTE] > **NOTE** > > Do not use this configuration with the multi-user client. #### Configuring a default Gateway To configure a default Gateway: - Set up a separate default Gateway Site to be the destination for the default Gateway traffic. - In Site > Client Routing, enable [*Route all traffic through tunnel*](/v1/docs/configuring-sites-v7-0#client-routing). This disables split-tunneling and routes all remaining traffic to the default gateway Site. - This is a special case of SBR, so you need to add an [entitlements action](/v1/docs/configuring-entitlements-v7-0#access-rights) for the Site with an *ALLOW* traffic rule set for `0.0.0.0/0` or `::0/0`, with port range `1-65535` to allow traffic through the Gateways' firewall. > [!NOTE] > **NOTE** > > Only one default route should be assigned to any connecting device. (See [Accessing the nearest geolocated Site](/v1/docs/tunnel-architectures-v7-0#accessing-the-nearest-geolocated-site) if you operate several default Gateways.) #### Exclude your local network To exclude your local network and retain access to local devices, create another [entitlement action](/v1/docs/configuring-entitlements-v7-0) with a suitable *EXCLUDE* route rule. > [!NOTE] > NOTE > > The *EXCLUDE* route feature is not supported on Android. #### Alternative default route Sometimes user traffic must be handled differently from appliance-generated traffic (such as LDAP queries). An alternative default route for all user traffic lets you send that traffic to a different default Gateway. - In the **Sites** page, select the Site for which you want to use an alternative default route. Under Tunneling, enable [*Alternative default route for all user traffic*](/v1/docs/configuring-sites-v7-0#tunneling) and options will appear to set both IPv4 and IPv6 addresses for the default Gateways. In the example below, all user traffic (from the IP pool 192.168.100.64-192.168.100.254) appears to be coming from the Gateways' IP addresses (172.17.111.10,11,12). The IPv4 address for the alternative default route for tunneled traffic has been set to 172.17.111.2, which is applied to all three Gateways. The appliance's own traffic continues to be sent to 172.17.111.1. ![](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/routing5.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A31Z&se=2026-11-21T22%3A29%3A31Z&sr=b&sp=r&sig=gjaUTeUD9pEk8jHPxPk5pGhBH%2FqdHBb%2FuqfWFuyo8Xk%3D)