Skip to content

Commit 1c81297

Browse files
[Magic] Mermaid graphs titles update (#28034)
* corrected titles * refined titles * adds meta data
1 parent 278e32f commit 1c81297

File tree

6 files changed

+25
-6
lines changed

6 files changed

+25
-6
lines changed

src/content/partials/networking-services/magic-wan/zero-trust/gateway.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,8 @@ The following diagram illustrates how DNS queries from Magic WAN and WARP Connec
6666
<pre class="mermaid">
6767
{`
6868
flowchart LR
69+
accTitle: DNS query flow
70+
accDescr: Shows how DNS queries from Magic WAN and WARP Connector flow through Gateway to internal DNS.
6971
subgraph subGraph0["Data center"]
7072
direction TB
7173
InternalDNS(["Internal DNS"])

src/content/partials/networking-services/mconn/configure-connectors.mdx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -490,7 +490,8 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
490490

491491
<pre class="mermaid">
492492
{`flowchart LR
493-
accTitle: ${props.productName} set up as a DHCP server, and connecting to the Internet.
493+
accTitle: Connector as WAN router
494+
accDescr: ${props.productName} set up as a DHCP server, and connecting to the Internet.
494495
a(${props.productName})--> b(Internet) --> c(Cloudflare)
495496
496497
subgraph Customer site
@@ -502,11 +503,14 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
502503
class a,c orange`}
503504
</pre>
504505

506+
<p><em>{props.productName} set up as a DHCP server, and connecting to the Internet.</em></p>
507+
505508
<p>In the following example, the {props.productName} device sits behind the WAN router in your site, and on-ramps only some of the existing LANs to Cloudflare.</p>
506509

507510
<pre class="mermaid">
508511
{`flowchart LR
509-
accTitle: ${props.productName} connects to the router in the site, and only some of the LANs connect to Connector.
512+
accTitle: Connector behind site router
513+
accDescr: ${props.productName} connects to the router in the site, and only some of the LANs connect to Connector.
510514
a(${props.productName})--> b((Site's router)) --> c(Internet) --> i(Cloudflare)
511515
512516
subgraph Customer site
@@ -520,6 +524,8 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
520524
class a,i orange`}
521525
</pre>
522526

527+
<p><em>{props.productName} connects to the router in the site, and only some of the LANs connect to Connector.</em></p>
528+
523529
<p>Refer to <a href="/reference-architecture/diagrams/sase/magic-wan-connector-deployment/">{props.productName} deployment options</a> for a high-level explanation of the deployment options that make sense to most environments, as well as a few advanced use cases.</p>
524530

525531
<AnchorHeading title="Firewall settings required" depth={4} />

src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,8 @@ import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, T
3131
<pre class="mermaid">
3232
{`
3333
flowchart LR
34-
accTitle: In this example, the applications go directly to the Internet, skipping Cloudflare's security filtering
34+
accTitle: Breakout traffic flow
35+
accDescr: Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.
3536
a(Magic WAN Connector) --> b(Cloudflare) -->|Filtered traffic|c(Internet)
3637
3738
a-- Breakout traffic ---d(Application1) & e(Application2) --> c
@@ -40,7 +41,7 @@ import { APIRequest, Aside, AnchorHeading, CURL, DashButton, Markdown, Render, T
4041
class a,b orange
4142
`}
4243
</pre>
43-
<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet</em></p>
44+
<p><em>In the graph above, Applications 1 and 2 are configured to bypass Cloudflare's security filtering, and go straight to the Internet.</em></p>
4445
<Aside type="note" title="A note on security">
4546
<Markdown
4647
text={`

src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,8 @@ DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that
1212
<pre class="mermaid">
1313
{`
1414
flowchart LR
15-
accTitle: An example of Connector in DHCP Relay mode
15+
accTitle: DHCP Relay diagram
16+
accDescr: The graph shows Magic WAN Connector sending DHCP discover messages to a DHCP server offsite.
1617
a(Magic WAN Connector) <--> b(Cloudflare/Magic WAN) <--> c(DHCP server)
1718
1819
subgraph Site A

src/content/partials/networking-services/mconn/network-options/network-segmentation.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,8 @@ You can define policies in your Magic WAN Connector to either allow traffic to f
1212
<pre class="mermaid">
1313
{`
1414
flowchart LR
15-
accTitle: In this example, there are LANs where traffic flows between each other, instead of going to Cloudflare first.
15+
accTitle: LAN-to-LAN traffic flow
16+
accDescr: In this example, the red path shows traffic that stays in the customer's premises (allowing direct communication between LAN 3 and LAN 4), and the orange path shows traffic that goes to Cloudflare before returning to the customer's premises (processing traffic between LAN 1 and LAN 2 in Cloudflare).
1617
a(Magic WAN Connector) <---> b(Internet) <---> c(Cloudflare)
1718
1819
subgraph Customer site

src/content/partials/networking-services/reference/tunnel-health-checks.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,8 @@ To avoid control plane policies enforced by the origin network, you can set tunn
124124

125125
```mermaid
126126
flowchart TB
127+
accTitle: Bidirectional request style
128+
accDescr: Shows the flow of a bidirectional request-style tunnel health check probe and response between Cloudflare and the origin.
127129
subgraph Tunnel Healthcheck Probe
128130
cloudflare(Cloudflare) --- bare_echo_request([ICMP Echo Request])
129131
bare_echo_request --> tunnel[Tunnel]
@@ -150,6 +152,8 @@ flowchart TB
150152

151153
```mermaid
152154
flowchart TB
155+
accTitle: Bidirectional reply style
156+
accDescr: Shows the flow of a bidirectional reply-style tunnel health check probe and response between Cloudflare and the origin.
153157
subgraph Tunnel Healthcheck Probe
154158
cloudflare(Cloudflare) --- bare_echo_probe([ICMP Echo Reply])
155159
bare_echo_probe --> tunnel[Tunnel]
@@ -176,6 +180,8 @@ flowchart TB
176180

177181
```mermaid
178182
flowchart TB
183+
accTitle: Unidirectional echo request
184+
accDescr: Shows the flow of a unidirectional echo request health check from Cloudflare to the origin and back.
179185
cloudflare(Cloudflare) --- bare_echo_probe([ICMP Echo Request])
180186
bare_echo_probe --> tunnel[Tunnel]
181187
tunnel --- encapsulated_echo_probe([Tunnel Protocol < ICMP Echo Request >])
@@ -193,6 +199,8 @@ flowchart TB
193199

194200
```mermaid
195201
flowchart TB
202+
accTitle: Unidirectional echo reply
203+
accDescr: Shows the flow of a unidirectional echo reply health check from Cloudflare to the origin and back.
196204
cloudflare(Cloudflare) --- bare_echo_probe([ICMP Echo Reply])
197205
bare_echo_probe --> tunnel[Tunnel]
198206
tunnel --- encapsulated_echo_probe([Tunnel Protocol < ICMP Echo Reply >])

0 commit comments

Comments
 (0)