link to new reserved IPs page

Author: ranbel

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/user-to-site.mdx

@@ -42,7 +42,7 @@ WARP clients and WARP Connectors are accessed using their [device IP](/cloudflar
 
 1. In your WARP Connector device profile, go to [Split Tunnels](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/).
 2.
-	<Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" params={{ feature: "WARP Connector"}}  />
+	<Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" />
 
 3. Repeat the previous steps for all WARP client device profiles.
 

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-to-warp.mdx

@@ -34,7 +34,7 @@ This guide covers how to:
 3. Turn on [**Allow all Cloudflare One traffic to reach enrolled devices**](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-settings/#allow-all-cloudflare-one-traffic-to-reach-enrolled-devices).
 4. Go to **Team & Resources** > **Devices** > **Device profiles** > **General profiles** and select the device group that needs WARP-to-WARP connectivity.
 5.
-	<Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" params={{ feature: "WARP-to-WARP"}} />
+	<Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" />
 
 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.
 

src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx

@@ -2,25 +2,10 @@
 {}
 ---
 
-import { Tabs, TabItem, Render, GlossaryTooltip } from "~/components"
+import { Render, GlossaryTooltip } from "~/components"
 
-In your WARP [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel. Refer to the steps below for your Split Tunnels mode:
+In your WARP [device profile](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/), configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/) such that the <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> route through the WARP tunnel.  Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/#change-split-tunnels-mode):
 
-   <Tabs> <TabItem label="Exclude IPs and domains">
-
-   1. [Remove the route](/cloudflare-one/team-and-resources/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.
-
-	 2. We recommend [adding back the IPs](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-warp) that are not being used for Zero Trust services. For example, if you are using <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> alongside [WARP-to-WARP connectivity](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-to-warp/), add routes to exclude 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`
-
-   </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 routes](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route) to include the following IP addresses:
+- **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#warp-split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
+- **Include mode**: Add Split Tunnel entries for the following IP addresses:
 	 	<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
-   </TabItem> </Tabs>

src/content/partials/cloudflare-one/tunnel/cgnat-split-tunnels.mdx

@@ -1,28 +1,8 @@
 ---
-params:
-  - feature
----
-
-import { TabItem, Tabs } from "~/components";
-
-Ensure that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-ips/) goes through the WARP tunnel. For example, if your devices use the default `100.96.0.0/12` range:
 
-    <Tabs> <TabItem label="Exclude IPs and domains">
-		If using Split Tunnels in **Exclude** mode:
-			1. Delete `100.64.0.0/10` from the list.
-			2. We recommend [adding back the IPs](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-warp) that are not being used for Cloudflare One services. For example, if you plan to use {props.feature} alongside [Gateway host selectors](/cloudflare-one/traffic-policies/egress-policies/host-selectors/), add routes to exclude 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`
-
-    </TabItem> <TabItem label="Include IPs and domains">
-		If using Split Tunnels in **Include** mode:
+---
 
-		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 `100.96.0.0/12`.
+In your device profile, configure [Split Tunnels](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/) so that traffic to your [device IPs](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-ips/) goes through the WARP tunnel. Configuration depends on your [Split Tunnels mode](/cloudflare-one/team-and-resources/devices/warp/configure-warp/route-traffic/split-tunnels/#change-split-tunnels-mode). For example, if your devices use the default `100.96.0.0/12` range:
 
-    </TabItem> </Tabs>
+- **Exclude mode**: Delete `100.64.0.0/10` from your Split Tunnels list. We recommend [adding back the IP ranges](/cloudflare-one/networks/routes/reserved-ips/#warp-split-tunnel-configuration) that are not explicitly used for Cloudflare One services. This reduces the risk of conflicts with existing private network configurations that may use the CGNAT address space.
+- **Include mode**: Add `100.96.0.0/12` to your Split Tunnels list.