---
title: "Complete the Client Routing fields to configure routes for a Site."
slug: "client-routing-v6-6"
description: "Configure Client routing configurations for a Site, including Entitlement and Subnet Based Routing for optimal traffic management."
updated: 2026-02-06T21:05:57Z
published: 2026-02-06T21:05:57Z
canonical: "support.appgate.com/client-routing-v6-6"
---

> ## 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.

# Client Routing

The Client Routing section of the **Add/Edit Site** page defines the configuration of Client routes, ensuring the users' traffic is directed to one of the Site's Gateways. See [Routing Client traffic](/v1/docs/routing-client-traffic-v6-6) for more information.

Complete the following fields to configure Client routes:

- ***Type of Routing.***

- *Entitlement Based Routing.* The Gateway will send resolved Entitlements to the Client. These will be used to configure the required routes to the Sites. EBR is enabled by default.
- *Subnet Based Routing.* Static subnets will be used by the Client to configure routes to Sites. They may be used with Entitlement Based Routing. Add a subnet and a note to help identify its use. If you add 0.0.0.0/0 to capture all the traffic towards this Site - this will be translated into two routes in the Clients: 0.0.0.0/1 and 128.0.0.0/1.
- *Route all traffic through tunnel (Default Gateway).* All other Client traffic will be routed to this Site in the Collective which will serve as the default gateway. Remember to add suitable Entitlements for this Site.

![List of network actions allowing various protocols and ports for traffic management.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag62-def_ents.png?sv=2026-02-06&spr=https&st=2026-10-26T23%3A24%3A26Z&se=2026-10-27T00%3A24%3A26Z&sr=c&sp=r&sig=A3Xa2TsCkBPiyvISoM%2BI8SOTW2JfHsSTPsA4eOSZwHc%3D)

- **Excluded Subnets***.* It might be a requirement to exclude certain Subnets from the default gateway Site such as IP addresses on the local network. Use the same format here as for Subnet Based Routing.

> [!NOTE]
> **NOTE**
> 
> If Advanced Ringfence is enabled then these Excluded Subnets will be honored and not blocked.