You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+38-33Lines changed: 38 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -300,47 +300,52 @@ You need to delete {props.featureName} applications for each of your existing si
300
300
301
301
</TabItem> </Tabs>
302
302
303
-
## Designate WAN ports for breakout apps
303
+
{props.magicWord==="breakout"&& (
304
+
<>
305
+
## Designate WAN ports for breakout apps
304
306
305
-
You can pin applications to a specific WAN port in {props.productName} when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, {props.productName} automatically fails over to a standard configured WAN port priority.
307
+
You can pin applications to a specific WAN port in {props.productName} when you need control over which WAN port your applications egress from the device. In case your preferred WAN port goes down, {props.productName} automatically fails over to a standard configured WAN port priority.
306
308
307
-
With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
309
+
With this preferred breakout port, customers have direct control over their local Internet breakout traffic. You can designate a specific WAN uplink as the primary path for your critical applications configured to bypass the Cloudflare network. This provides the predictability and control needed for performance-sensitive applications, ensuring your critical traffic always takes the path you choose.
308
310
309
-
To pin applications to a WAN port:
311
+
To pin applications to a WAN port:
310
312
311
-
{props.mwanName==="WAN Tunnels"? (
312
-
<>
313
-
<Markdown
314
-
text={`
315
-
1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
316
-
2. Go to **Connectors** > **Appliances** > **Profiles**.
317
-
3. Under **Profiles**, select your appliance > **Edit**.
318
-
`}
319
-
inline={false}
320
-
/>
321
-
</>
322
-
) : (
323
-
<>
313
+
{props.mwanName==="WAN Tunnels"? (
314
+
<>
315
+
<Markdown
316
+
text={`
317
+
1. Log in to the <a href="https://one.dash.cloudflare.com/">Cloudflare One dashboard</a>, and go to **Networks**.
318
+
2. Go to **Connectors** > **Appliances** > **Profiles**.
319
+
3. Under **Profiles**, select your appliance > **Edit**.
320
+
`}
321
+
inline={false}
322
+
/>
323
+
</>
324
+
) : (
325
+
<>
326
+
<Markdown
327
+
text={`
328
+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
0 commit comments