Skip to content

[CF1] connectivity.cloudflare.com clarification #19772

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

Closed
wants to merge 1 commit into from
Closed

[CF1] connectivity.cloudflare.com clarification #19772

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
2 changes: 2 additions & 0 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 @@ -75,6 +75,8 @@ As part of establishing the WARP connection, the client will check the following

- `connectivity.cloudflareclient.com` verifies connectivity inside of the WARP tunnel. Because this check happens inside of the tunnel, you do not need to add `connectivity.cloudflareclient.com` to your firewall allowlist.

- `connectivity.cloudflareclient.com` currently resolves to `162.159.138.65` and `162.159.137.65`. However, the WARP client does not use DNS resolution for its tunnel connectivity checks and therefore, these IP addresses do not need to be added to any firewall rules.

## NEL reporting (optional)

The WARP client reports connectivity issues to our NEL endpoint via `a.nel.cloudflare.com`. This is not technically required to operate but will result in errors in our logs if not excluded properly.
Expand Down