Skip to content

[ZT] Clarify ICMP proxy functionality #27480

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
nikitacano merged 1 commit into from
Jan 8, 2026
Merged

[ZT] Clarify ICMP proxy functionality #27480

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: 1 addition & 1 deletion src/content/docs/cloudflare-one/traffic-policies/proxy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ For HTTP/3 traffic to be logged and filtered, you need to turn on both TLS decry

### ICMP <Badge text="Beta" variant="caution" size="small" />

The ICMP proxy forwards traffic for diagnostic tools such as `ping` and `traceroute`.
The ICMP proxy allows IMCP traffic to reach your private network through Gateway. For example, this would allow a WARP user to run diagnostic commands such as `ping` and `traceroute` to an internal server IP.

:::caution[Limitation]
Gateway cannot log or filter ICMP traffic.
Expand Down