Skip to content

Commit a67020c

Browse files
committed
Revamp diagram
1 parent a1ee4ff commit a67020c

File tree

1 file changed

+25
-11
lines changed
  • src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic

1 file changed

+25
-11
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/index.mdx

Lines changed: 25 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -22,18 +22,32 @@ There are four options you can configure to exclude traffic from WARP:
2222

2323
## How the WARP client handles DNS requests
2424

25-
When you use the WARP client together with `cloudflared` Tunnels or third-party VPNs, Cloudflare evaluates each request and routes it according to the following traffic flow.
25+
When you use the WARP client together with `cloudflared` Tunnels or third-party VPNs, Cloudflare evaluates each request and routes it according to the following traffic flow:
2626

2727
```mermaid
2828
flowchart TD
29-
accTitle: WARP traffic is evaluated and routed through various parts of the Cloudflare network
30-
A[WARP User requests resource] -- Domain does not match Local Domain Fallback --> C{WARP client resolves query according to Gateway DNS policies}
31-
A -- Domain matches Local Domain Fallback --> D[WARP client proxies DNS traffic to specified fallback server]
32-
D -- Resolver IP included in Tunnel per Split Tunnel configuration --> E[Query sent via WARP Tunnel to be resolved]
33-
D -- Resolver IP not included in Tunnel per Split Tunnel configuration --> F{Query sent to resolver IP outside WARP Tunnel}
34-
E -- Matches CF Gateway block policy --> G{Traffic blocked by CF}
35-
E -- "Passes CF Gateway network policies (allowed or unblocked)" --> H[Evaluated by Cloudflare Tunnel routes]
36-
H -- Tunnel routes do not include resolver IP --> I{CF Gateway proxies query to resolver IP via normal WARP egress route}
37-
H -- Tunnel routes include resolver IP --> J[Cloudflare Tunnel advertises route that includes Resolver IP]
38-
J --> L{Private resolver returns IP address to WARP client}
29+
D["WARP client proxies DNS traffic to specified fallback server"] -- Resolver IP included in Tunnel per Split Tunnel configuration --> E["Query sent via WARP Tunnel to be resolved"]
30+
D -- Resolver IP not included in Tunnel per Split Tunnel configuration --> F["Query sent to resolver IP outside WARP Tunnel"]
31+
E -- Blocked by Gateway --> G["Traffic blocked by Cloudflare"]
32+
E -- Allowed by Gateway --> H["Evaluated by Cloudflare Tunnel routes"]
33+
H -- Tunnel routes do not include resolver IP --> I["Gateway proxies query to resolver IP via normal WARP egress route"]
34+
H -- Tunnel routes include resolver IP --> J["Cloudflare Tunnel advertises route that includes Resolver IP"]
35+
J --> L["Private resolver returns IP address to WARP client"]
36+
n1["Local Domain Fallback"] -- Matches domain --> C["WARP client resolves query according to Gateway policies"]
37+
n1 -- Does not match domain --> D
38+
A["WARP user requests resource"] --> n2["Gateway resolver policies"]
39+
n2 -- Does not match traffic --> n1
40+
n2 -- Matches traffic --> C
41+
42+
D@{ shape: rect}
43+
E@{ shape: hex}
44+
F@{ shape: terminal}
45+
G@{ shape: terminal}
46+
H@{ shape: hex}
47+
I@{ shape: terminal}
48+
L@{ shape: terminal}
49+
n1@{ shape: proc}
50+
C@{ shape: terminal}
51+
A@{ shape: in-out}
52+
n2@{ shape: proc}
3953
```

0 commit comments

Comments
 (0)