refined solution

marciocloudflare · marciocloudflare · commit e80231a7c906 · 2025-10-31T09:47:37.000Z
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/index.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/index.mdx
@@ -14,7 +14,8 @@ import { Render } from "~/components";
 	magicWord: "hardware",
 	productName: "Magic WAN Connector",
 	maintenanceURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/",
-	productOriginalName: "Magic WAN",
+	productOriginalName: "WAN Tunnels",
+	mwanName: "Magic WAN",
 	sfpURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/sfp-port-information/",
 	wan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",
 	lan: "refers to the physical Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-virtual-connector.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-virtual-connector.mdx
@@ -15,7 +15,8 @@ import { Render } from "~/components";
 	productName: "Magic WAN Connector",
 	productNameVirtual: "Virtual Connector",
 	maintenanceURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/",
-	productOriginalName: "Magic WAN",
+	productOriginalName: "WAN Tunnels",
+	mwanName: "Magic WAN",
 	wan: "needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
 	lan: "needs to correspond to the virtual LAN interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
 	noConnectorShows: "For a Virtual Connector to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Connector Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/add-remove-connectors.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/add-remove-connectors.mdx
@@ -13,5 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 		}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/deactivate-connector.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/deactivate-connector.mdx
@@ -14,5 +14,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-basic-info.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-basic-info.mdx
@@ -13,5 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-network-settings.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-network-settings.mdx
@@ -13,5 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-sites.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-sites.mdx
@@ -12,5 +12,6 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-traffic-steering-settings.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/edit-traffic-steering-settings.mdx
@@ -13,5 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/heartbeat.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/heartbeat.mdx
@@ -14,5 +14,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/interrupt-service-window.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/interrupt-service-window.mdx
@@ -16,5 +16,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 />
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/dhcp/dhcp-relay.mdx
@@ -11,6 +11,7 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels",
 		cfTunnelURL: "/cloudflare-one/networks/connectors/cloudflare-tunnel/",
 		cfVsCoreDashNamingMwanCni: "WAN Tunnels tunnel or a CNI connection"
 	}}
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/dhcp/dhcp-server.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/dhcp/dhcp-server.mdx
@@ -10,6 +10,7 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 	}}
 
 	/>
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/network-segmentation.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/network-options/network-segmentation.mdx
@@ -11,6 +11,7 @@ import { Render } from "~/components"
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 		hardConnectorURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/",
 		virtualConnectorURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-virtual-connector/",
 		configHardProductName: "Configure hardware Connector",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/reference.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/reference.mdx
@@ -12,7 +12,7 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic WAN Connector",
-		productOriginalName: "Magic WAN",
+		productOriginalName: "WAN Tunnels",
 		virtualProductName: "Virtual Connector",
 		gatewayURL: "/cloudflare-one/policies/gateway/",
 		hardConnectorURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/",
diff --git a/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/troubleshooting.mdx b/src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/troubleshooting.mdx
@@ -13,6 +13,7 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		wanName: "Magic WAN",
+		dashName: "WAN Tunnels"
 		activateURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/#activate-connector",
 		firewallURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/#firewall-settings-required",
 		heartbeatURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/heartbeat/"
diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx
@@ -5,6 +5,7 @@ params:
   - productNameVirtual?
   - maintenanceURL
   - productOriginalName
+  - mwanName
   - sfpURL?
   - wan
   - lan
@@ -58,7 +59,7 @@ In this page you will find instructions on how to configure {props.productName}.
 
 { props.magicWord === "hardware" && (
   <>
-		<p>You need to purchase <a href="https://www.cloudflare.com/magic-wan">{props.productOriginalName}</a> before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.</p>
+		<p>You need to purchase <a href="https://www.cloudflare.com/magic-wan">{props.mwanName}</a> before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.</p>
 
 		<p>You also need to purchase {props.productName} before you can start configuring your settings in the Cloudflare dashboard. Contact your account representative to learn more about purchasing options for {props.productName}.</p>
 
@@ -70,7 +71,7 @@ In this page you will find instructions on how to configure {props.productName}.
   <>
 		<Markdown
 		text={`
-		Before you can install ${props.productNameVirtual}, you need an Enterprise account with ${props.productOriginalName}. Additionally, you need to have a VMware or Proxmox host with sufficient compute, memory, and storage to run the virtual machine with ${props.productNameVirtual}. This includes:
+		Before you can install ${props.productNameVirtual}, you need an Enterprise account with ${props.mwanName}. Additionally, you need to have a VMware or Proxmox host with sufficient compute, memory, and storage to run the virtual machine with ${props.productNameVirtual}. This includes:
     - Intel x86 CPU architecture
     - ESXi hypervisor 7.0U1 or higher
     - 4 virtual CPUs per virtual connector (We recommend deployment with a 1:1 virtual CPU to physical core allocation to avoid CPU over contention which will cause packet loss.)
@@ -324,7 +325,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 { props.magicWord === "hardware" && (
   <>
 		<AnchorHeading title="Register your Connector" depth={3} />
-		<p>To set up and use {props.productOriginalName}, you first need to register it with your account.</p>
+		<p>To set up and use {props.mwanName}, you first need to register it with your account.</p>
 		<Render
 			file="mconn/maintenance/register-hardware-appliance"
 			product="networking-services"
diff --git a/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
@@ -2,13 +2,14 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { Markdown } from "~/components";
 
 To add a new {props.productName} you first need to remove the one associated with the on-ramps. You can only have more than one {props.productName} if you initially enabled high availability on your on-ramp.
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -2,11 +2,12 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { DashButton, Markdown } from '~/components';
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -2,13 +2,14 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { DashButton, Markdown } from "~/components";
 
 In **Basic information**, you can change the name and description of your {props.productName}.
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -2,11 +2,12 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { Markdown } from "~/components";
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-sites.mdx
@@ -1,11 +1,12 @@
 ---
 params:
   - wanName
+  - dashName
 ---
 
 import { Markdown } from "~/components";
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -2,13 +2,14 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { Markdown } from "~/components";
 
 You can only add or remove applications to Breakout traffic and Prioritized traffic. To add or remove applications:
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -2,6 +2,7 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { DashButton, Markdown } from '~/components';
@@ -18,7 +19,7 @@ There are three symbols for the heartbeat signal that allow you to quickly check
 
 ### Access {props.productName}'s heartbeat
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx b/src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx
@@ -2,13 +2,14 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { DashButton, Markdown } from '~/components';
 
 The Interrupt window defines when {props.productName} can update its systems. When {props.productName} is updating, this may result in an interruption to existing connections. Set up a time window that minimizes disruption to your sites.
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -2,6 +2,7 @@
 params:
   - productName
   - wanName
+  - dashName
   - cfTunnelURL
   - cfVsCoreDashNamingMwanCni
 ---
@@ -39,7 +40,7 @@ To configure DHCP relay:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-server.mdx
@@ -2,6 +2,7 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
@@ -10,7 +11,7 @@ When you use a static IP address, {props.productName} can also act as a DHCP ser
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -2,6 +2,7 @@
 params:
   - productName
   - wanName
+  - dashName
   - hardConnectorURL
   - virtualConnectorURL
   - configHardProductName
@@ -51,7 +52,7 @@ The following guide assumes you have already created a site and configured your
 
 Follow the steps below to create a new LAN policy to segment your network. Only the fields marked **required** are mandatory.
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
@@ -195,7 +196,7 @@ The new policy will ensure that traffic between the specified LANs flows locally
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
@@ -300,7 +301,7 @@ Example:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx
@@ -2,11 +2,12 @@
 params:
   - productName
   - wanName
+  - dashName
 ---
 
 import { DashButton, Markdown } from "~/components";
 
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
 	<>
 		<Markdown
 	text={`
