Skip to content

[Gateway] CIDR ranges for FQDN selectors in split tunnel/warp-to-warp #26242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 3, 2025
+14 −4
Merged

[Gateway] CIDR ranges for FQDN selectors in split tunnel/warp-to-warp #26242

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7de6666
[Gateway] CIDR ranges for FQDN selectors in split tunnel/warp-to-warp
Maddy-Cloudflare Nov 3, 2025
ae12c36
Apply suggestions from code review
Maddy-Cloudflare Nov 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions ...oudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-to-warp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,16 @@ This guide covers how to:
3. Enable **Allow WARP to WARP connection**. This allows Cloudflare to route traffic to the <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> space.
4. In your [Split Tunnel configuration](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/), ensure that traffic to `100.96.0.0/12` is going through WARP:

- If using **Exclude** mode, delete `100.64.0.0/10` from the list and re-add `100.64.0.0/11` and `100.112.0.0/12`.
- If using **Include** mode, add `100.96.0.0/12` to your list.
- If using **Exclude** mode, delete `100.64.0.0/10` from the list and the following IP addresses:

- `100.64.0.0/12`
- `100.81.0.0/16`
- `100.82.0.0/15`
- `100.84.0.0/14`
- `100.88.0.0/13`
- `100.112.0.0/12`

- If using **Include** mode, add `100.96.0.0/12` and `100.80.0.0/16` to your list.

This will instruct WARP to begin proxying any traffic destined for a `100.96.0.0/12` IP address to Cloudflare for routing and policy enforcement.

Expand Down
6 changes: 4 additions & 2 deletions ...content/docs/cloudflare-one/traffic-policies/egress-policies/host-selectors.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,11 +102,13 @@ To configure your Zero Trust organization to use Host selectors with Egress poli
- `100.82.0.0/15`
- `100.84.0.0/14`
- `100.88.0.0/13`
- `100.96.0.0/11`
- `100.112.0.0/12`

And remove `100.64.0.0/10` IP address.

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

</TabItem> </Tabs>

Expand Down