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 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.
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
If Advanced Ringfence is enabled then these Excluded Subnets will be honored and not blocked.