Skip to content

Commit dad96d1

Browse files
[MWAN] Added rfc ips to routes (#25901)
* added rfc ips * created single partial for info
1 parent f464a7c commit dad96d1

File tree

4 files changed

+44
-11
lines changed

4 files changed

+44
-11
lines changed

src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,8 @@ import { Render } from "~/components"
2222
chooseWeights: "/magic-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
2323
publicAsnMT: " ",
2424
productGatewayOrEgress: "Magic WAN with Gateway",
25-
dashButtonPath: "/?to=/:account/magic-wan/configuration"
25+
dashButtonPath: "/?to=/:account/magic-wan/configuration",
26+
cfTunnelURL: "/magic-wan/zero-trust/cloudflare-tunnel/",
2627
}}
2728
/>
2829

src/content/partials/networking-services/reference/traffic-steering.mdx

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -47,16 +47,14 @@ The following IPv4 address ranges are allowed in the Magic Routing table:
4747

4848
{ props.magicWord === "Magic WAN" && (
4949
<>
50-
<Markdown
51-
text={`
52-
- [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address space, specifically \`10.0.0.0/8\`, \`172.16.0.0/12\`, and \`192.168.0.0/16\`.
53-
54-
When using ${props.productName} and Cloudflare Tunnel together, remember to consider the IP ranges utilized in the static routes of Cloudflare Tunnel when selecting static routes for ${props.productName}. For more information, refer to <a href="${props.cfTunnelURL}">Cloudflare Tunnel</a>.
55-
56-
For prefixes outside RFC 1918 contact your Cloudflare customer service manager.
57-
`}
58-
inline={false}
59-
/>
50+
<Render
51+
file="routing/magic-wan-allowed-ip-ranges"
52+
product="networking-services"
53+
params={{
54+
productName: props.productName,
55+
cfTunnelURL: props.cfTunnelURL
56+
}}
57+
/>
6058
</>
6159
)
6260
}

src/content/partials/networking-services/routing/configure-routes.mdx

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ params:
99
- chooseWeights
1010
- productGatewayOrEgress
1111
- dashButtonPath
12+
- cfTunnelURL?
1213
---
1314

1415
import { Aside, APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
@@ -29,6 +30,21 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
2930

3031
## Configure static routes
3132

33+
{ props.magicWord === "Magic WAN" && (
34+
<>
35+
<p>The following IPv4 address ranges are allowed in the Magic Routing table:</p>
36+
<Render
37+
file="routing/magic-wan-allowed-ip-ranges"
38+
product="networking-services"
39+
params={{
40+
productName: props.productName,
41+
cfTunnelURL: props.cfTunnelURL
42+
}}
43+
/>
44+
</>
45+
)
46+
}
47+
3248
### Create a static route
3349

3450
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
params:
3+
- productName
4+
- cfTunnelURL
5+
---
6+
7+
import { Markdown } from "~/components";
8+
9+
<Markdown
10+
text={`
11+
- [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address space, specifically \`10.0.0.0/8\`, \`172.16.0.0/12\`, and \`192.168.0.0/16\`.
12+
13+
When using ${props.productName} and Cloudflare Tunnel together, remember to consider the IP ranges utilized in the static routes of Cloudflare Tunnel when selecting static routes for ${props.productName}. For more information, refer to <a href="${props.cfTunnelURL}">Cloudflare Tunnel</a>.
14+
15+
For prefixes outside RFC 1918 contact your Cloudflare customer service manager.
16+
`}
17+
inline={false}
18+
/>

0 commit comments

Comments
 (0)