Skip to content

[MWAN] Broken links #19661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 3, 2025
Merged

[MWAN] Broken links #19661

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a92f683
corrected legacy hcs links
marciocloudflare Feb 3, 2025
e401b84
refined legacy hc partial
marciocloudflare Feb 3, 2025
f3eb25e
changed title
marciocloudflare Feb 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/magic-transit/how-to/bgp-peering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ import { Render } from "~/components"
params={{
productName: "Magic Transit",
productPath: "/magic-transit/reference/tunnel-health-checks/",
legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-health-checks-system",
legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
asnProduct: "<br /> Magic Transit customers should also be aware of the following: <br /> <ul><li>The Cloudflare side ASN will never be exposed in <code>AS_PATH</code> of anycast announcements from the Cloudflare edge. In those announcements, Cloudflare will always use the Cloudflare ASN of <code>13335</code> optionally prepended with a bring-your-own ASN as described in [Cloudflare ASN vs. your own ASN](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn)</li><li>The customer device ASN can be a private ASN or the ASN they are using for Magic Transit anycast announcements at the edge: this has no impact on the ASN for the anycast announced prefix at the edge of the Cloudflare global network.</li></ul>",
mtLimitations: "<br /> For Magic Transit customers, BGP with the Magic routing table is separated from the announcement of anycast prefixes at the Cloudflare edge. Anycast withdrawal must be controlled with existing methods documented in [Advertise prefixes](/magic-transit/how-to/advertise-prefixes/).",
productGatewayOrEgress: "Magic Transit with Egress"
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/magic-transit/how-to/configure-tunnels.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ import { GlossaryTooltip, Render } from "~/components";

<Render file="tunnel-endpoints/mt-egress" />

### Legacy health checks system
### Legacy bidirectional health checks

<Render file="legacy-hc-system" />

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/magic-wan/configuration/manually/how-to/bgp-peering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ import { Render } from "~/components"
params={{
productName: "Magic WAN",
productPath: "/magic-wan/reference/tunnel-health-checks/",
legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-health-checks-system",
legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
asnProduct: "<br /> Magic WAN customers should also be aware of the following: <br /> <ul><li>The Cloudflare side ASN will be included in the <code>AS_PATH</code> of announced routes to any BGP enabled interconnect.</li><li>The customer chooses their device ASN, which should be different to the Cloudflare-side ASN.</li></ul>",
mtLimitations: " ",
productGatewayOrEgress: "Magic WAN with Gateway"
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnels.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ import { GlossaryTooltip, Render } from "~/components";
params={{ productPathProbe: "/magic-wan/reference/tunnel-health-checks/" }}
/>

### Legacy health checks system
### Legacy bidirectional health checks

<Render file="legacy-hc-system" product="magic-transit" />

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/magic-wan/network-interconnect.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ With Direct CNI you can also setup BGP peering between your network and Cloudfla

### Bidirectional health checks

Bidirectional health checks do not work when you use Direct CNI to onboard your traffic to Cloudflare. You will need to resort to the [legacy health check system](/magic-wan/configuration/manually/how-to/configure-tunnels/#legacy-health-checks-system).
Bidirectional health checks do not work when you use Direct CNI to onboard your traffic to Cloudflare. You will need to resort to the [legacy health check system](/magic-wan/configuration/manually/how-to/configure-tunnels/#legacy-bidirectional-health-checks).

:::note
Do not use Magic WAN Connector with Direct CNI. You can use the Connector with a [Public Peering or a Private Network Interconnection (PNI)](/network-interconnect/pni-and-peering/) if needed.
Expand Down
6 changes: 3 additions & 3 deletions src/content/partials/magic-transit/legacy-hc-system.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

---

For customers using the legacy health check system with a public IP range, Cloudflare recommends that:
For customers using the legacy health check system with a public IP range, Cloudflare recommends:

1. You configure the IP address for your tunnel health check target to be one from within the prefix range `172.64.240.252/30`.
2. Apply a policy-based route that matches packets with source IP address equal to the configured tunnel health check target (for example `172.64.240.253/32`), and route them over the tunnel back to Cloudflare.
- Configuring the tunnel health check target IP address to one within the `172.64.240.252/30` prefix range.
- Applying a policy-based route that matches packets with a source IP address equal to the configured tunnel health check target (for example `172.64.240.253/32`), and route them over the tunnel back to Cloudflare.