Skip to content

Commit d0de2f7

Browse files
[CF1] warp egress ip note (#19450)
* [CF1] warp egress up note * final edit * Apply suggestions from code review * Update src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx Co-authored-by: ranbel <[email protected]> --------- Co-authored-by: ranbel <[email protected]>
1 parent e76d68d commit d0de2f7

File tree

1 file changed

+2
-0
lines changed
  • src/content/docs/cloudflare-one/policies/gateway/egress-policies

1 file changed

+2
-0
lines changed

src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ When your users connect to the Internet through Cloudflare Gateway, by default t
1616

1717
Egress policies allow you to control which dedicated egress IP is used and when, based on attributes such as identity, IP address, and geolocation. Traffic that does not match an egress policy will default to using the most performant dedicated egress IP.
1818

19+
Cloudflare does not publish WARP egress IP ranges. WARP egress IPs are not documented at [Cloudflare's IP Ranges](https://cloudflare.com/ips). To obtain a dedicated WARP egress IP, contact your account team.
20+
1921
## Force IP version
2022

2123
To control whether only IPv4 or IPv6 is used to egress, ensure you are [filtering DNS traffic](/cloudflare-one/policies/gateway/initial-setup/dns/), then create a DNS policy to [block AAAA or A records](/cloudflare-one/policies/gateway/dns-policies/common-policies/#control-ip-version).

0 commit comments

Comments
 (0)