Skip to content

Commit 545b0dd

Browse files
committed
remove DoH IPs from learning path
1 parent fc2e10e commit 545b0dd

File tree

3 files changed

+12
-21
lines changed

3 files changed

+12
-21
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,8 @@ The WARP client connects to Cloudflare via a standard HTTPS connection outside t
1919

2020
All DNS requests through WARP are sent outside the tunnel via DoH (DNS over HTTPS). In your organization's firewall, you must allow the following host: `<ACCOUNT_ID>.cloudflare-gateway.com`. WARP will connect to the following IPs, which must be reachable for DNS to work correctly.
2121

22-
<Render file="warp/doh-ips" />
22+
- IPv4 DoH Addresses: `162.159.36.1` and `162.159.46.1`
23+
- IPv6 DoH Addresses: `2606:4700:4700::1111` and `2606:4700:4700::1001`
2324

2425
### Android devices
2526

src/content/partials/cloudflare-one/warp/doh-ips.mdx

Lines changed: 0 additions & 7 deletions
This file was deleted.

src/content/partials/learning-paths/zero-trust/install-agent.mdx

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,26 +10,23 @@ Most admins test by manually downloading the WARP client and enrolling in your o
1010
## Install WARP
1111

1212
1. First, uninstall any existing third-party VPN software if possible. Sometimes products placed in a disconnected or disabled state will still interfere with the WARP client.
13-
2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to these IP addresses:
14-
* Client orchestration IPs: <Render file="warp/client-orchestration-ips" product="cloudflare-one" />
15-
* Gateway DoH IPs: <Render file="warp/doh-ips" product="cloudflare-one" />
16-
For more information, refer to [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/).
17-
3. Manually install WARP on the device.
18-
13+
2. If you are running third-party firewall or TLS decryption software, verify that it does not inspect or block traffic to the WARP client orchestration IPs:
14+
<Render file="warp/client-orchestration-ips" product="cloudflare-one" />
1915

20-
<Details header="Window, macOS, and Linux">
21-
22-
<Render file="warp/enroll-desktop" product="cloudflare-one" />
16+
For more information, refer to [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/).
2317

18+
3. Manually install WARP on the device.
2419

25-
</Details>
20+
<Details header="Window, macOS, and Linux">
2621

22+
<Render file="warp/enroll-desktop" product="cloudflare-one" />
2723

28-
<Details header="iOS, Android, and ChromeOS">
24+
</Details>
2925

30-
<Render file="warp/enroll-ios-android" product="cloudflare-one" />
26+
<Details header="iOS, Android, and ChromeOS">
3127

28+
<Render file="warp/enroll-ios-android" product="cloudflare-one" />
3229

33-
</Details>
30+
</Details>
3431

3532
The WARP client should show as **Connected**. {props.one}

0 commit comments

Comments
 (0)