Skip to content

Update warp-to-warp.mdx - Split tunnel Exclude mode #18609

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
Dec 6, 2024
Merged

Update warp-to-warp.mdx - Split tunnel Exclude mode #18609

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dea5ffa
Update warp-to-warp.mdx - Split tunnel Exclude mode
Doneven2012 Dec 6, 2024
993d409
Update warp-to-warp.mdx
ranbel Dec 6, 2024
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
2 changes: 1 addition & 1 deletion ...t/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ This guide covers how to:
3. Enable **Warp-to-Warp**. This allows Cloudflare to route traffic to the <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> space.
4. In your [Split Tunnel configuration](/cloudflare-one/connections/connect-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, remove `100.96.0.0/12` from your list.
- 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.

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
Loading