---
title: "Complete the Client Routing fields to configure routes for a Site."
slug: "client-routing-v6-7"
description: "Configure Client routing configurations for a Site, including Entitlement and Subnet Based Routing for optimal traffic management."
updated: 2026-03-16T19:49:45Z
published: 2026-04-03T16:41:06Z
canonical: "support.appgate.com/client-routing-v6-7"
---

> ## 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-7) for more information.

Complete the following fields to configure client routes:

- ***Type of Routing.***

- *Entitlement Based Routing.* In entitlement-based routing (EBR), the Gateway will send resolved entitlements to the client. These entitlements will be used to configure required routes to the Sites. EBR is enabled by default.
- *Subnet Based Routing.* In subnet-based routing (SBR), static subnets will be used by the client to configure routes to Sites. They may be used with EBR. Add a subnet and a note to identify its use. If you add 0.0.0.0/0 to capture all 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-26T22%3A30%3A42Z&se=2026-10-26T23%3A30%3A42Z&sr=c&sp=r&sig=WFD8FnuHCSrG5W3%2F68RpC8sSDu7KBnYjHhFRG02mOHo%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 SBR.

> [!NOTE]
> **NOTE**
> 
> If *Advanced Ringfence* is enabled, the excluded subnets will be honored and not blocked.