Skip to content

Commit 2ba4209

Browse files
[CF1] split tunnel ip addresses (#21032)
1 parent 1b16861 commit 2ba4209

File tree

1 file changed

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

1 file changed

+7
-0
lines changed

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

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,13 @@ Many Cloudflare Zero Trust services rely on traffic going through WARP, such as
4747
- The application protected by the Access or Gateway policy
4848
- `edge.browser.run` if using [Browser Isolation](/cloudflare-one/policies/browser-isolation/)
4949

50+
## Cloudflare Zero Trust IP addresses
51+
52+
In [Secure Web Gateway without DNS filtering](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/#secure-web-gateway-without-dns-filtering) WARP mode, you cannot [add domains](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) to the Split Tunnel. If you are using Split Tunnels in Include mode, you must include the IPs that resolve to `<your-team-name>.cloudflareaccess.com` instead:
53+
54+
- `104.19.194.29`
55+
- `104.19.195.29`
56+
5057
## Domain-based Split Tunnels
5158

5259
Domain-based split tunneling has a few ramifications you should be aware of before deploying in your organization:.

0 commit comments

Comments
 (0)