Skip to content

[CF1] WARP with firewall macOS scope update #22662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 27, 2025
Merged

[CF1] WARP with firewall macOS scope update #22662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 18 additions & 6 deletions ...nt/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,11 +52,11 @@ WARP connects to the following IP addresses, depending on which [tunnel protocol

### MASQUE

| | |
| -------------- | ---------------------------------------------------------------------------------------------- |
| IPv4 address | `162.159.197.0/24` |
| IPv6 address | `2606:4700:102::/48` |
| Default port | `UDP 443` |
| | |
| -------------- | ------------------------------------------------------------------------------------------------------------------- |
| IPv4 address | `162.159.197.0/24` |
| IPv6 address | `2606:4700:102::/48` |
| Default port | `UDP 443` |
| Fallback ports | `UDP 500` <br/> `UDP 1701` <br/> `UDP 4500` <br/> `UDP 4443` <br/> `UDP 8443` <br/> `UDP 8095` <br/> `TCP 443` [^1] |

[^1]: Required for HTTP/2 fallback
Expand Down Expand Up @@ -116,7 +116,19 @@ The WARP client attempts to synchronize the exact time by NTP (`UDP 123`) to [Cl
If your organization does not currently allow inbound/outbound communication over the IP addresses, ports, and domains described above, you must manually add an exception. The rule at a minimum needs to be scoped to the following process based on your platform:

- Windows: `C:\Program Files\Cloudflare\Cloudflare WARP\warp-svc.exe`
- macOS: `/Applications/Cloudflare WARP.app/Contents/Resources/CloudflareWARP`
- macOS: You must explicitly allow both the core networking daemon and GUI component as shown in the following instructions.

1. Core networking daemon: `/Applications/Cloudflare WARP.app/Contents/Resources/CloudflareWARP`

This binary does not have a Bundle ID and must be allowed via full path.

2. GUI component, choose one of the following three identifiers depending on your MDM or firewall vendor's preferred format:

`/Applications/Cloudflare WARP.app` (Path)

`/Applications/Cloudflare WARP.app/Contents/MacOS/Cloudflare WARP` (Path)

`com.cloudflare.1dot1dot1dot1dot1.macos` (Bundle ID)

### Optional scopes

Expand Down