From 9211b9bdb51b9137fd1d6828a75cd6c0361ee9a2 Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Mon, 27 Jan 2025 14:42:47 +0000 Subject: [PATCH 1/4] [CF1] warp egress up note --- .../cloudflare-one/policies/gateway/egress-policies/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx index c67a7317731f6c7..56a11308aeee27d 100644 --- a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx +++ b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx @@ -16,6 +16,8 @@ When your users connect to the Internet through Cloudflare Gateway, by default t 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. +Cloudflare does not publish egress IP ranges publicly. To obtain an egress IP, request this feature from your CSM. + ## Force IP version 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). From b5eb7eac4f96e6afb0dcf5936b2edcfb89b14278 Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Mon, 27 Jan 2025 14:47:26 +0000 Subject: [PATCH 2/4] final edit --- .../cloudflare-one/policies/gateway/egress-policies/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx index 56a11308aeee27d..4658f44a1290795 100644 --- a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx +++ b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx @@ -16,7 +16,7 @@ When your users connect to the Internet through Cloudflare Gateway, by default t 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. -Cloudflare does not publish egress IP ranges publicly. To obtain an egress IP, request this feature from your CSM. +Cloudflare does not and will not publish WARP egress IP ranges publicly. WARP egress IPs are not documented at [Cloudflare's IP Ranges](https://cloudflare.com/ips). To obtain an egress IP, contact your CSM. ## Force IP version From 321c3734424bc7193dae55af33a34475f8a94376 Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Mon, 27 Jan 2025 15:32:31 +0000 Subject: [PATCH 3/4] Apply suggestions from code review --- .../cloudflare-one/policies/gateway/egress-policies/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx index 4658f44a1290795..9e55b7b97d63e3d 100644 --- a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx +++ b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx @@ -16,7 +16,7 @@ When your users connect to the Internet through Cloudflare Gateway, by default t 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. -Cloudflare does not and will not publish WARP egress IP ranges publicly. WARP egress IPs are not documented at [Cloudflare's IP Ranges](https://cloudflare.com/ips). To obtain an egress IP, contact your CSM. +Cloudflare does not and will not publish WARP egress IP ranges publicly. WARP egress IPs are not documented at [Cloudflare's IP Ranges](https://cloudflare.com/ips). To obtain a dedicated WARP egress IP, contact your CSM. ## Force IP version From 3f511065efc7e234917b9f8437a5ecf4dbee8d44 Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Tue, 28 Jan 2025 11:44:51 +0000 Subject: [PATCH 4/4] Update src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx Co-authored-by: ranbel <101146722+ranbel@users.noreply.github.com> --- .../cloudflare-one/policies/gateway/egress-policies/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx index 9e55b7b97d63e3d..e1074b01a0df810 100644 --- a/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx +++ b/src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx @@ -16,7 +16,7 @@ When your users connect to the Internet through Cloudflare Gateway, by default t 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. -Cloudflare does not and will not publish WARP egress IP ranges publicly. WARP egress IPs are not documented at [Cloudflare's IP Ranges](https://cloudflare.com/ips). To obtain a dedicated WARP egress IP, contact your CSM. +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. ## Force IP version