cloudflare · marciocloudflare · Apr 17, 2025 · Apr 16, 2025 · Apr 16, 2025 · Apr 16, 2025
@@ -804,7 +804,7 @@
 # magic-transit
 /magic-transit/magic-firewall/ /magic-firewall/ 301
 /magic-transit/set-up/onboarding/ /magic-transit/get-started/ 301
-/magic-transit/set-up/provide-configuration-data/assign-tunnel-route-priorities/ /magic-transit/how-to/configure-static-routes/ 301
+/magic-transit/set-up/provide-configuration-data/assign-tunnel-route-priorities/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/set-up/requirements/ /magic-transit/get-started/ 301
 /magic-transit/get-started/configure-tunnels/specify-gre-tunnel-endpoints/ /magic-transit/how-to/configure-tunnels/ 301
 /magic-transit/about/health-checks/ /magic-transit/reference/tunnel-health-checks/ 301
@@ -814,6 +814,8 @@
 /magic-transit/prerequisites/ /magic-transit/get-started/ 301
 /magic-transit/how-to/ /magic-transit/how-to/configure-tunnels/ 301
 /magic-transit/reference/ /magic-transit/reference/anti-replay-protection/ 301
+/magic-transit/how-to/configure-static-routes/ /magic-transit/how-to/configure-routes/ 301
+/magic-transit/how-to/bgp-peering/ /magic-transit/how-to/configure-routes/ 301
 
 # magic-wan
 /magic-wan/tutorials/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
@@ -837,6 +839,8 @@
 /magic-wan/configuration/common-settings/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/prerequisites/ /magic-wan/get-started/ 301
 /magic-wan/configuration/common-settings/check-tunnel-health-dashboard/ /magic-wan/configuration/common-settings/tunnel-health-checks/ 301
+/magic-wan/configuration/manually/how-to/configure-static-routes/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
+/magic-wan/configuration/manually/how-to/bgp-peering/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
 
 # notifications
 /fundamentals/notifications/ /notifications/ 301

@@ -13,7 +13,7 @@ In addition to using Magic Transit with your own IP address, you can use Magic T
 To protect your network using a Cloudflare IP address, contact your account manager. After receiving your IP address, you will need to:
 
 - [Create a tunnel](/magic-transit/how-to/configure-tunnels/).
-- [Set up static routes](/magic-transit/how-to/configure-static-routes) or [BGP peering](/magic-transit/how-to/bgp-peering/).
+- [Set up static routes](/magic-transit/how-to/configure-routes/#configure-static-routes) or [BGP peering](/magic-transit/how-to/configure-routes/#configure-bgp-routes).
 - [Configure health checks](/magic-transit/how-to/run-endpoint-health-checks).
 - Confirm [tunnel](/magic-transit/how-to/tunnel-health-checks/) and endpoint health checks were properly configured.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.

@@ -99,7 +99,7 @@ Refer to [Maximum transmission unit and maximum segment size](/magic-transit/ref
 
 ## 4. Configure static routes or BGP peering
 
-Configure [static routes](/magic-transit/how-to/configure-static-routes/) or [BGP peering](/magic-transit/how-to/bgp-peering/) to route traffic from Cloudflare's global network to your locations.
+Configure [static routes](/magic-transit/how-to/configure-routes/#configure-static-routes) or [BGP peering](/magic-transit/how-to/configure-routes/#configure-bgp-routes) to route traffic from Cloudflare's global network to your locations.
 
 ## 5. Run pre-flight checks
 

@@ -89,12 +89,12 @@ When you withdraw a prefix using BGP, you must ensure the prefix is withdrawn ac
 
 ### BGP peering
 
-If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP peering](/magic-transit/how-to/bgp-peering/) to learn how to use BGP to handle traffic routing between Cloudflare and your network. Note that this is a different option to using BGP as a means to control the advertisement status of your prefix.
+If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP information](/magic-transit/reference/traffic-steering/#bgp-information) to learn how to use BGP to handle traffic routing between Cloudflare and your network. Note that this is a different option to using BGP as a means to control the advertisement status of your prefix.
 
 
 ### Regional settings
 
-Magic Transit requires static routing to steer traffic from Cloudflare's network over one of your configured tunnel off-ramps (for GRE and IPsec tunnels). For CNI, both static routing and [BGP](/magic-transit/how-to/bgp-peering/) options are available. Currently, advertisement of routes for traffic engineering purposes is not supported. As a best practice to reduce last-hop latency, you should consider scoping your routes regionally. The default setting for static route regions is **All Regions**. Refer to [Configure static routes](/magic-transit/how-to/configure-static-routes/) for more information.
+Magic Transit requires static routing to steer traffic from Cloudflare's network over one of your configured tunnel off-ramps (for GRE and IPsec tunnels). For CNI, both static routing and BGP options are available. Currently, advertisement of routes for traffic engineering purposes is not supported. As a best practice to reduce last-hop latency, you should consider scoping your routes regionally. The default setting for static route regions is **All Regions**. Refer to [Scoping routes to specific regions](/magic-transit/reference/traffic-steering/#scoping-routes-to-specific-regions) for more information.
 
 ## Example router configurations
 

@@ -0,0 +1,25 @@
+---
+pcx_content_type: how-to
+title: Configure routes
+sidebar:
+  order: 2
+head: []
+description: Magic Transit uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through Direct CNI you also have access to BGP peering. Learn how to configure routing.
+
+---
+
+import { Render } from "~/components"
+
+<Render
+	file="routing/configure-routes"
+	product="networking-services"
+	params={{
+		magicWord: "Magic Transit",
+		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
+		productName: "Magic Transit",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
+		productGatewayOrEgress: "Magic Transit with Egress"
+	}}
+/>
@@ -31,6 +31,4 @@ import { GlossaryTooltip, Render } from "~/components";
 
 ## Next steps
 
-Now that you have set up your tunnel endpoints, you need to configure <GlossaryTooltip term="static route" link="/magic-transit/how-to/configure-static-routes/">static routes</GlossaryTooltip> to route your traffic through Cloudflare.
-
-If you are connecting to Cloudflare through a [Direct CNI connection](/network-interconnect/express-cni/), you can [configure BGP routing](/magic-transit/how-to/bgp-peering/) instead.
+Now that you have set up your tunnel endpoints, you need to configure routes to route your traffic through Cloudflare. Refer to [Configure routes](/magic-transit/how-to/configure-routes/) to learn more about static routing and BGP peering (only available through Direct CNI connection).
@@ -39,7 +39,7 @@ Magic Transit steers traffic along tunnel routes based on priorities you define
 Use Cloudflare-owned IP addresses if you want to protect a smaller network and do not meet Magic Transit's `/24` prefix length requirements.
 </Feature>
 
-<Feature header="BGP peering" href="/magic-transit/how-to/bgp-peering/">
+<Feature header="BGP peering" href="/magic-transit/how-to/configure-routes/#configure-static-routes">
 Use BGP peering between your networks and Cloudflare to automate the process of adding or removing networks and subnets, and take advantage of failure detection and session recovery features.
 </Feature>
 

@@ -14,9 +14,13 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
-		greURL: "/magic-transit/reference/tunnels/",
-		staticRoutesURL: "/magic-transit/how-to/configure-static-routes/",
-		ipsecURL: "/magic-transit/reference/tunnels/#ipsec-tunnels",
+  	magicWord: "Magic Transit",
+  	productName: "Magic Transit",
+  	greIpsecReferenceURL: "/magic-transit/reference/tunnels/",
+  	createStaticRoute: "/magic-transit/how-to/configure-routes/#create-a-static-route",
+  	editStaticRoute: "/magic-transit/how-to/configure-routes/#edit-a-static-route",
+  	setupBgpPeering: "/magic-transit/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage: "/magic-transit/reference/tunnel-health-checks/"
 	}}
 />
@@ -16,7 +16,7 @@ import { Render } from "~/components";
 		changeHealthCheckRate: "/magic-transit/how-to/tunnel-health-checks/",
 		probeHealth: "#health-state-and-prioritization",
 		productName: "Magic Transit",
-		staticRoutes: "/magic-transit/how-to/configure-static-routes/",
+		staticRoutes: "/magic-transit/how-to/configure-routes/",
 		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/"
 	}}
 />
@@ -0,0 +1,29 @@
+---
+title: Configure routes
+pcx_content_type: how-to
+sidebar:
+  order: 2
+head: []
+description: Magic WAN uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through Direct CNI you also have access to BGP peering.  Learn how to configure routing.
+
+---
+
+import { Render } from "~/components"
+
+<Render
+	file="routing/configure-routes"
+	product="networking-services"
+	params={{
+		magicWord: "Magic WAN",
+		trafficSteeringPage: "/magic-wan/reference/traffic-steering/",
+		productName: "Magic WAN",
+		tunnelEndpoints: "/magic-wan/configuration/manually/how-to/configure-tunnels/",
+		chooseWeights: "/magic-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		publicAsnMT: " ",
+		productGatewayOrEgress: "Magic WAN with Gateway"
+	}}
+/>
+
+## Next steps
+
+Now that you have configured your tunnels and routes, the next step is to create a site. <Render file="sites-brief" product="networking-services" />
@@ -32,6 +32,7 @@ import { GlossaryTooltip, Render } from "~/components";
 
 ## Next steps
 
-- Now that you have set up your tunnel endpoints, you need to configure <GlossaryTooltip term="static route" link="/magic-wan/configuration/manually/how-to/configure-static-routes/">static routes</GlossaryTooltip> to route your traffic through Cloudflare. <br /> If you are connecting to Cloudflare through a [Direct CNI connection](/network-interconnect/express-cni/), you can [configure BGP routing](/magic-wan/configuration/manually/how-to/bgp-peering/) instead.
+- Now that you have set up your tunnel endpoints you need to configure routes to route your traffic through Cloudflare. Refer to [Configure routes](/magic-wan/configuration/manually/how-to/configure-routes/) to learn more about static routing and BGP peering (only available through Direct CNI connection).
 
 - After configuring either static routes or BGP routing, you will have to [set up a site](/magic-wan/configuration/common-settings/sites/).
+
@@ -72,5 +72,5 @@ This tutorial provides information on how to connect Alibaba Cloud infrastructur
 
 ### 2. Static route
 
-1. Follow the [Configure static routes](/magic-wan/configuration/manually/how-to/configure-static-routes/#create-a-static-route) instructions to create a static route.
+1. Follow the [Configure static routes](/magic-wan/configuration/manually/how-to/configure-routes/#create-a-static-route) instructions to create a static route.
 2. In **Prefix**, enter the IP CIDR you used to create your virtual private cloud in the Alibaba Cloud interface. In our example we used `192.168.20.0/24`.
@@ -88,7 +88,7 @@ The static route in Magic WAN should point to the appropriate virtual machine (V
 
 To create a static route:
 
-1. Refer to [Create a static route](/magic-wan/configuration/manually/how-to/configure-static-routes/#create-a-static-route) to learn how to create one.
+1. Refer to [Create a static route](/magic-wan/configuration/manually/how-to/configure-routes/#create-a-static-route) to learn how to create one.
 2. In **Prefix**, enter the subnet for your VM. For example, `192.xx.xx.xx/24`.
 3. For the **Tunnel/Next hop**, choose the IPsec tunnel you created in the previous step.
 4. Repeat the steps above for the second IPsec tunnel you created.
@@ -68,7 +68,7 @@ The time it takes for Azure to fully provision the Virtual Network Gateway depen
 3. If you are using the Active/Active configuration, select **Add IPsec tunnel** and repeat step 2 to create the second Magic WAN IPsec tunnel. Use the same **Cloudflare endpoint** as for the first tunnel.
 4. Select **Add Tunnels** when you are finished.
 5.The Cloudflare dashboard will show you a list of your tunnels. Edit the tunnel(s) you have created > select **Generate a new pre-shared key** > copy the generated key. If using the Active/Active configuration, select **Change to a new custom pre-shared key** on the second tunnel and use the PSK generated for the first tunnel.
-6. Create [static routes](/magic-wan/configuration/manually/how-to/configure-static-routes/) for your Azure Virtual Network subnets, specifying the newly created tunnel as the next hop.
+6. Create [static routes](/magic-wan/configuration/manually/how-to/configure-routes/#create-a-static-route) for your Azure Virtual Network subnets, specifying the newly created tunnel as the next hop.
 
 :::note
 Both tunnels in an Active/Active configuration must use the same **Cloudflare endpoint**, because an Active/Active Azure VPN connection creates two tunnels to the same remote address.

@@ -176,7 +176,7 @@ To configure routes for east-west (branch to branch) connections, refer to the f
 1. Go to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Magic WAN** > **Configuration**.
 3. From the **Static Routes** tab, select **Create**.
-4. For the first route, ensure the following settings are defined (refer to [Configure static routes](/magic-wan/configuration/manually/how-to/configure-static-routes/) to learn about settings not mentioned here):
+4. For the first route, ensure the following settings are defined (refer to [Configure static routes](/magic-wan/configuration/manually/how-to/configure-routes/#create-a-static-route) to learn about settings not mentioned here):
 
 - **Prefix**: `192.168.0.0/24`
 - **Tunnel/Next hop**: _FITEL-tunnel-1 / 10.0.0.0_

@@ -47,7 +47,7 @@ By default, the Magic static routes are defined with the priority set to `100`.
 
 3. From the **Static Routes** tab, select **Create**.
 
-4. For the first route, ensure the following settings are defined (refer to [Configure static routes](/magic-wan/configuration/manually/how-to/configure-static-routes/) to learn about settings not mentioned here):
+4. For the first route, ensure the following settings are defined (refer to [Configure static routes](/magic-wan/configuration/manually/how-to/configure-routes/#create-a-static-route) to learn about settings not mentioned here):
 
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first Magic IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).