From dea5ffa83bef7eb9501ff70a3bbb638e6d029cc7 Mon Sep 17 00:00:00 2001
From: Doneven2012 <37813014+Doneven2012@users.noreply.github.com>
Date: Fri, 6 Dec 2024 10:58:21 -0500
Subject: [PATCH 1/2] Update warp-to-warp.mdx - Split tunnel Exclude mode
Instead of simply excluding 100.96.0.0/12 from split tunneling in Exclude mode, this removes only the CGNAT IP range that CloudFlare WARP need. Info taken from another page on the CloudFlare documentation.
https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/private-net/warp-connector/user-to-site/#3-route-cgnat-ips-through-cloudflare
---
.../connect-networks/private-net/warp-to-warp.mdx | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
index 15b2580a0f9582..3c5f92d434727f 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
@@ -34,8 +34,11 @@ This guide covers how to:
3. Enable **Warp-to-Warp**. This allows Cloudflare to route traffic to the CGNAT IP 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 **Include** mode, add `100.96.0.0/12` to your list.
+- If using **Exclude** mode:
+ - Remove `100.96.0.0/12` from your list.
+ - 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.
From 993d4099dfa9b51fee9431834ac87e94503ef8e8 Mon Sep 17 00:00:00 2001
From: ranbel <101146722+ranbel@users.noreply.github.com>
Date: Fri, 6 Dec 2024 16:53:13 -0500
Subject: [PATCH 2/2] Update warp-to-warp.mdx
---
.../connect-networks/private-net/warp-to-warp.mdx | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
index 3c5f92d434727f..eca7cd0ef94f8d 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx
@@ -34,11 +34,8 @@ This guide covers how to:
3. Enable **Warp-to-Warp**. This allows Cloudflare to route traffic to the CGNAT IP 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.
- - 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 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.