{`
@@ -65,7 +61,7 @@ flowchart LR
ResolverPolicies -- Retain and useSource Internal IP --> InternalDNS
CloudflareGatewayDNSResolver --
--> ResolverPolicies
WarpConnector["WARP Connector"] -- DHCP/DNS resolver --> IPSecTunnel["IPsec tunnel"]
- MagicWAN[${props.magicWANName}] -- DHCP/DNS resolver --> IPSecTunnel
+ MagicWAN[$Magic WAN] -- DHCP/DNS resolver --> IPSecTunnel
IPSecTunnel -- Shared IP endpoints --> CloudflareGatewayDNSResolver
ResolverPolicies@{ shape: proc}
WarpConnector@{ shape: in-out}
@@ -75,20 +71,20 @@ flowchart LR
## Outbound Internet traffic
-By default, the following traffic routed through {props.magicWANName} tunnels and destined to public IP addresses is proxied/filtered through Cloudflare Gateway:
+By default, the following traffic routed through Magic WAN tunnels and destined to public IP addresses is proxied/filtered through Cloudflare Gateway:
- TCP, UDP, and ICMP traffic sourced from [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) IPs or WARP devices.
- TCP and UDP traffic sourced from [BYO](/byoip/) or [Leased IPs](/magic-transit/cloudflare-ips/) and destined to a well-known port (`0`-`1023`).
-Traffic destined to public IPs will be routed over the public Internet, unless explicitly specified otherwise. If you want to configure specific public IP ranges to be routed through your {props.magicWANName} tunnels instead of over the public Internet after filtering, contact your account team.
+Traffic destined to public IPs will be routed over the public Internet, unless explicitly specified otherwise. If you want to configure specific public IP ranges to be routed through your Magic WAN tunnels instead of over the public Internet after filtering, contact your account team.
This traffic will egress from Cloudflare according to the egress policies you define in Cloudflare Gateway. By default, it will egress from a shared Cloudflare public IP range.
## Private traffic
-By default, TCP, UDP, and ICMP traffic routed through {props.magicWANName} tunnels and destined to routes behind Cloudflare Tunnel will be proxied/filtered through Cloudflare Gateway.
+By default, TCP, UDP, and ICMP traffic routed through Magic WAN tunnels and destined to routes behind Cloudflare Tunnel will be proxied/filtered through Cloudflare Gateway.
-Contact your account team to enable Gateway filtering for traffic destined to routes behind {props.magicWANName} tunnels.
+Contact your account team to enable Gateway filtering for traffic destined to routes behind Magic WAN tunnels.
If enabled, by default TCP/UDP traffic meeting **all** the following criteria will be proxied/filtered by Cloudflare Gateway:
@@ -108,20 +104,18 @@ Source ports are hard-coded to `1024`-`65535` and may not be overridden.
file="traceroute"
product="networking-services"
params={{
- productName: props.magicWANName,
greIpsecURL: props.greIpsecURL,
warpURL: props.warpURL,
- cloudflareTunnelURL: props.cloudflareTunnelURL,
tracerouteURL: props.tracerouteURL
}}
/>
## Test Gateway integration
-To check if Gateway is working properly with your {props.magicWANName} connection, open a browser from a host behind your customer premise equipment, and browse to `https://ifconfig.me`.
+To check if Gateway is working properly with your Magic WAN connection, open a browser from a host behind your customer premise equipment, and browse to `https://ifconfig.me`.
If you are still in the process of testing Gateway, and Cloudflare is not your default route, configure a policy-based route on your router to send traffic to Cloudflare Gateway first, before browsing to `https://ifconfig.me`.
-Confirm there is an entry for the test in HTTP Gateway Activity Logs. The destination IP address should be the public IP address of `ifconfig.me`, and the source IP address should be the private (WAN) address of the host with the browser. Your outbound connection should be sourced from a {props.magicWANName} IP address, and not any public IP address that Cloudflare might be advertising on your behalf. This is true as well when using [Magic Transit With Egress Option](/reference-architecture/architectures/magic-transit/#magic-transit-with-egress-option-enabled).
+Confirm there is an entry for the test in HTTP Gateway Activity Logs. The destination IP address should be the public IP address of `ifconfig.me`, and the source IP address should be the private (WAN) address of the host with the browser. Your outbound connection should be sourced from a Magic WAN IP address, and not any public IP address that Cloudflare might be advertising on your behalf. This is true as well when using [Magic Transit With Egress Option](/reference-architecture/architectures/magic-transit/#magic-transit-with-egress-option-enabled).
Additionally, test both `http://ifconfig.me` (non-TLS) and `https://ifconfig.me` (TLS) to ensure that your TCP maximum segment size (MSS Clamping) has been set properly. If the response to the HTTPS query hangs or fails, but HTTP works, it is possible that the MSS value is too high or not set. Reduce this value on your customer premise equipment to match the overhead introduced by your IKE and [ESP](https://en.wikipedia.org/wiki/IPsec#Encapsulating_Security_Payload) settings.
diff --git a/src/content/partials/networking-services/magic-wan/zero-trust/overview.mdx b/src/content/partials/networking-services/magic-wan/zero-trust/overview.mdx
index dcbc78cca11e6f..9029331c30f981 100644
--- a/src/content/partials/networking-services/magic-wan/zero-trust/overview.mdx
+++ b/src/content/partials/networking-services/magic-wan/zero-trust/overview.mdx
@@ -1,12 +1,11 @@
---
-params:
- - productName
+ {}
---
import { DirectoryListing } from "~/components"
-Review the tutorials to learn more about how you can use {props.productName} with the following Cloudflare Zero Trust products.
+Review the tutorials to learn more about how you can use Magic WAN with the following Cloudflare One products.
on-ramp to {props.productName} and route traffic from user devices with WARP installed to any network connected with Cloudflare Tunnel or Magic IP-layer tunnels (anycast GRE, IPsec, or [CNI](/network-interconnect/)). Take advantage of the integration between {props.productName} and {props.magicFirewallName} and enforce policies at Cloudflare's global network.
+Use WARP as an on-ramp to Magic WAN and route traffic from user devices with WARP installed to any network connected with Cloudflare Tunnel or Magic IP-layer tunnels (anycast GRE, IPsec, or [CNI](/network-interconnect/)). Take advantage of the integration between Magic WAN and Magic Firewall and enforce policies at Cloudflare's global network.
## Prerequisites
-Before you can begin using WARP as an on-ramp to {props.productName}, you must set up your Zero Trust account.
+Before you can begin using WARP as an on-ramp to Magic WAN, you must set up your Zero Trust account.
## IP ranges
-When connecting a WARP device to {props.productName}, you will have virtual IP addresses from WARP, in the `100.96.0.0/12` range.
+When connecting a WARP device to Magic WAN, you will have virtual IP addresses from WARP, in the `100.96.0.0/12` range.
---
-## Set up WARP with {props.productName}
+## Set up WARP with Magic WAN
### 1. Route packets back to WARP devices
@@ -75,19 +71,17 @@ You must log out and log back in with at least one WARP device to ensure the con
file="traceroute"
product="networking-services"
params={{
- productName: props.productName,
greIpsecURL: props.greIpsecURL,
warpURL: props.warpURL,
- cloudflareTunnelURL: props.cloudflareTunnelURL,
tracerouteURL: props.tracerouteURL
}}
/>
## Double encapsulation
-When a WARP user goes to a location (like an office) with a {props.productName} tunnel already set up, WARP traffic is doubly encapsulated - first by WARP and then by {props.productName}. This is unnecessary, since each on-ramp method provides full Zero Trust protection.
+When a WARP user goes to a location (like an office) with a Magic WAN tunnel already set up, WARP traffic is doubly encapsulated - first by WARP and then by Magic WAN. This is unnecessary, since each on-ramp method provides full Zero Trust protection.
-Since WARP traffic is already protected on its own, Cloudflare recommends that you set up {props.productName} to exclude WARP traffic, sending it to the Internet through regular connections.
+Since WARP traffic is already protected on its own, Cloudflare recommends that you set up Magic WAN to exclude WARP traffic, sending it to the Internet through regular connections.
To learn which IP addresses and UDP ports you should exclude to accomplish this, refer to WARP ingress IP.
@@ -107,7 +101,7 @@ Before testing, be sure to configure domain fa
If WARP integration has been enabled for the account within the last day, log off and on again in the WARP client before testing.
-To check if WARP is working correctly as an on-ramp, you can do a resolution test on a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) for a server or service in the {props.productName}. Test this from a user with a WARP device.
+To check if WARP is working correctly as an on-ramp, you can do a resolution test on a [fully qualified domain name (FQDN)](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) for a server or service in the Magic WAN. Test this from a user with a WARP device.
For example:
diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx
index 0fe0c27b9a6ed1..ec2721ee617de9 100644
--- 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
- dashName
+ - deviceTypeName
- sfpURL?
- wan
- lan
@@ -16,7 +17,6 @@ params:
- shippedLanguage
- hardSoftConn
- hcConfigsURL
- - finalInstructions
- ipsecTunnelsRefURL
- trafficSteeringURL
- vlanIdURL
@@ -44,6 +44,7 @@ import {
DashButton,
} from "~/components";
+{/* Virtual Connector */}
{ props.magicWord === "virtual" && (
<>
{props.productNameVirtual} is a virtual device alternative to the hardware based {props.productName}. These two versions of {props.productName} are identical otherwise.
Currently, you can set up {props.productNameVirtual} on VMWare ESXi and Proxmox Virtual Environment. Support for Proxmox is in beta.
@@ -65,6 +66,7 @@ In this page you will find instructions on how to configure {props.productName}.
)
}
+{/* Virtual Connector */}
{ props.magicWord === "virtual" && (
<>
{props.productNameVirtual} uses a DHCP connection at first boot to download your settings and go through the activation process. However, if you need to use a static IP in your {props.productNameVirtual}, and this is a fresh install:
@@ -177,6 +180,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
)
}
+{/* Virtual Connector */}
{ props.magicWord === "virtual" && (
<>
To set up and use Magic WAN, you first need to register it with your account.
- Log in to Cloudflare One, and go to Networks.
- Go to Connectors > Appliances.
- - Select Create a new profile.
+ - Select Create a profile.
)
@@ -367,8 +369,8 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
4. In **Name**, enter a descriptive name for your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. Optionally, you can also add a description for it.
5. You need to decide if you want to turn on high availability for the { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }. Refer to [About high availability configurations](#about-high-availability-configurations) for more information.
6. Select **Create and continue**.
-7. Select **Add { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }**. This will show you a list of devices associated with your account.
Select **Select { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }** when you are ready to proceed.
+7. Select **Add {props.deviceTypeName}**. This will show you a list of devices associated with your account.
Select **Add Connector** when you are ready to proceed.
9. { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } will be added to your account with an **Interrupt window** defined. The interrupt window is the time period when the { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } software can update, which may result in interruption to existing connections. You can change this later. Refer to Interrupt window for more details on how to define when the { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } can update its systems.
10. Select **Continue** to proceed to creating your WAN and LAN networks.
@@ -829,10 +831,10 @@ inline={false}
/>
2. After naming your site, select **Turn on high availability**.
3. Select **Create and continue**.
-4. Select **Add { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }**.
-5. From the list, choose your first { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } > **Add { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }**.
-6. Back on the previous screen, select **Add secondary { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }**.
-7. From the list, choose your second { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } > **Add { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }**.
+4. Select **Add {props.deviceTypeName}**.
+5. From the list, choose your first { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } > **Add {props.deviceTypeName}**.
+6. Back on the previous screen, select **Add secondary {props.deviceTypeName}**.
+7. From the list, choose your second { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } > **Add {props.deviceTypeName}**.
8. Select **Continue** to create a WAN. If you are configuring a static IP, configure the IP for the primary node as the static address, and the IP for the secondary node as the secondary static address.
9. To create a LAN, follow the steps mentioned above in [Create a LAN](#create-a-lan) up until step 4.
10. In **Static address**, enter the IP for the primary node in your site. For example, `192.168.10.1/24`.
@@ -840,7 +842,7 @@ inline={false}
12. In **Virtual static address**, enter the IP that the LAN south of the { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } device will forward traffic to. For example, `192.168.10.3/24`.
13. Select **Save**.
14. From the **High availability probing link** drop-down menu, select the port that should be used to monitor the node's health. Cloudflare recommends you choose a reliable interface as the HA probing link. The primary and secondary node's probing link should be connected over a switch, and cannot be a direct connection.
-15. ).
+The metric `average CPU load` is unique and distinctly different from `CPU utilization` which is another common CPU metric. The Magic WAN Connector uses a [Unix-style CPU load calculation]().
-CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the {props.productName} CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
+CPU load is a measure of the number of processes that are currently running and that are waiting to be run on the CPU. Cloudflare collects the one minute load average from the device and converts that into a percentage based on the total number of cores in the CPU. If the Magic WAN Connector CPU has eight cores, and a one minute load average of two, then the average CPU load is 25%. If the average CPU load is above 100%, then there are processes in the queue that are waiting to be executed on the CPU.
-Cloudflare is still evaluating the typical CPU load operating range on the {props.productName}. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased {props.productName} performance if the average CPU load is consistently above 100%.
\ No newline at end of file
+Cloudflare is still evaluating the typical CPU load operating range on the Magic WAN Connector. In general, a healthy range for average CPU load on any device is between 30% and 70%. Customers may experience decreased Magic WAN Connector performance if the average CPU load is consistently above 100%.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
index cfe5a7cd047ddb..8e079af31538da 100644
--- a/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/activate-connectors.mdx
@@ -1,11 +1,10 @@
---
params:
- - productName
- hardwareConnectorURL
- virtualConnectorURL
---
-Before you can activate your {props.productName}, you need to follow Cloudflare's instructions regarding DHCP. For full instructions on this, refer to:
+Before you can activate your Magic WAN Connector, you need to follow Cloudflare's instructions regarding DHCP. For full instructions on this, refer to:
-- The hardware version of {props.productName}
-- The virtual version of {props.productName}
\ No newline at end of file
+- The hardware version of Magic WAN Connector
+- The virtual version of Magic WAN Connector
\ No newline at end of file
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
index a0eb0952dec2f1..3456a26cf5d69a 100644
--- a/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
@@ -1,19 +1,18 @@
---
params:
- - productName
- 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.
+To add a new Magic WAN Connector you first need to remove the one associated with the on-ramps. You can only have more than one Magic WAN Connector if you initially enabled high availability on your on-ramp.
{ props.dashName === "WAN Tunnels" ? (
<>
Cloudflare One , and go to **Networks**.
- 2. Go to **Connectors** > **Appliances**.
+ 2. Go to **Connectors** > **Appliances** > **Profiles**.
`}
inline={false}
/>
@@ -30,7 +29,7 @@ To add a new {props.productName} you first need to remove the one associated wit
)
}
-3. Find the {props.productName} that you want to edit > select the three dots next to it > **Edit**.
-4. In **{props.productName}**, remove the {props.productName} associated with the on-ramp.
-5. Select **Add {props.productName}** to add a different {props.productName} to your on-ramp.
+3. Find the Magic WAN Connector that you want to edit > select the three dots next to it > **Edit**.
+4. In **{props.dashName === "WAN Tunnels" ? "Appliances" : "Connectors"}**, remove the Magic WAN Connector associated with the on-ramp.
+5. Select **{props.dashName === "WAN Tunnels" ? "Add appliance" : "Add Connector"}** to add a different Magic WAN Connector to your on-ramp.
6. Select **Save**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
index 02223ea28e6ca7..15e843e739451f 100644
--- a/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/deactivate-connector.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
---
@@ -11,8 +10,8 @@ import { DashButton, Markdown } from '~/components';
Cloudflare One, and go to **Networks**.
- 2. Go to **Connectors** > **Appliances** > **Profiles**.
- 3. Find the ${props.productName} you want to deactivate, select the three dots next to it > **Edit**.
+ 2. Go to **Connectors** > **Appliances** > **Appliances**.
+ 3. Find the Magic WAN Connector you want to deactivate, select the three dots next to it > **Edit**.
`}
inline={false}
/>
@@ -28,7 +27,7 @@ import { DashButton, Markdown } from '~/components';
**Edit**.
+ 3. In the **Magic WAN Connector** tab, find the Magic WAN Connector you want to deactivate, select the three dots next to it > **Edit**.
`}
inline={false}
/>
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index 1abf75b6fc17e1..e84624142e3f43 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -1,18 +1,15 @@
---
-params:
- - productName
- - hardwareConnectorName
- - virtualConnectorName
+{}
---
-{props.productName} ships to you with a default password that enables you to access the hardware box or the virtual machine. Cloudflare recommends that you change this password after the first boot.
+Magic WAN Connector ships to you with a default password that enables you to access the hardware box or the virtual machine. Cloudflare recommends that you change this password after the first boot.
-## Default password to access hardware {props.hardwareConnectorName}
+## Default password to access hardware Magic WAN Connector
-The default password for {props.productName} is the serial number (also known as a Service Tag for Dell devices), all uppercase followed by an `!` (exclamation mark). For example, `A1B2C3D!`
+The default password for Magic WAN Connector is the serial number (also known as a Service Tag for Dell devices), all uppercase followed by an `!` (exclamation mark). For example, `A1B2C3D!`
-## Default password to access {props.virtualConnectorName}
+## Default password to access Virtual Connector
-The default password for {props.virtualConnectorName} is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
+The default password for Virtual Connector is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
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
index a9a70dabf74534..e00cb3aaba8a83 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-basic-info.mdx
@@ -1,19 +1,18 @@
---
params:
- - productName
- dashName
---
import { DashButton, Markdown } from "~/components";
-In **Basic information**, you can change the name and description of your {props.productName}.
+In **Basic information**, you can change the name and description of your Magic WAN Connector.
{ props.dashName === "WAN Tunnels" ? (
<>
Cloudflare One, and go to **Networks**.
- 2. Go to **Connectors** > **Appliances**.
+ 2. Go to **Connectors** > **Appliances** > **Appliances**.
`}
inline={false}
/>
@@ -30,6 +29,6 @@ In **Basic information**, you can change the name and description of your {props
)
}
-3. Find the {props.productName} that you want to edit > select the three dots next to it > **Edit**.
+3. Find the Magic WAN Connector that you want to edit > select the three dots next to it > **Edit**.
4. In **Basic information** make the necessary changes.
5. Select **Save**.
\ No newline at end of file
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
index f868a98b1ab588..fbf0b20046567c 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-network-settings.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
---
@@ -11,7 +10,7 @@ import { Markdown } from "~/components";
Cloudflare One, and go to **Networks**.
- 2. Go to **Connectors** > **Appliances**.
+ 2. Go to **Connectors** > **Appliances** > **Profiles**.
`}
inline={false}
/>
@@ -28,7 +27,7 @@ import { Markdown } from "~/components";
)
}
-3. Find the on-ramp that you want to edit > select the three dots next to it > **Edit**.
+3. Find the Connector that you want to edit > select the three dots next to it > **Edit**.
4. Go to **Network configuration** > **WAN configuration** or **LAN configuration**.
5. Find the WAN/LAN you want to edit > select the three dots next to it > **Edit**.
6. Make the necessary changes.
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
index 26c1f2b540d63f..ad4ac18b0a9345 100644
--- a/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/edit-traffic-steering.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
---
@@ -13,7 +12,7 @@ You can only add or remove applications to Breakout traffic and Prioritized traf
Cloudflare One, and go to **Networks**.
- 2. Go to **Connectors** > **Appliances**.
+ 2. Go to **Connectors** > **Appliances** > **Profiles**.
`}
inline={false}
/>
@@ -30,7 +29,7 @@ You can only add or remove applications to Breakout traffic and Prioritized traf
)
}
-3. Find the on-ramp that you want to edit > select the three dots next to it > **Edit**.
+3. Find the Connector that you want to edit > select the three dots next to it > **Edit**.
4. Go to **Traffic steering** > **Breakout traffic** or **Prioritized traffic**.
5. Select **Add** to add a new application.
6. To delete an application, find the one you want to delete from **Breakout traffic** or **Prioritized traffic** > select the three dots next to it > **Remove**.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
index c93fd178e95970..8dcaaa1e6d7df8 100644
--- a/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx
@@ -1,30 +1,29 @@
---
params:
- - productName
- dashName
---
import { DashButton, Markdown } from '~/components';
-{props.productName} communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the {props.productName} in question is connected to the Internet and reachable.
+Magic WAN Connector communicates periodically with Cloudflare via HTTPS. This is also known as a heartbeat, and lets Cloudflare know that the Magic WAN Connector in question is connected to the Internet and reachable.
-The heartbeat calls are made to `api.cloudflare.com`. Each {props.productName} has a heartbeat frequency of 10 seconds, independently of the number of WAN interfaces you have running on your device.
+The heartbeat calls are made to `api.cloudflare.com`. Each Magic WAN Connector has a heartbeat frequency of 10 seconds, independently of the number of WAN interfaces you have running on your device.
-There are three symbols for the heartbeat signal that allow you to quickly check the status of {props.productName}:
+There are three symbols for the heartbeat signal that allow you to quickly check the status of Magic WAN Connector:
-- **Blue `i`**: {props.productName} is contacting Cloudflare as expected.
-- **Yellow triangle**: {props.productName} has not yet connected to Cloudflare.
-- **Red triangle**: There is a potential problem with {props.productName}.
+- **Blue `i`**: Magic WAN Connector is contacting Cloudflare as expected.
+- **Yellow triangle**: Magic WAN Connector has not yet connected to Cloudflare.
+- **Red triangle**: There is a potential problem with Magic WAN Connector.
-### Access {props.productName}'s heartbeat
+### Access Magic WAN Connector's heartbeat
{ props.dashName === "WAN Tunnels" ? (
<>
Cloudflare One, and go to **Networks**.
- 2. Go to **Connectors** > **Appliances** > **Profiles**.
- 3. Find your ${props.productName}, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp shows you the last time ${props.productName} successfully contacted Cloudflare.
+ 2. Go to **Connectors** > **Appliances** > **Appliances**.
+ 3. Find your Magic WAN Connector, and place your cursor over the icon on the **Status** column to check the timestamp. The timestamp shows you the last time Magic WAN Connector successfully contacted Cloudflare.
`}
inline={false}
/>
@@ -40,7 +39,7 @@ There are three symbols for the heartbeat signal that allow you to quickly check
Cloudflare One, and go to **Networks** > **Connectors**.
- 2. In **Appliances** > **Profiles**, select the ${props.productName} for which you want to set up the update window > **Edit**.
+ 2. In **Appliances** > **Appliances**, select the Magic WAN Connector for which you want to set up the update window > **Edit**.
`}
inline={false}
/>
@@ -29,14 +28,14 @@ The Interrupt window defines when {props.productName} can update its systems. Wh
**Edit**.
+ 2. In the **Magic WAN Connector** tab, select the Magic WAN Connector for which you want to set up the update window > **Edit**.
`}
inline={false}
/>
)
}
-3. In **Interrupt window**, select the most appropriate time for the {props.productName} to update its systems:
- - **Timezone**: Select the time zone for the {props.productName} to update.
- - **Start time**: Choose an hour for the {props.productName} to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
- - **Duration**: Duration indicates the time window during which the {props.productName} is scheduled to update. For example, if you configure your {props.productName} to update at `22:00` and specify a **Duration** of `4 hours`, the {props.productName} will attempt to update within the four-hour period following `22:00`.
+3. In **Interrupt window**, select the most appropriate time for the Magic WAN Connector to update its systems:
+ - **Timezone**: Select the time zone for the Magic WAN Connector to update.
+ - **Start time**: Choose an hour for the Magic WAN Connector to start updating. Cloudflare recommends you choose an hour when there is minimal activity in your network, to avoid potential disruptions.
+ - **Duration**: Duration indicates the time window during which the Magic WAN Connector is scheduled to update. For example, if you configure your Magic WAN Connector to update at `22:00` and specify a **Duration** of `4 hours`, the Magic WAN Connector will attempt to update within the four-hour period following `22:00`.
diff --git a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
index e536e1ff252e6e..a9ffd86eabb0ed 100644
--- a/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/register-hardware-appliance.mdx
@@ -1,12 +1,11 @@
---
params:
- dashName
- - productName
---
import { DashButton } from "~/components";
-To set up and use the hardware version of {props.productName}, you first need to register it with your account. This is not applicable to Virtual {props.productName}.
+To set up and use the hardware version of Magic WAN Connector, you first need to register it with your account. This is not applicable to Virtual Magic WAN Connector.
{/* Dashboard steps for WAN Tunnels (Cloudflare One dashboard) */}
{ props.dashName === "WAN Tunnels" && (
@@ -31,8 +30,8 @@ To set up and use the hardware version of {props.productName}, you first need to
)
}
-3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the {props.productName} you are adding to the dashboard.
-4. (Optional) Select **Add** below **Serial number** to add multiple {props.productName}s at once to your account.
+3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Magic WAN Connector you are adding to the dashboard.
+4. (Optional) Select **Add** below **Serial number** to add multiple Magic WAN Connectors at once to your account.
5. Select **Register appliance**.
Your device is now registered with your account.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 33b75082635d54..dd8bed1c85a849 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -1,13 +1,9 @@
---
params:
- - productName
- dashName
- - virtualProductName
- gatewayURL
- hardConnectorURL
- virtualConnectorURL
- - configHardProductName
- - configVirtualProductName
- haSetupURL
- ecmpRoutingURL
- multipleWansURL
@@ -22,41 +18,41 @@ params:
import { GlossaryTooltip, Render } from "~/components"
-The {props.productName} software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
+The Magic WAN Connector software is certified for use on the [Dell Networking Virtual Edge Platform](https://www.dell.com/support/home/en-us/product-support/product/dell-emc-networking-vep1445-vep1485/docs). It can be purchased with software pre-installed through our partner network for plug-and-play connectivity to Cloudflare One.
## Security and other information
-- Cloudflare ensures the {props.productName} device is secure and is not altered via TPM/Secure boot (does not apply to {props.virtualProductName}).
-- Connectivity to the Cloudflare global network is secure and all traffic is encrypted through IPsec tunneling. The {props.productName} uses ESP-in-UDP with GCM-AES-256 encryption. Cloudflare uses a non-IKE keying protocol built into our control plane, secured with TLS.
-- The {props.productName} does not support fail open.
+- Cloudflare ensures the Magic WAN Connector device is secure and is not altered via TPM/Secure boot (does not apply to Virtual Connector).
+- Connectivity to the Cloudflare global network is secure and all traffic is encrypted through IPsec tunneling. The Magic WAN Connector uses ESP-in-UDP with GCM-AES-256 encryption. Cloudflare uses a non-IKE keying protocol built into our control plane, secured with TLS.
+- The Magic WAN Connector does not support fail open.
- Customers have the ability to layer on additional security features/policies that are enforced at the Cloudflare network.
---
## ICMP traffic
-ICMP traffic is routed through the Internet and bypasses Cloudflare Gateway. This enables you to ping resources on the Internet from the {props.productName} directly, which can be useful for debugging.
+ICMP traffic is routed through the Internet and bypasses Cloudflare Gateway. This enables you to ping resources on the Internet from the Magic WAN Connector directly, which can be useful for debugging.
---
## VLAN ID
-This feature allows you to have multiple [virtual LANs](https://www.cloudflare.com/learning/network-layer/what-is-a-lan/) (VLANs) configured over the same physical port on your {props.productName}. VLAN tagging adds an extra header to [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/) in order to identify which VLAN the packet belongs to and to route it appropriately. This effectively allows you to run multiple networks over the same physical port.
+This feature allows you to have multiple [virtual LANs](https://www.cloudflare.com/learning/network-layer/what-is-a-lan/) (VLANs) configured over the same physical port on your Magic WAN Connector. VLAN tagging adds an extra header to [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/) in order to identify which VLAN the packet belongs to and to route it appropriately. This effectively allows you to run multiple networks over the same physical port.
-A non-zero value set up for the VLAN ID field in your WAN/LAN is used to handle VLAN-tagged traffic. Cloudflare uses the VLAN ID to handle traffic coming into your {props.productName} device, and applies a VLAN tag with the configured VLAN ID for traffic going out of your {props.productName} through WAN/LAN.
+A non-zero value set up for the VLAN ID field in your WAN/LAN is used to handle VLAN-tagged traffic. Cloudflare uses the VLAN ID to handle traffic coming into your Magic WAN Connector device, and applies a VLAN tag with the configured VLAN ID for traffic going out of your Magic WAN Connector through WAN/LAN.
-You can setup VLAN IDs both for WAN and LAN. Refer to {props.configHardProductName} or {props.configVirtualProductName} to learn where you can set up VLAN IDs.
+You can setup VLAN IDs both for WAN and LAN. Refer to Configure hardware Connector or Configure Virtual Connector to learn where you can set up VLAN IDs.
## High availability configurations
### Terminology
-- **Primary/Secondary**: Used to identify the two nodes which are part of a high availability (HA) configuration pair of {props.productName}s. This identity allows the node to identify which configuration is attributed to it — for example, specifying a primary and secondary IP in a LAN configuration. This identity is configured by the user on the Cloudflare dashboard.
+- **Primary/Secondary**: Used to identify the two nodes which are part of a high availability (HA) configuration pair of Magic WAN Connectors. This identity allows the node to identify which configuration is attributed to it — for example, specifying a primary and secondary IP in a LAN configuration. This identity is configured by the user on the Cloudflare dashboard.
- **Active/Standby**: These are states that the two nodes in a HA pair will dynamically assume based on an election process. Only one node at any time is expected to be active.
### High availability
-A site set up in high availability (HA) mode has two {props.productName}s with the same configuration but replicated in two nodes. In case of failure of one {props.productName}, the other {props.productName} becomes the active node, taking over configuration of the LAN gateway IP and allowing traffic to continue without disruption.
+A site set up in high availability (HA) mode has two Magic WAN Connectors with the same configuration but replicated in two nodes. In case of failure of one Magic WAN Connector, the other Magic WAN Connector becomes the active node, taking over configuration of the LAN gateway IP and allowing traffic to continue without disruption.
### Active/Standby Election
@@ -68,7 +64,7 @@ The HA pair is configured in non-preemptive mode, meaning that once a node becom
### Configuration
-The two {props.productName}s of a high availability (HA) pair are part of a single site. You designate the {props.productName} as primary and secondary in the Cloudflare dashboard.
+The two Magic WAN Connectors of a high availability (HA) pair are part of a single site. You designate the Magic WAN Connector as primary and secondary in the Cloudflare dashboard.
:::note
The HA link cannot be connected back-to-back. It has to be connected over a switch. This is because, in a direct connection, if the link is unplugged on one end, the other end also detects a link failure. Since we have configured the system to enter a `FAULT` state when the HA link goes down, the affected node will be unable to function as the active node.
@@ -76,7 +72,7 @@ The HA link cannot be connected back-to-back. It has to be connected over a swit
### Failure detection and failover
-The {props.productName}'s health can be in one of three states:
+The Magic WAN Connector's health can be in one of three states:
- **Good** : All health parameters are good
- **Degraded** : One of the following is true:
@@ -85,9 +81,9 @@ The {props.productName}'s health can be in one of three states:
- **Down** : If one of the following is true:
- Health of all tunnels is `DOWN`
- All LAN interfaces are disconnected
- - {props.productName}'s software is not healthy
+ - Magic WAN Connector's software is not healthy
-A failover happens when the active node's health declines to a level lower than that of the standby node. For example, from `GOOD` to `DEGRADED`, or from `DEGRADED` to `DOWN`. In the case of a failover where one {props.productName} is acting as a DHCP server, DHCP leases will be synchronized.
+A failover happens when the active node's health declines to a level lower than that of the standby node. For example, from `GOOD` to `DEGRADED`, or from `DEGRADED` to `DOWN`. In the case of a failover where one Magic WAN Connector is acting as a DHCP server, DHCP leases will be synchronized.
When a failover occurs, traffic is moved to the new active node. It could take up to 30 seconds for traffic to be fully restored over the new active node.
@@ -95,12 +91,12 @@ When a failover occurs, traffic is moved to the new active node. It could take u
This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
-
If you are using {props.virtualProductName}, this needs to correspond to the virtual network interface on the {props.virtualProductName} instance you have set up in your virtual machine.
-- **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your {props.productName}. Refer to VLAN ID for more information.
+- **Interface number:** When using the hardware version of Magic WAN Connector, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to SFP+ port information for more information on the hardware supported.
If you are using Virtual Connector, this needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in your virtual machine.
+- **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Magic WAN Connector. Refer to VLAN ID for more information.
- **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. Refer to Traffic steering to learn more about how Cloudflare calculates priorities.
- **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. Refer to Update tunnel health checks frequency for more information.
-- **Addressing:** Configures the {props.productName} to work in a DHCP or static IP environment.
+- **Addressing:** Configures the Magic WAN Connector to work in a DHCP or static IP environment.
## LAN settings
-- **Interface number:** When using the hardware version of {props.productName}, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to SFP+ port information for more information on the hardware supported.
If you are using the {props.virtualProductName}, this needs to correspond to the virtual LAN interface on the {props.virtualProductName} instance you have set up in your virtual machine.
-- **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your {props.productName}. Refer to VLAN ID for more information.
+- **Interface number:** When using the hardware version of Magic WAN Connector, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to SFP+ port information for more information on the hardware supported.
If you are using the Virtual Connector, this needs to correspond to the virtual LAN interface on the Virtual Connector instance you have set up in your virtual machine.
+- **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Magic WAN Connector. Refer to VLAN ID for more information.
- **Static addressing:** Configures the type of IP addressing for your Connector. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. Refer to DHCP options to learn more.
- **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
- **Routed subnets:** Configures additional subnets behind a layer 3 router. Refer to Routed subnets for more information.
### Restrict traffic to your premises
-Depending on your use case, you can define policies in your {props.productName} to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
+Depending on your use case, you can define policies in your Magic WAN Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
Refer to Network segmentation for more information.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index 87346f78ac0951..1df28683b3e54a 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -1,7 +1,6 @@
---
params:
- magicWord
- - productName
- featureName
- trafficSteeringURL?
- whatHappensApp
@@ -12,7 +11,7 @@ import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs
{ props.magicWord === "breakout" && (
<>
- Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that {props.productName} can detect. This can take several minutes.
+ Breakout traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that Magic WAN Connector can detect. This can take several minutes.
)
@@ -20,7 +19,7 @@ import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs
{ props.magicWord === "prioritized" && (
<>
- Prioritized traffic allows you to define which applications {props.productName} should process first. Applications not in the list will be queued behind prioritized traffic.
+ Prioritized traffic allows you to define which applications Magic WAN Connector should process first. Applications not in the list will be queued behind prioritized traffic.
Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.
@@ -33,7 +32,7 @@ import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs
{`
flowchart LR
accTitle: In this example, the applications go directly to the Internet, skipping Cloudflare's security. filtering
- a(${props.productName}) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
+ a(Magic WAN Connector) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
a-- Breakout traffic ---d(Application1) & e(Application2) --> c
@@ -58,7 +57,7 @@ import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs
## Add an application to your account
-Before you can add or remove {props.featureName} applications to your {props.productName}, you need to create an account-level list with the applications that you want to configure. Currently, adding to or modifying this list is only possible via API, through the [`managed_app_id`](/api/resources/magic_transit/subresources/apps/methods/create/) endpoint.
+Before you can add or remove {props.featureName} applications to your Magic WAN Connector, you need to create an account-level list with the applications that you want to configure. Currently, adding to or modifying this list is only possible via API, through the [`managed_app_id`](/api/resources/magic_transit/subresources/apps/methods/create/) endpoint.
To add applications to your account:
@@ -87,9 +86,9 @@ Send a `POST` request to add new apps to your account.
}
```
-You can now add this new app to the {props.featureName} list in your {props.productName}.
+You can now add this new app to the {props.featureName} list in your Magic WAN Connector.
-### Add an application to {props.productName}
+### Add an application to Magic WAN Connector
You need to configure {props.featureName} applications for each of your existing sites, as this is a per-site configuration.
@@ -119,9 +118,9 @@ You need to configure {props.featureName} applications for each of your existing
}
**Edit**.
+3. Select the Magic WAN Connector you want to configure > **Edit**.
4. Select **Traffic Steering**.
-5. In **${props.featureName}**, select **Assign application traffic**.
+5. In **${props.featureName}**, select **${props.dashName === "WAN Tunnels" ? "Create" : "Assign application traffic"}**.
6. Select one or more applications that should bypass Cloudflare filtering from the list. You can also use the search box.
`}
inline={false}
@@ -213,7 +212,7 @@ The traffic for the application you chose ${props.whatHappensApp}.
-### Delete an application from {props.productName}
+### Delete an application from Magic WAN Connector
@@ -243,7 +242,7 @@ The traffic for the application you chose ${props.whatHappensApp}.
text={`
3. Select the Connector you want to configure > **Edit**.
4. Select **Traffic Steering**.
-5. In **${props.featureName}**, find the application you want to delete > select the **three dots** next to it > **Remove**.
+5. In **${props.featureName}**, find the application you want to delete > select the **three dots** next to it > **Remove application traffic**.
6. (Optional) If you have several pages of applications, you can use the search box to quickly find the application you are looking for.
`}
inline={false}
@@ -306,7 +305,7 @@ You need to delete {props.featureName} applications for each of your existing si
Cloudflare One dashboard, and go to **Networks**.
2. Go to **Connectors** > **Appliances** > **Profiles**.
- 3. Select the ${props.productName} you want to configure> **Edit**.
+ 3. Select the Magic WAN Connector you want to configure> **Edit**.
`}
inline={false}
/>
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
index c22ec831c3b213..84c7c63c93f4a0 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/overview.mdx
@@ -1,19 +1,18 @@
---
params:
- - productName
- gatewayPoliciesURL
- appTypesGatewayURL
---
import { DirectoryListing } from "~/components"
-In addition to traffic policies based on network-layer attributes like IP and port ranges, {props.productName} supports the ability to classify traffic based on well-known applications. Application-aware policies provide easier management and more granularity over traffic flows.
+In addition to traffic policies based on network-layer attributes like IP and port ranges, Magic WAN Connector supports the ability to classify traffic based on well-known applications. Application-aware policies provide easier management and more granularity over traffic flows.
Cloudflare's implementation of application awareness leverages the intelligence of our global network, using the same categorization/classification already shared across security tools like our Secure Web Gateway, so IT and security teams can expect consistent behavior across routing and inspection decisions.
For more information, refer to Applications and app types.
-{props.productName}'s ability to classify traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. You can also give some applications a higher priority, and Connector will process them first. This is useful when your network is at capacity, for example.
+Magic WAN Connector's ability to classify traffic allows you to define which applications should bypass Cloudflare's security filtering, and go directly to the Internet. You can also give some applications a higher priority, and Connector will process them first. This is useful when your network is at capacity, for example.
Refer to the following pages for more information.
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
index e5d6bfe5a7022f..4c8a966a1f973e 100644
--- 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
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
- cfTunnelURL
- cfVsCoreDashNamingMwanCni
@@ -8,13 +7,13 @@ params:
import { APIRequest, Markdown, Render, TabItem, Tabs } from "~/components";
-DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, {props.productName} forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
+DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that are not available on the same local subnet/broadcast domain. When you enable DHCP Relay, Magic WAN Connector forwards DHCP discover messages to a predefined DHCP server, and routes the responses back to the original device that sent the discover message.
{`
flowchart LR
accTitle: An example of Connector in DHCP Relay mode
- a(${props.productName}) <--> b(Cloudflare/Magic WAN) <--> c(DHCP server)
+ a(Magic WAN Connector) <--> b(Cloudflare/Magic WAN) <--> c(DHCP server)
subgraph Site A
d[LAN 1] <--> a
@@ -29,7 +28,7 @@ DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that
`}
-_The above graph shows {props.productName} sending DHCP discover messages to a DHCP server offsite._
+_The above graph shows Magic WAN Connector sending DHCP discover messages to a DHCP server offsite._
:::caution
DHCP relay will not work if your DHCP server is behind a Cloudflare Tunnel. To enable DHCP relay functionality, use either a {props.cfVsCoreDashNamingMwanCni}.
@@ -63,7 +62,7 @@ To configure DHCP relay:
}
**Edit**.
+3. Select your Magic WAN Connector > **Edit**.
4. Select **Network Configuration**.
5. In **LAN configuration**, select the LAN where you need to configure DHCP relay.
6. Select **Edit**.
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
index b2adabb36b23f5..84695960f4d8a7 100644
--- 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
@@ -1,12 +1,11 @@
---
params:
- - productName
- dashName
---
import { APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
-When you use a static IP address, {props.productName} can also act as a DHCP server in your network. To enable this feature:
+When you use a static IP address, Magic WAN Connector can also act as a DHCP server in your network. To enable this feature:
@@ -34,7 +33,7 @@ When you use a static IP address, {props.productName} can also act as a DHCP ser
}
{/* Command needed so list starts on number 3 since steps 1, 2 are inside conditional render */}
-- Select your {props.productName} you want to configure > Edit.
+- Select your Magic WAN Connector you want to configure > Edit.
- Select Network Configuration, and scroll down to LAN configuration.
- In LAN configuration, select the LAN where you want to enable DHCP server.
- Select Edit.
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-static-address-reservation.mdx
index 70103e220bb38d..83a67d692e8a83 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-static-address-reservation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-static-address-reservation.mdx
@@ -1,16 +1,15 @@
---
params:
- - productName
- dhcpServerURL
---
import { APIRequest, Render, TabItem, Tabs } from "~/components";
-If you configure your {props.productName} to be a DHCP server, you can also assign IP addresses to specific devices on your network. To reserve IP addresses:
+If you configure your Magic WAN Connector to be a DHCP server, you can also assign IP addresses to specific devices on your network. To reserve IP addresses:
-1. Configure your {props.productName} to be a DHCP server.
+1. Configure your Magic WAN Connector to be a DHCP server.
2. Select **Add DHCP Reservation**.
3. In **Hardware Address** enter the [MAC address](https://en.wikipedia.org/wiki/MAC_address) for the device you want a specific IP address for.
4. In **IP Address**, enter the IP address for that device.
diff --git a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
index 251ececaf68585..4e0a05808e9588 100644
--- a/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/nat-subnet.mdx
@@ -1,28 +1,24 @@
---
params:
- - productName
- - connectorName
- hardConnectorURL
- virtualConnectorURL
- - configHardProductName
- - configVirtualProductName
---
-Each subnet (directly-attached or routed) must have a unique address space within your {props.productName}. You can re-use address spaces locally by enabling static network address translation (NAT) for a subnet. NAT is static. This means that inbound connections - from {props.productName} to the site behind the {props.connectorName} - are allowed, and connections do not have to be initiated by hosts behind the {props.connectorName}. NAT is also 1:1, that is, the {props.connectorName} will translate between corresponding addresses in two equal-sized prefixes.
+Each subnet (directly-attached or routed) must have a unique address space within your Magic WAN. You can re-use address spaces locally by enabling static network address translation (NAT) for a subnet. NAT is static. This means that inbound connections - from Magic WAN to the site behind the Connector - are allowed, and connections do not have to be initiated by hosts behind the Magic WAN Connector. NAT is also 1:1, that is, the Connector will translate between corresponding addresses in two equal-sized prefixes.
-To enable NAT, supply a WAN-facing address prefix the same size as the subnet's prefix, and the {props.connectorName} will translate between the two.
+To enable NAT, supply a WAN-facing address prefix the same size as the subnet's prefix, and the Magic WAN Connector will translate between the two.
For example:
- **Prefix**: `192.168.100.0/24`
- **Static NAT prefix**: `10.10.100.0/24`
-With the example above, outbound traffic from host `192.168.100.13` in the subnet is translated to `10.10.100.13` in the {props.connectorName} (and vice versa for incoming traffic).
+With the example above, outbound traffic from host `192.168.100.13` in the subnet is translated to `10.10.100.13` in the Magic WAN Connector (and vice versa for incoming traffic).
:::note
-Even if NAT is enabled, the local prefix for a subnet must be unique within its LAN. It can, however, be reused on other LANs or other sites. Overlay-facing prefixes - that is, a subnet's NAT prefix if NAT is enabled, and its local prefix otherwise - must always be unique across your whole {props.productName}.
+Even if NAT is enabled, the local prefix for a subnet must be unique within its LAN. It can, however, be reused on other LANs or other sites. Overlay-facing prefixes - that is, a subnet's NAT prefix if NAT is enabled, and its local prefix otherwise - must always be unique across your whole Magic WAN.
:::
## Create NATs for subnets
-For more information on how to a create a NAT for a subnets, refer to **Create a LAN**, either in {props.configHardProductName} or in {props.configVirtualProductName}.
+For more information on how to a create a NAT for a subnets, refer to **Create a LAN**, either in Configure hardware Connector or in Configure Virtual Connector.
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
index 2f5e3cb640805c..bc063096b4e743 100644
--- a/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx
@@ -1,23 +1,20 @@
---
params:
- - productName
- dashName
- hardConnectorURL
- virtualConnectorURL
- - configHardProductName
- - configVirtualProductName
---
import { APIRequest, Markdown, Render, TabItem, Tabs } from "~/components";
-You can define policies in your {props.productName} to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
+You can define policies in your Magic WAN Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features. The default behavior is to drop all LAN-to-LAN traffic. These policies can be created for specific subnets, and link two LANs.
{`
flowchart LR
accTitle: In this example, there are LANs where traffic flows between each other, instead of going to Cloudflare first.
- a(${props.productName}) <---> b(Internet) <---> c(Cloudflare)
+ a(Magic WAN Connector) <---> b(Internet) <---> c(Cloudflare)
subgraph Customer site
d[LAN 1] <---> a
@@ -43,7 +40,7 @@ If you enable LAN to LAN traffic flows, communications can only be initiated fro
Unidirectional communication can be enabled for UDP and ICMP, but it is not available for TCP, as it would break that protocol.
-The following guide assumes you have already created a site and configured your {props.productName}. To learn how to create a site and configure your {props.productName}, refer to {props.configHardProductName} or {props.configVirtualProductName}, depending on the type of {props.productName} you have on your premises.
+The following guide assumes you have already created a site and configured your Magic WAN Connector. To learn how to create a site and configure your Magic WAN Connector, refer to Configure hardware Connector or Configure Virtual Connector, depending on the type of Magic WAN Connector you have on your premises.
## Create a policy
@@ -73,22 +70,35 @@ Follow the steps below to create a new LAN policy to segment your network. Only
)
}
-3. Select the {props.productName} you want to configure > **Edit**.
-4. Go to **Network Configuration**, and scroll down to **LAN configuration**.
-5. Select **LAN policies** > **Create Policy**.
-6. In **Policy name**, enter a descriptive name for the policy you are creating.
-7. From the drop-down menu **Origin (required)**, select your origin LAN.
-8. Specify a subnet for your first LAN in **Subnets**.
-9. In **Ports** specify the TCP/UDP ports you want to use. Valid ports range from `1` to `65535`. Zero (`0`) is not a valid port number. Add a comma to separate each of the ports or add a port range. For example, \`2,5,6,9-14\`.
-10. In **Destination (required)**, select the destination LAN and repeat the above process to configure it.
-11. In **Protocols**, select the type of traffic you want to allow. You can choose **TCP**, **UDP**, and **ICMP**. You can also select **Any** to choose all types of traffic.
-12. In **Traffic direction** you can choose between bidirectional traffic (the default) and unidirectional traffic. What you can choose depends on the protocol that you chose for the policy:
- 1. **Any**: If **Any** is selected and you choose **Unidirectional**, the system will alert you that this will break TCP traffic.
- 2. **TCP**: You can only select **Bidirectional**.
- 3. **UDP**: The system defaults to **Bidirectional** but you can choose **Unidirectional**.
- 4. **ICMP**: The system defaults to **Bidirectional** but you can choose **Unidirectional**.
-13. In **Traffic path**, select **Forwarded via Cloudflare** if you want traffic to be forwarded to Cloudflare to be processed. If you do not select this option, traffic will flow locally, in your premises without passing through Cloudflare.
-14. Select **Create policy**.
+{/* Command needed so list starts on number 3 since steps 1, 2 are inside conditional render */}
+
+ - Select the Magic WAN Connector you want to configure > Edit.
+ { props.dashName === "Magic WAN" && (
+ - Go to Network Configuration, and scroll down to LAN configuration.
+ )
+ }
+
+{/* Command needed so list continues with correct number depending on product */}
+
+ - Select LAN policies > {props.dashName === "Magic WAN" ? "Create Policy" : "Create"}.
+ - In Policy name, enter a descriptive name for the policy you are creating.
+ - From the drop-down menu Origin (required), select your origin LAN.
+ - Specify a subnet for your first LAN in Subnets.
+ - In Ports specify the TCP/UDP ports you want to use. Valid ports range from
1 to 65535. Zero (0) is not a valid port number. Add a comma to separate each of the ports or add a port range. For example, 2,5,6,9-14.
+ - In Destination (required), select the destination LAN and repeat the above process to configure it.
+ - In Protocols, select the type of traffic you want to allow. You can choose TCP, UDP, and ICMP. You can also select Any to choose all types of traffic.
+ -
+ In Traffic direction you can choose between bidirectional traffic (the default) and unidirectional traffic. What you can choose depends on the protocol that you chose for the policy:
+
+ - Any: If Any is selected and you choose Unidirectional, the system will alert you that this will break TCP traffic.
+ - TCP: You can only select Bidirectional.
+ - UDP: The system defaults to Bidirectional but you can choose Unidirectional.
+ - ICMP: The system defaults to Bidirectional but you can choose Unidirectional.
+
+
+ - In Traffic path, select Forwarded via Cloudflare if you want traffic to be forwarded to Cloudflare to be processed. If you do not select this option, traffic will flow locally, in your premises without passing through Cloudflare.
+ - Select Save.
+
@@ -217,11 +227,20 @@ The new policy will ensure that traffic between the specified LANs flows locally
)
}
-3. Select the {props.productName} you want to configure > **Edit**.
-4. Go to **Network Configuration**, and scroll down to **LAN configuration**.
-5. Select **LAN policies**.
-6. Select the policy you need to edit > **Edit**.
-7. Make your changes, and select **Update policy**.
+{/* Command needed so list starts on number 3 since steps 1, 2 are inside conditional render */}
+
+ - Select the Magic WAN Connector you want to configure > Edit.
+ { props.dashName === "Magic WAN" && (
+ - Go to Network Configuration, and scroll down to LAN configuration.
+ )
+ }
+
+{/* Command needed so list continues with correct number depending on product */}
+
+ - Select LAN policies.
+ - Select the policy you need to edit > Edit.
+ - Make your changes, and select Update policy.
+
@@ -322,12 +341,21 @@ Example:
)
}
-3. Select the {props.productName} you want to configure > **Edit**.
-4. Go to **Network Configuration**, and scroll down to **LAN configuration**.
-5. Select **LAN policies**.
-6. Select the policy you need to edit > **Edit**.
-7. Select **Delete**.
-8. Select **I understand that deleting a policy is permanent** in the dialog box > **Delete**.
+{/* Command needed so list starts on number 3 since steps 1, 2 are inside conditional render */}
+
+ - Select the Magic WAN Connector you want to configure > Edit.
+ { props.dashName === "Magic WAN" && (
+ - Go to Network Configuration, and scroll down to LAN configuration.
+ )
+ }
+
+{/* Command needed so list continues with correct number depending on product */}
+
+ - Select LAN policies.
+ - Select the policy you need to edit > Edit.
+ - Select Delete.
+ - Select I understand that deleting a policy is permanent in the dialog box > Delete.
+
diff --git a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
index 5af559004e6b72..e51e090b47c2f9 100644
--- a/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/routed-subnets.mdx
@@ -1,16 +1,13 @@
---
params:
- - productName
- netSubnetURL
- hardConnectorURL
- virtualConnectorURL
- - configHardProductName
- - configVirtualProductName
---
-Each LAN interface (physical port + VLAN tag) on {props.productName} is part of a _directly-attached subnet_. When you specify a static address for the LAN interface, you indicate both the interface's address as well as the subnet it attaches to. For example, `192.168.100.13/24` means the LAN interface has the IP address `192.168.100.13`, and is part of the subnet `192.168.100.0/24`.
+Each LAN interface (physical port + VLAN tag) on Magic WAN Connector is part of a _directly-attached subnet_. When you specify a static address for the LAN interface, you indicate both the interface's address as well as the subnet it attaches to. For example, `192.168.100.13/24` means the LAN interface has the IP address `192.168.100.13`, and is part of the subnet `192.168.100.0/24`.
-Some LANs are more complex. In addition to the directly-attached subnet, they might have additional subnets sitting behind L3 routers south of the {props.productName}. We call these _routed subnets_.
+Some LANs are more complex. In addition to the directly-attached subnet, they might have additional subnets sitting behind L3 routers south of the Magic WAN Connector. We call these _routed subnets_.
Refer to the diagram below for an example of how this might work:
@@ -26,7 +23,7 @@ Blue represents directly-attached subnets, and red represents routed subnets.
a((WAN)) --> b
- subgraph b [${props.productName}]
+ subgraph b [Magic WAN Connector]
direction TB
c(LAN 1)
d(LAN n)
@@ -51,11 +48,11 @@ Blue represents directly-attached subnets, and red represents routed subnets.
To add a routed subnet to your LAN, you need:
-- **A prefix**: The subnet's CIDR prefix; Cloudflare will automatically install static routes to this prefix in our global network (to forward [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/) for this subnet to the right {props.productName}), and in your {props.productName} (to forward packets for this subnet to the right LAN interface). In the figure above, the routed subnet in the center has the prefix `192.168.200.0/24`.
-- **A next-hop address**: The address of the L3 router to which the {props.productName} should forward packets for this subnet. In the figure, the routed subnet in the center has the next-hop address `192.168.100.10`.
+- **A prefix**: The subnet's CIDR prefix; Cloudflare will automatically install static routes to this prefix in our global network (to forward [packets](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/) for this subnet to the right Magic WAN Connector), and in your Magic WAN Connector (to forward packets for this subnet to the right LAN interface). In the figure above, the routed subnet in the center has the prefix `192.168.200.0/24`.
+- **A next-hop address**: The address of the L3 router to which the Magic WAN Connector should forward packets for this subnet. In the figure, the routed subnet in the center has the next-hop address `192.168.100.10`.
Optionally, you can also enable NAT for a subnet by providing a static overlay prefix.
## Create routed subnets
-For more information on how to create routed subnets, refer to **Create a LAN**, either in either in {props.configHardProductName} or in {props.configVirtualProductName}.
+For more information on how to create routed subnets, refer to **Create a LAN**, either in either in Configure hardware Connector or in Configure Virtual Connector.
diff --git a/src/content/partials/networking-services/mconn/spf-port-info.mdx b/src/content/partials/networking-services/mconn/spf-port-info.mdx
index b172a8cad9256d..0a502bf795ed0c 100644
--- a/src/content/partials/networking-services/mconn/spf-port-info.mdx
+++ b/src/content/partials/networking-services/mconn/spf-port-info.mdx
@@ -1,13 +1,11 @@
---
-params:
- - productName
- - productNameVirtual
+{}
---
-The hardware version of {props.productName} includes two [SFP+ ports](https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable) that support 10G throughput. These ports can be configured as either a WAN or a LAN port, like all of the 1G RJ45 ports in the machine. Because a 10G WAN uplink will often be bottlenecked by IPsec tunnel speeds, the SFP+ ports are most useful for configuring high speed LANs, and for using fiber connections.
+The hardware version of Magic WAN Connector includes two [SFP+ ports](https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable) that support 10G throughput. These ports can be configured as either a WAN or a LAN port, like all of the 1G RJ45 ports in the machine. Because a 10G WAN uplink will often be bottlenecked by IPsec tunnel speeds, the SFP+ ports are most useful for configuring high speed LANs, and for using fiber connections.
-:::note[{props.productNameVirtual} and SFP+ ports]
-Since you decide and set up the hardware where {props.productNameVirtual} runs, you can ignore the information on this page.
+:::note[Virtual Connector and SFP+ ports]
+Since you decide and set up the hardware where Virtual Connector runs, you can ignore the information on this page.
:::
## Port configuration
@@ -23,7 +21,7 @@ _The left port, SFP+ 1, is port 7. The right port, SFP+ 2, is port 8._
## SFP+ module compatibility
-{props.productName} only supports 10Gbps SFP+ modules, including RJ45, DAC, and fiber, among others. Many 1 Gbps modules are incompatible with the Intel driver used internally, and thus are not supported.
+Magic WAN Connector only supports 10Gbps SFP+ modules, including RJ45, DAC, and fiber, among others. Many 1 Gbps modules are incompatible with the Intel driver used internally, and thus are not supported.
Cloudflare supports the following SFP+ inputs:
@@ -40,8 +38,8 @@ Keep in mind that SFP+ modules/cables have to be compatible at both ends, that i
## Recover from unsupported SFP+ inputs
-SFP+ modules should be installed and tested prior to deploying {props.productName} into production usage.
+SFP+ modules should be installed and tested prior to deploying Magic WAN Connector into production usage.
-An unsupported SFP+ input is indicated by the interface failing to come up (that is, the {props.productName} has no status lights), and also by the port (7 or 8) going offline until the hardware is rebooted.
+An unsupported SFP+ input is indicated by the interface failing to come up (that is, the Magic WAN Connector has no status lights), and also by the port (7 or 8) going offline until the hardware is rebooted.
-When an unsupported module is plugged, the module should be removed and then {props.productName} rebooted by removing power for five seconds. The module should not remain plugged during reboot, or {props.productName} will have to be rebooted again after the module is removed.
+When an unsupported module is plugged, the module should be removed and then Magic WAN Connector rebooted by removing power for five seconds. The module should not remain plugged during reboot, or Magic WAN Connector will have to be rebooted again after the module is removed.
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx
index 2958dacf15c28c..6766cdfc629828 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting-steps.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
---
@@ -11,7 +10,8 @@ import { DashButton, Markdown } from "~/components";
Cloudflare One, and go to **Networks** > **Connectors**.
- 2. Go to **Appliances** > **Profiles** > **View analytics**.
+ 2. Go to **Appliances** > **Profiles**.
+ 3. Select your Connector > **View analytics**.
`}
inline={false}
/>
@@ -27,7 +27,8 @@ import { DashButton, Markdown } from "~/components";
**View analytics**.
+ 2. In the **Magic WAN Connector** tab, select the Magic WAN Connector want to check analytics for.
+ 3. Select **View analytics**.
`}
inline={false}
/>
diff --git a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
index 6b5d74fec72b15..c04e71cb70961c 100644
--- a/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
+++ b/src/content/partials/networking-services/mconn/troubleshooting/troubleshooting.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- dashName
- activateURL
- firewallURL
@@ -11,20 +10,20 @@ import { Render } from "~/components";
## Device metrics
-Cloudflare customers can inspect metrics for a specific {props.productName} in the Cloudflare dashboard. These metrics help you troubleshoot potential issues with your device. The information spans categories such as:
+Cloudflare customers can inspect metrics for a specific Magic WAN Connector in the Cloudflare dashboard. These metrics help you troubleshoot potential issues with your device. The information spans categories such as:
- Performance analytics
- Port analytics
- Event logs
- DHCP leasing information
-To find the information above and start troubleshooting your {props.productName}:
+To find the information above and start troubleshooting your Magic WAN Connector:
-Cloudflare One, and go to **Networks**.
- 2. Go to **Routes** > **WAN Routes**, and select **Add a static route** to add a new route.
+ 2. Go to **Routes** > **WAN Routes**, and select **Create** to add a new route.
`}
inline={false}
/>
@@ -174,7 +174,8 @@ Example:
<>
**WAN Routes**, select the three dots > **Edit** next to the route you want to modify.
+ 1. In **Routes** > **WAN Routes** find the route you want to modify.
+ 2. Select the three dots next to it > **Edit**.
`}
inline={false}
/>
@@ -187,7 +188,8 @@ Example:
<>
**Edit** next to the route you want to modify.
+ 1. In **Routes** find the route you want to modify.
+ 2. Select the three dots next to it > **Edit**.
`}
inline={false}
/>
@@ -195,9 +197,9 @@ Example:
)
}
-2. Enter the updated route information.
-3. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.
-4. Select **Edit routes** to save the new information when you are done.
+3. Enter the updated route information.
+4. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.
+5. Select **Edit routes** to save the new information when you are done.
@@ -276,7 +278,8 @@ Example:
<>
**WAN Routes**, locate the static route you want to modify, select the three dots > **Delete**.
+ 1. In **Routes** > **WAN Routes**, locate the static route you want to modify.
+ 2. Select the three dots next to it > **Delete**.
`}
inline={false}
/>
@@ -289,7 +292,8 @@ Example:
<>
**Delete**.
+ 1. In **Routes**, locate the static route you want to modify.
+ 2. Select the three dots next to it > **Delete**.
`}
inline={false}
/>
@@ -297,7 +301,7 @@ Example:
)
}
-2. Confirm the action by selecting the checkbox and select **Delete**.
+3. Confirm the action by selecting the checkbox and select **Delete**.
@@ -371,7 +375,8 @@ To set this ASN:
text={`
1. Log in to Cloudflare One, and go to **Networks**.
2. Go to **Routes** > **WAN configuration**.
- 3. In **Account-level virtual network overlay**, select **Edit ASN** and enter your ASN.
+ 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit** and enter your ASN.
+ 4. Select **Save**.
`}
inline={false}
/>
@@ -393,6 +398,7 @@ To set this ASN:
text={`
2. Go to **BGP configuration**.
3. In **CF Account ASN**, enter Cloudflare's ASN.
+ 4. Select **Update**.
`}
inline={false}
/>
@@ -400,8 +406,6 @@ To set this ASN:
)
}
-4. Select **Update**.
-
{ props.magicWord === "Magic Transit" && (
<>
Cloudflare One, and go to **Networks**.
2. Go to **Routes** > **WAN configuration**.
- 3. In **Account-level virtual network overlay**, select **Edit ASN** and enter your ASN.
- 4. Go to **Networks** > **Interconnects**.
+ 3. In **Border Gateway Protocol (BGP) configuration**, select **Edit ASN** and enter your ASN.
+ 4. Go to **Networks** > **Connectors** > **Interconnects**.
`}
inline={false}
/>
diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx
index 47a416ef30b850..ba06ed886a3034 100644
--- a/src/content/partials/networking-services/routing/configure-tunnels.mdx
+++ b/src/content/partials/networking-services/routing/configure-tunnels.mdx
@@ -1,13 +1,12 @@
---
params:
- - magicWord?
+ - magicWord
- ipRange?
- productName
- tunnelsAndEncapsulationPagePath
- ciphersPagePath
- antiReplayPagePath
- cniLink
- - targetPageName
- dashButtonPath?
- updateHCFrequencyPage
- tunnelHealthChecksPage
@@ -86,11 +85,14 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
{/* Dashboard steps for WAN Tunnels (Cloudflare One dashboard) */}
{ props.magicWord === "WAN Tunnels" && (
<>
-
- - Log in to Cloudflare One, and go to Networks.
- - Go to Connectors > WAN Tunnels, and select Create a tunnel.
- - On the Add Tunnel page, choose either a GRE tunnel or IPsec tunnel.
-
+ Cloudflare One, and go to **Networks**.
+ 2. Go to **Connectors** > **WAN Tunnels**, and select **Create**.
+ 3. On the **Add Tunnel** page, choose either a **GRE tunnel** or **IPsec tunnel**.
+ `}
+ inline={false}
+ />
)
}
@@ -98,13 +100,20 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb
{/* Dashboard steps for Magic WAN and Magic Transit (standalone dashboards) */}
{ props.magicWord !== "WAN Tunnels" && (
<>
-
- - In the Cloudflare dashboard, go to {props.productName}'s {props.targetPageName} page.
-
- - From the Tunnels tab, select Create.
- - On the Add tunnels page, choose either a GRE tunnel or IPsec tunnel.
-
+ traceroute]
-{props.productName} clients connecting through GRE, IPsec, [CNI](/network-interconnect/) or WARP that want to perform a `traceroute` to an endpoint behind a Cloudflare Tunnel will need to change some settings to make the command useful. Refer to Run `traceroute` for more information.
+Magic WAN clients connecting through GRE, IPsec, [CNI](/network-interconnect/) or WARP that want to perform a `traceroute` to an endpoint behind a Cloudflare Tunnel will need to change some settings to make the command useful. Refer to Run `traceroute` for more information.
:::
diff --git a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
index 938b771b36ca56..711baf5e7fcf23 100644
--- a/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
+++ b/src/content/partials/networking-services/tunnel-health/check-tunnel-healthchecks-dash.mdx
@@ -29,7 +29,7 @@ Not all data centers will be relevant to you at all times. You can refer to the
1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) and go to **Insights**.
2. Go to **Network visibility** > **WAN connector health**.
- 3. In the next screen you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+ 3. In this screen screen you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
4. Find the tunnel you wish to inspect, select the three dots in front of the tunnel and select:
- **Create alert**: This will send you to the ${props.notificationsPath} so you can create specific alerts for that tunnel, to be warned when specific conditions are met.
- **Network Analytics**: This will send you to the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
@@ -66,7 +66,7 @@ To check for anycast tunnel health:
text={`
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
2. Go to **${props.productPath}**.
- 3. In the next screen you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
+ 3. In this screen you can access a list of your tunnels and their current health status. You can also check the amount of health checks passed in the last hour as well as traffic volume for each tunnel.
4. Find the tunnel you wish to inspect, select the three dots in front of the tunnel and select:
- **Create alert**: This will send you to the ${props.notificationsPath} so you can create specific alerts for that tunnel, to be warned when specific conditions are met.
- **Network Analytics**: This will send you to the Analytics section of the dash, prefiltered with the tunnel you want to inspect.
@@ -83,7 +83,7 @@ To check for anycast tunnel health:
## Check tunnel health for a specific tunnel
-Beyond having a wide view into all connections, you can drill down into a specific tunnel to check its health status and other information. Refer to the blue note above to learn how to access the new dashboard experience, and:
+Beyond having a wide view into all connections, you can drill down into a specific tunnel to check its health status and other information.{props.magicWord !== "WAN Tunnels" && <> Refer to the blue note above to learn how to access the new dashboard experience, and:}
1. Go to **{props.productPath}**.
2. Find and select the tunnel you wish to inspect.
diff --git a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
index 095b35ecc5a600..f8e99f55a12e1c 100644
--- a/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
+++ b/src/content/partials/networking-services/tunnel-health/mconn-heartbeat-health.mdx
@@ -1,9 +1,8 @@
---
params:
- - productName
- heartbeatURL
---
-{props.productName} also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare via HTTPS and lets Cloudflare know that the {props.productName} in question is connected to the Internet and reachable.
+Magic WAN Connector also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare via HTTPS and lets Cloudflare know that the Magic WAN Connector in question is connected to the Internet and reachable.
Refer to Heartbeat to learn more.
\ No newline at end of file