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. 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.
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
If Advanced Ringfence is enabled, the excluded subnets will be honored and not blocked.