Skip to content

Commit 2d42903

Browse files
marciocloudflareelithrar
authored andcommitted
[MWAN] WARP Connector breakout traffic (#17138)
* added warp encapsulation partial * added new warp info to pages * reworked explainer * refined text * refined text
1 parent 86bef5c commit 2d42903

File tree

3 files changed

+28
-9
lines changed

3 files changed

+28
-9
lines changed

src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -179,3 +179,7 @@ Take note of the `"id"` value for the application that want to delete.
179179
```
180180

181181
</TabItem> </Tabs>
182+
183+
## WARP traffic
184+
185+
<Render file="connector/app-aware-policies/warp-traffic" />

src/content/docs/magic-wan/zero-trust/warp.mdx

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,18 @@ You must log out and log back in with at least one WARP device to ensure the con
5555

5656
<Render file="traceroute" />
5757

58+
## Double encapsulation
59+
60+
When a WARP user goes to a location (like an office) with a Magic WAN tunnel already set up, WARP traffic is doubly encapsulated — first by WARP and then by Magic WAN. This is unnecessary, since each on-ramp method provides full Zero Trust protection.
61+
62+
Since WARP traffic is already protected on its own, Cloudflare recommends that you set up Magic WAN to exclude WARP traffic, sending it to the Internet through regular connections.
63+
64+
To learn which IP addresses and UDP ports you should exclude to accomplish this, refer to [WARP ingress IP](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip).
65+
66+
### WARP and Magic WAN Connector
67+
68+
<Render file="connector/app-aware-policies/warp-traffic" />
69+
5870
## Test WARP integration
5971

6072
Before testing, be sure to [configure domain fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/#add-a-domain) for the server or service in WARP settings. This is needed because by default Cloudflare Zero Trust excludes common top level domains used for local resolution from being sent to Gateway for processing.
@@ -71,12 +83,4 @@ nslookup <SERVER_BEHIND_MAGIC_WAN>
7183

7284
This DNS lookup should return a valid IP address associated with the server or service you are testing for.
7385

74-
Next, test with a browser that you can connect to a service on the WAN by opening a webpage that is only accessible on the WAN. The server can be the same server used in the DNS lookup or another server in the WAN. Connecting using an IP address instead of a domain name should work.
75-
76-
## Double encapsulation
77-
78-
When a WARP user goes to a location (like an office) with a Magic WAN tunnel already set up, WARP traffic is doubly encapsulated - first by WARP and then by Magic WAN. This is unnecessary, since each on-ramp method provides full Zero Trust protection.
79-
80-
Since WARP traffic is already protected on its own, Cloudflare recommends that you set up Magic WAN to exclude WARP traffic, sending it to the Internet through regular connections.
81-
82-
To learn which IP addresses and UDP ports you should exclude to accomplish this, refer to [WARP ingress IP](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip) and [WARP UDP ports](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#warp-ingress-ip).
86+
Next, test with a browser that you can connect to a service on the WAN by opening a webpage that is only accessible on the WAN. The server can be the same server used in the DNS lookup or another server in the WAN. Connecting using an IP address instead of a domain name should work.
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
{}
3+
---
4+
5+
If you have Magic WAN Connector and WARP clients deployed in your premises, Magic WAN Connector automatically routes WARP traffic to the Internet rather than Magic WAN IPsec tunnels. This prevents traffic from being encapsulated twice.
6+
7+
You may need to configure your firewall to allow this new traffic. Make sure to allow the following IPs and ports:
8+
9+
- **Destination IPs**: `162.159.193.0/24`, `162.159.197.0/24`
10+
- **Destination ports**: `443`, `500`, `1701`, `2408`, `4443`, `4500`, `8095`, `844`
11+
Refer to [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/) for more information on this topic.

0 commit comments

Comments
 (0)