Skip to content

Commit 0caa2c4

Browse files
committed
Rearrange egress load balancing
1 parent f61fc73 commit 0caa2c4

File tree

1 file changed

+1
-3
lines changed
  • src/content/docs/cloudflare-one/policies/gateway/egress-policies

1 file changed

+1
-3
lines changed

src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Cloudflare does not publish WARP egress IP ranges. WARP egress IPs are not docum
2121

2222
## Load balancing
2323

24-
Gateway traffic that does not match an egress policy will egress from the closest Cloudflare data center with a default Gateway egress IP. If there are two data centers of equal distance from the user, Gateway will split the traffic between the two data centers, and the load balancer will retain the same user selection and egress IP regardless of data center. This logic applies to both the default Cloudflare egress IPs and any dedicated egress IPs.
24+
When using either the default Cloudflare egress IPs or any dedicated egress IPs, Gateway traffic that does not match an egress policy will egress from the closest Cloudflare data center with a default Gateway egress IP. If there are two data centers of equal distance from the user, Gateway will split the traffic between the two data centers, and the load balancer will retain the same user selection and egress IP regardless of data center.
2525

2626
## Force IP version
2727

@@ -254,7 +254,6 @@ Additionally, to use these selectors to filter traffic onboarded with WARP, you
254254
2. In your WARP [device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/), configure your [Split Tunnel](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) depending on the mode:
255255

256256
<Tabs> <TabItem label="Exclude IPs and domains">
257-
258257
1. [Remove the route](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#remove-a-route) to the IP address `100.64.0.0/10` from your Split Tunnel exclude list.
259258
2. [Add routes](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route) to exclude the following IP addresses:
260259
- `100.64.0.0/12`
@@ -265,7 +264,6 @@ Additionally, to use these selectors to filter traffic onboarded with WARP, you
265264
- `100.96.0.0/11`
266265

267266
</TabItem> <TabItem label="Include IPs and domains">
268-
269267
1. Add the required [Zero Trust domains](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
270268
2. [Add a route](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route) to include the IP address `100.80.0.0/16`.
271269

0 commit comments

Comments
 (0)