[Magic] Tunnels patch (#28052)

marciocloudflare · web-flow · commit 5de97a4d42f1 · 2026-02-04T10:34:01.000Z
* added link

* refined text

* var

* corrected cond render

* refined text

* refined text

* refined names
diff --git a/src/content/changelog/magic-wan/2025-11-06-automatic-return-routing-beta.mdx b/src/content/changelog/magic-wan/2025-11-06-automatic-return-routing-beta.mdx
@@ -14,6 +14,6 @@ Key benefits:
 - **Overlapping IP space support**: Traffic originating from customer sites can use overlapping private IP ranges.
 - **Symmetric routing**: Return traffic is guaranteed to use the same connection as the original on-ramp.
 
-This feature is currently in Beta and requires the new Unified Routing mode.
+This feature is currently in beta and requires the new Unified Routing mode (beta).
 
 For configuration details, refer to [Configure Automatic Return Routing](/magic-wan/configuration/manually/how-to/configure-routes/#configure-automatic-return-routing-beta).
diff --git a/src/content/changelog/magic-wan/2026-01-27-configure-cloudflare-source-ips.mdx b/src/content/changelog/magic-wan/2026-01-27-configure-cloudflare-source-ips.mdx
@@ -21,6 +21,6 @@ Key details:
 - **IPv6**: Sourced from `2606:4700:cf1:5000::/64` (not configurable)
 - **Affected connectors**: GRE, IPsec, CNI, WARP Connector, and WARP Client (Cloudflare Tunnel is not affected)
 
-Configuring Cloudflare source IPs requires Cloudflare One Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
+Configuring Cloudflare source IPs requires Unified Routing (beta) and the `Cloudflare One Networks Write` permission.
 
 For configuration details, refer to [Configure Cloudflare source IPs](/magic-wan/configuration/manually/how-to/configure-cloudflare-source-ips/).
diff --git a/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/index.mdx
@@ -30,7 +30,7 @@ import { Render, Details} from "~/components";
 </Details>
 
 :::note
-Accounts on Legacy routing mode do not support WARP Connector when [Magic WAN](/magic-wan/) is enabled. Your account needs to be on the Cloudflare One Unified Routing for this to be supported. Contact your account team for more information.
+Accounts on Legacy routing mode do not support WARP Connector when [Magic WAN](/magic-wan/) is enabled. Your account needs to be on Unified Routing (beta) for this to be supported. Contact your account team for more information.
 :::
 
 Cloudflare WARP Connector (beta) is a software client[^1] that enables site-to-site, bidirectional, and mesh networking connectivity without requiring changes to underlying network routing infrastructure. WARP Connector establishes a secure Layer 3 proxy between a private network and Cloudflare, allowing you to:
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-tunnel-endpoints.mdx
@@ -28,6 +28,7 @@ import { GlossaryTooltip, Render } from "~/components";
 		configureRoutesURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-routes/",
 		sitesURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/common-settings/sites/",
 		configureARRURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/manually/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/cloudflare-one/networks/connectors/wan-tunnels/reference/traffic-steering/#unified-routing-mode-beta",
 		troubleshootTunnelHealthURL: "/cloudflare-one/networks/connectors/wan-tunnels/troubleshooting/tunnel-health/",
 		troubleshootIpsecURL: "/cloudflare-one/networks/connectors/wan-tunnels/troubleshooting/ipsec-troubleshoot/"
 	}}
diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx
@@ -22,6 +22,7 @@ import { GlossaryTooltip, Render } from "~/components";
 		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
 		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
 		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
 	}} />
diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx
@@ -24,6 +24,7 @@ import { Render } from "~/components";
 		tunnelHealthDash: "/magic-transit/network-health/check-tunnel-health-dashboard/",
 		biVsUniHealthCheckDefaults: "For Magic Transit this option defaults to unidirectional",
 		configureRoutesURL: "/magic-transit/how-to/configure-routes/",
+		unifiedRoutingURL: "/magic-transit/reference/traffic-steering/#unified-routing-mode-beta",
 		troubleshootTunnelHealthURL: "/magic-transit/troubleshooting/tunnel-health/",
 		troubleshootIpsecURL: "/magic-transit/troubleshooting/ipsec-troubleshoot/"
 	}}
diff --git a/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx
@@ -29,6 +29,7 @@ import { GlossaryTooltip, Render } from "~/components";
 		configureRoutesURL: "/magic-wan/configuration/manually/how-to/configure-routes/",
 		sitesURL: "/magic-wan/configuration/common-settings/sites/",
 		configureARRURL: "/magic-wan/configuration/manually/how-to/configure-routes/#configure-automatic-return-routing-beta",
+		unifiedRoutingURL: "/magic-wan/reference/traffic-steering/#unified-routing-mode-beta",
 		troubleshootTunnelHealthURL: "/magic-wan/troubleshooting/tunnel-health/",
 		troubleshootIpsecURL: "/magic-wan/troubleshooting/ipsec-troubleshoot/"
 	}}
diff --git a/src/content/partials/networking-services/reference/traffic-steering.mdx b/src/content/partials/networking-services/reference/traffic-steering.mdx
@@ -149,7 +149,7 @@ Cloudflare adjusts route priority when using AS prepending with communities. For
 		<AnchorHeading title="Automatic Return Routing (beta)" depth={2} />
 		<Markdown
 		text={`
-Automatic Return Routing (ARR) allows Cloudflare to track network flows from your Magic WAN connected locations, ensuring return traffic is routed back to the connection where it was received without requiring static or dynamic routes. This functionality requires the new [Unified Routing mode](#unified-routing-mode).
+Automatic Return Routing (ARR) allows Cloudflare to track network flows from your Magic WAN connected locations, ensuring return traffic is routed back to the connection where it was received without requiring static or dynamic routes. This functionality requires the new [Unified Routing mode (beta)](#unified-routing-mode-beta).
 
 Instead of relying on static or dynamic routes for the return path, Magic WAN learns flows and remembers which connection a given flow arrived on. For any matching return traffic, Magic WAN uses this learned state to choose the next hop. This simplifies configuration, reduces the number of routes you must manage, and helps preserve symmetry for stateful traffic.
 
@@ -203,20 +203,17 @@ In this initial release, ARR does not change routing for traffic between Magic W
 		inline={false}
 		/>
 
-		<AnchorHeading title="Unified routing mode (beta)" depth={2} />
-		<Markdown
-		text={`
-The Unified routing mode is the newer Cloudflare One data plane that uses a single routing fabric for all supported connection types. Unified routing mode routes traffic across WARP, Cloudflare Tunnel, IPsec, GRE, and Cloudflare Network Interconnect (CNI) in a single system, making it easier to set up your Cloudflare One connections.
+	</>
+)}
+
+## Unified Routing mode (beta)
+
+The Unified Routing mode is the newer Cloudflare One data plane that uses a single routing fabric for all supported connection types. Unified Routing mode routes traffic across WARP, Cloudflare Tunnel, IPsec, GRE, and Cloudflare Network Interconnect (CNI) in a single system, making it easier to set up your Cloudflare One connections.
 
-In the Magic WAN dashboard, routing mode appears where you manage Magic routes:
+In the {props.productName} dashboard, routing mode appears where you manage Magic routes:
 
 - **Routing mode: Unified** — your account is on the unified data plane and supports the new routing features.
 - **Routing mode: Legacy** — your account uses the previous data plane and does not support all unified routing features.
-		`}
-		inline={false}
-		/>
-	</>
-)}
 
 ## Scoping routes to specific regions
 
diff --git a/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx b/src/content/partials/networking-services/routing/configure-cloudflare-source-ips.mdx
@@ -41,7 +41,7 @@ The following Connectors are affected:
 ## Configure source IPs
 
 :::note
-You need Cloudflare One Unified Routing to configure source IPs. If your account is not yet on Unified Routing, contact your account team to discuss migration and availability.
+You need Unified Routing (beta) to configure source IPs. If your account is not yet migrated, contact your account team to discuss migration and availability.
 :::
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/partials/networking-services/routing/configure-routes.mdx b/src/content/partials/networking-services/routing/configure-routes.mdx
@@ -365,7 +365,7 @@ Example:
 		<AnchorHeading title="Configure Automatic Return Routing (beta)" depth={2} />
 		<Markdown
 		text={`
-		[Automatic Return Routing (beta)](${props.arrReferenceURL}) allows Cloudflare to track network flows from your Magic WAN connected locations, ensuring return traffic is routed back to the connection where it was received without requiring static or dynamic routes. This functionality requires the new [Unified Routing mode](${props.unifiedRoutingModeURL}).
+		[Automatic Return Routing (beta)](${props.arrReferenceURL}) allows Cloudflare to track network flows from your Magic WAN connected locations, ensuring return traffic is routed back to the connection where it was received without requiring static or dynamic routes. This functionality requires the new [Unified Routing mode (beta)](${props.unifiedRoutingModeURL}).
 
 		To enable ARR:
 		`}
diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx
@@ -15,6 +15,7 @@ params:
   - configureRoutesURL
   - sitesURL?
   - configureARRURL?
+  - unifiedRoutingURL
   - troubleshootTunnelHealthURL
   - troubleshootIpsecURL
 ---
@@ -139,7 +140,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
 { props.magicWord !== "Magic Transit" && (<Markdown text={`16. (Optional) Select **Automatic return routing** if you are setting up this tunnel for a site that only needs to send traffic to and receive responses from Cloudflare, and does not need to receive traffic from other sites in your WAN. Refer to [Configure Automatic Return Routing](${props.configureARRURL}) for more information.`} inline={false} />)}
 <Markdown text={`${props.magicWord !== "Magic Transit" ? "17" : "16"}. To add multiple tunnels, select **Add GRE tunnel** for each new tunnel.`} inline={false} />
 <Markdown text={`${props.magicWord !== "Magic Transit" ? "18" : "17"}. After adding your tunnel information, select **Add tunnels**.`} inline={false} />
-<Markdown text={`${props.magicWord !== "Magic Transit" ? "19" : "18"}. (Optional) Select **Allow BGP (Border Gateway Protocol) peering** (beta) if you want to dynamically exchange routes between your network and Cloudflare. BGP is recommended for environments with frequently changing routes or when you need automatic failover. Refer to [Configure BGP routes](${props.configureRoutesURL}#configure-bgp-routes) for more information.`} inline={false} />
+<Markdown text={`${props.magicWord !== "Magic Transit" ? "19" : "18"}. (Optional) Select **Allow BGP (Border Gateway Protocol) peering** (beta) if you want to dynamically exchange routes between your network and Cloudflare. This feature requires <a href="${props.unifiedRoutingURL}">Unified Routing (beta)</a>. <br /> BGP is recommended for environments with frequently changing routes or when you need automatic failover. Refer to [Configure BGP routes](${props.configureRoutesURL}#configure-bgp-routes) for more information.`} inline={false} />
 
 </Details>
 
@@ -179,7 +180,7 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
 { props.magicWord !== "Magic Transit" && (<Markdown text={`17. (Optional) Select **Automatic return routing** if you are setting up this tunnel for a site that only needs to send traffic to and receive responses from Cloudflare, and does not need to receive traffic from other sites in your WAN. Refer to [Configure Automatic Return Routing](${props.configureARRURL}) for more information.`} inline={false} />)}
 <Markdown text={`${props.magicWord !== "Magic Transit" ? "18" : "17"}. To add multiple tunnels, select **Add IPsec tunnel** for each new tunnel.`} inline={false} />
 <Markdown text={`${props.magicWord !== "Magic Transit" ? "19" : "18"}. After adding your tunnel information, select **Add tunnels**.`} inline={false} />
-<Markdown text={`${props.magicWord !== "Magic Transit" ? "20" : "19"}. (Optional) Select **Allow BGP (Border Gateway Protocol) peering** (beta) if you want to dynamically exchange routes between your network and Cloudflare. BGP is recommended for environments with frequently changing routes or when you need automatic failover. Refer to [Configure BGP routes](${props.configureRoutesURL}#configure-bgp-routes) for more information.`} inline={false} />
+<Markdown text={`${props.magicWord !== "Magic Transit" ? "20" : "19"}. (Optional) Select **Allow BGP (Border Gateway Protocol) peering** (beta) if you want to dynamically exchange routes between your network and Cloudflare. This feature requires <a href="${props.unifiedRoutingURL}">Unified Routing (beta)</a>. <br /> BGP is recommended for environments with frequently changing routes or when you need automatic failover. Refer to [Configure BGP routes](${props.configureRoutesURL}#configure-bgp-routes) for more information.`} inline={false} />
 
 </Details>
 
