Skip to content

Commit 938d546

Browse files
ranbelranbel
committed
clean up feature availability
1 parent eda0904 commit 938d546

File tree

6 files changed

+26
-25
lines changed

6 files changed

+26
-25
lines changed

‎src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname.mdx‎

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,6 @@ sidebar:
99

1010
import { Render, Details, GlossaryTooltip, Checkbox } from "~/components";
1111

12-
:::note[Availability]
13-
Hostname routes are currently available in closed beta to Enterprise customers. To request access, contact your account team.
14-
:::
15-
1612
`cloudflared` can route to HTTP and non-HTTP applications on your private network using their private hostname (for example, `wiki.internal.local`). Private hostname routes are especially useful when the application has an unknown or ephemeral IP, which often occurs when infrastructure is provisioned by a third-party cloud provider.
1713

1814
## How private hostname routing works
@@ -84,7 +80,7 @@ To connect to private hostnames, your devices must forward the following traffic
8480

8581
Configuration steps vary depending on your [device on-ramp](/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname/#device-connectivity):
8682

87-
<Details header = "WARP clients">
83+
<Details header="WARP clients">
8884
1. In [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/), ensure that the IPs listed above route through the WARP tunnel. For example, if you are using the default Split Tunnels Exclude configuration and your application and DNS resolver have private IPs in the range `10.0.0.0/8`, delete `100.64.0.0/10` and `10.0.0.0/8` from the Split Tunnels list. We recommend adding back the IPs that are not explicitly used by your network — refer to our [Split Tunnels calculator](/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-cidr/#3-route-private-network-ips-through-warp) for details.
8985
2. In [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/), delete the top-level domain for your private hostname.
9086
3. In [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/#create-a-resolver-policy), delete any existing entries that match your private hostname.

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

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,10 @@ sidebar:
99

1010
import { Render, Details, GlossaryTooltip } from "~/components";
1111

12-
:::note[Availability]
13-
Hostname routes are currently available in closed beta to Enterprise customers. To request access, contact your account team.
14-
:::
15-
16-
<Render file="gateway/egress-selector-warp-version" />
12+
<Render
13+
file="gateway/egress-selector-warp-version"
14+
product="cloudflare-one"
15+
/>
1716

1817
Cloudflare Tunnel can be used for source IP anchoring when you want to use existing egress IPs instead of purchasing [Cloudflare dedicated egress IPs](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/). Some third-party websites may have an Access Control List (ACL) that only allow connections from certain source IPs. If you already a non-Cloudflare IP on their allowlist (such an egress IP provided by an ISP or a cloud provider like AWS), you can configure `cloudflared` to anchor user traffic to the same IPs that you use today.
1918

@@ -41,9 +40,12 @@ To learn more about how Gateway applies hostname-based egress policies, refer to
4140

4241
## Prerequisites
4342

44-
- User traffic is on-ramped to Gateway using one of the following methods:
43+
User traffic is on-ramped to Gateway using one of the following methods:
4544

46-
<Render file="gateway/egress-selector-onramps" />
45+
<Render
46+
file="gateway/egress-selector-onramps"
47+
product="cloudflare-one"
48+
/>
4749

4850
## 1. Connect your private network
4951

@@ -70,13 +72,15 @@ In your WARP [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/co
7072
### Initial resolved IPs
7173

7274
When users connect to a public hostname route, Gateway will assign an <GlossaryTooltip term="initial resolved IP">initial resolved IP</GlossaryTooltip> to the DNS query from the following range:
73-
<Render file="gateway/egress-selector-cgnat-ips" />
7475

7576
The initial resolved IP is required because Gateway's network engine operates at L3/L4 and can only see IPs (not hostnames) when processing the connection. If a packet's destination IP falls within the initial resolved IP CGNAT range, Gateway knows that the IP maps to a public hostname route and sends the traffic down the corresponding Cloudflare Tunnel.
7677

7778
To route initial resolved IPs through WARP:
7879

79-
<Render file="gateway/egress-selector-split-tunnels" />
80+
<Render
81+
file="gateway/egress-selector-split-tunnels"
82+
product="cloudflare-one"
83+
/>
8084

8185
### Private network IPs
8286

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -220,11 +220,9 @@ Gateway uses Rust to evaluate regular expressions. The Rust implementation is sl
220220

221221
### Selector prerequisites
222222

223-
<Render file="gateway/egress-selector-warp-version" />
224-
225223
The [Application](#application), [Content Categories](#content-categories), [Domain](#domain), and [Host](#host) selectors are only available for traffic on-ramped to Gateway with the following methods:
226224

227-
<Render file="gateway/egress-selector-onramps" />
225+
<Render file="gateway/egress-selector-onramps" product="cloudflare-one" />
228226

229227
When you use these selectors in an egress policy for traffic from a supported on-ramp, Gateway will assign <GlossaryTooltip term="initial resolved IP">initial resolved IPs</GlossaryTooltip> to the DNS queries, then apply the correct egress IP according to the egress policy. Unsupported traffic will be resolved with your default Gateway settings. Gateway will only overwrite the DNS response when the query matches a condition in the egress policy. If you use [DNS locations](/cloudflare-one/connections/connect-devices/agentless/dns/locations/) to send a DNS query to Gateway with IPv4, IPv6, DoT, or DoH, Gateway will not return the initial resolved IP for supported traffic nor resolve unsupported traffic.
230228

@@ -268,6 +266,6 @@ Additionally, to use these selectors to filter traffic onboarded with WARP, you
268266
</array>
269267
```
270268

271-
2. <Render file="gateway/egress-selector-split-tunnels" />
269+
2. <Render file="gateway/egress-selector-split-tunnels" product="cloudflare-one" />
272270

273271
The WARP client must be set to _Gateway with WARP_ mode for traffic affected by these selectors to route correctly.

‎src/content/partials/cloudflare-one/gateway/egress-selector-onramps.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,3 +15,7 @@ import { Render, Details, GlossaryTooltip } from "~/components"
1515

1616
[^1]: Not compatible with [ECMP routing](/magic-wan/reference/traffic-steering/#equal-cost-multi-path-routing). For hostname-based routing to work, DNS queries and the resulting network traffic must reach Cloudflare over the same Magic WAN tunnel. <br/>
1717

18+
<Render
19+
file="gateway/egress-selector-warp-version"
20+
product="cloudflare-one"
21+
/>

‎src/content/partials/cloudflare-one/gateway/egress-selector-split-tunnels.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
{}
3-
43
---
4+
55
import { Tabs, TabItem, Render } from "~/components"
66

77
In your WARP [device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/), configure [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) depending on the mode:
@@ -21,5 +21,5 @@ In your WARP [device profile](/cloudflare-one/connections/connect-devices/warp/c
2121

2222
1. Add the required [Zero Trust domains](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) or [IP addresses](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-ip-addresses) to your Split Tunnel include list.
2323
2. [Add routes](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route) to include the following IP addresses:
24-
<Render file="gateway/egress-selector-cgnat-ips" />
24+
<Render file="gateway/egress-selector-cgnat-ips" product="cloudflare-one" />
2525
</TabItem> </Tabs>

‎src/content/partials/cloudflare-one/gateway/egress-selector-warp-version.mdx‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,14 @@
11
---
22
{}
3-
43
---
54

65
import { Details } from "~/components"
76

8-
<Details header="Feature availability">
7+
<Details header="WARP feature availability">
98

10-
| [WARP modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) | [Zero Trust plans](https://www.cloudflare.com/teams-pricing/) |
11-
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
12-
| Gateway with WARP | Enterprise |
9+
| [WARP modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) |
10+
| ----------------------------------------------------------------------------------------- |
11+
| Gateway with WARP |
1312

1413
| System | Availability | Minimum WARP version |
1514
| -------- | ------------ | -------------------- |

0 commit comments

Comments
 (0)