Skip to content

Commit 4894651

Browse files
ranbelranbel
committed
apply review feedback
1 parent e1b5be0 commit 4894651

File tree

5 files changed

+28
-31
lines changed

5 files changed

+28
-31
lines changed

‎src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector/site-to-internet.mdx‎

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,16 +13,13 @@ This guide covers how to connect a private network to the Internet using WARP Co
1313
```mermaid
1414
flowchart LR
1515
subgraph subnet1[Subnet 10.0.0.0/24]
16-
router1["WARP Connector
16+
device1["Device
17+
10.0.0.2"]-->router1["WARP Connector
1718
10.0.0.1"]
1819
end
1920
router1-->C((Cloudflare))-->I{Internet}
2021
```
2122

22-
:::note
23-
To connect a private network using `cloudflared`, refer to [Connect private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/).
24-
:::
25-
2623
## Prerequisites
2724

2825
- A Linux host [^1] on the subnet
@@ -48,7 +45,7 @@ Depending on where you installed the WARP Connector, you may need to configure o
4845

4946
<Render file="tunnel/warp-connector-alternate-gateway" />
5047

51-
#### Route from subnet to Internet
48+
#### Add route to router
5249

5350
For example, for all traffic from the subnet to egress through WARP Connector, add a rule on the router that routes `0.0.0.0` to the WARP Connector host machine (`10.0.0.100`).
5451

@@ -58,7 +55,7 @@ For example, for all traffic from the subnet to egress through WARP Connector, a
5855

5956
<Render file="tunnel/warp-connector-intermediate-gateway" />
6057

61-
#### Route all traffic
58+
#### Add route to devices
6259

6360
<Render file="tunnel/warp-connector-route-all-traffic" />
6461

‎src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector/site-to-site.mdx‎

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ Depending on where you installed the WARP Connector, you may need to configure o
9191

9292
<Render file="tunnel/warp-connector-alternate-gateway" />
9393

94-
#### Route from subnet to subnet
94+
#### Add route to router
9595

9696
For example, for devices on subnet `10.0.0.0/24` to reach applications behind subnet `192.168.1.0/24`, add a rule on the router that routes `192.168.1.0/24` to the WARP Connector host machine (`10.0.0.100`).
9797

@@ -101,13 +101,11 @@ For example, for devices on subnet `10.0.0.0/24` to reach applications behind su
101101

102102
<Render file="tunnel/warp-connector-intermediate-gateway" />
103103

104-
#### Route all traffic
104+
#### Add route to devices
105105

106106
<Render file="tunnel/warp-connector-route-all-traffic" />
107107

108-
#### Route specific IPs
109-
110-
You can configure only certain routes to egress through WARP Connector. For example, you may only want to filter traffic destined to internal applications and devices, but allow public Internet traffic to bypass Cloudflare.
108+
Alternatively, you can configure only certain routes to egress through WARP Connector. For example, you may only want to filter traffic destined to internal applications and devices, but allow public Internet traffic to bypass Cloudflare.
111109

112110
<Tabs> <TabItem label="Linux">
113111

‎src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-connector/user-to-site.mdx‎

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,16 +13,15 @@ This guide covers how to connect WARP client user devices to a private network b
1313
```mermaid
1414
flowchart LR
1515
subgraph subnet1[Subnet 10.0.0.0/24]
16+
router1["WARP Connector
17+
10.0.0.1"]--> device1["Device
18+
10.0.0.2"]
1619
router1["WARP Connector
1720
10.0.0.1"]
1821
end
1922
W[WARP clients]-->C((Cloudflare))-->router1
2023
```
2124

22-
:::note
23-
To connect a private network using `cloudflared`, refer to [Connect private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/).
24-
:::
25-
2625
## Prerequisites
2726

2827
- A Linux host [^1] on the subnet
@@ -40,8 +39,9 @@ To connect a private network using `cloudflared`, refer to [Connect private netw
4039

4140
WARP clients and WARP Connectors are accessed using their <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip>. Therefore, CGNAT IP traffic must route through Cloudflare on both the WARP Connector host and WARP client devices.
4241

43-
1. In your WARP Connector device profile, delete `100.96.0.0/12` from the [Split Tunnel Exclude list](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) (or add it to the Split Tunnel Include list).
44-
2. Repeat the previous step for all WARP client device profiles.
42+
1. In your WARP Connector device profile, go to [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/).
43+
2. Ensure that `100.96.0.0/12` routes through the WARP tunnel. For example, if you are using **Exclude** mode, delete `100.64.0.0/10` from the list and re-add `100.64.0.0/11` and `100.112.0.0/12`.
44+
3. Repeat the previous steps for all WARP client device profiles.
4545

4646
## 4. Route traffic from subnet to WARP Connector
4747

@@ -55,7 +55,7 @@ Depending on where you installed the WARP Connector, you may need to configure o
5555

5656
<Render file="tunnel/warp-connector-alternate-gateway" />
5757

58-
#### Route from subnet to WARP clients
58+
#### Add route to router
5959

6060
`100.96.0.0/12` is the default CIDR for all user devices running the [WARP client](/cloudflare-one/connections/connect-devices/warp/). On your router, add a rule that routes the destination IP `100.96.0.0/12` to the WARP Connector host machine (`10.0.0.100`).
6161

@@ -65,7 +65,7 @@ Depending on where you installed the WARP Connector, you may need to configure o
6565

6666
<Render file="tunnel/warp-connector-intermediate-gateway" />
6767

68-
#### Route CGNAT IPs
68+
#### Add route to devices
6969

7070
To route all <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> traffic through WARP Connector:
7171

@@ -105,12 +105,13 @@ You can now send a request from a device behind WARP Connector to a WARP client
105105
```mermaid
106106
flowchart LR
107107
subgraph subnet1[Subnet 10.0.0.0/24]
108-
device1["Device
109-
10.0.0.2"]--ping 100.96.0.21-->router1["WARP Connector
108+
router1["WARP Connector
109+
10.0.0.1"]--> device1["Device
110+
10.0.0.2"]
111+
router1["WARP Connector
110112
10.0.0.1"]
111113
end
112-
router1-->C((Cloudflare))-->W["WARP client
113-
100.96.0.21"]
114+
W[WARP client]--ping 10.0.0.2 -->C((Cloudflare))-->router1
114115
```
115116

116117
[^1]: <Render file="tunnel/warp-connector-linux-packages" />

‎src/content/partials/cloudflare-one/tunnel/warp-connector-device-profile.mdx‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@
22
{}
33
---
44

5-
A dedicated [device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/) allows you to manage the WARP Connector host machine separately from WARP client user devices.
5+
A dedicated [device profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/) allows you to manage the WARP Connector host machine separately from WARP client user devices. WARP Connector hosts are registered to your Zero Trust organization with the email address `warp_connector@<your-team-name>.cloudflareaccess.com`. To set up a device profile for WARP Connector:
66

7-
WARP Connector hosts are registered to your Zero Trust organization with the email address `warp_connector@<your-team-name>.cloudflareaccess.com`. To set up a device profile for WARP Connector, [create a new profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/#create-a-new-profile) that matches on the following expression:
7+
1. [Create a new profile](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/#create-a-new-profile) that matches on the following expression:
88

9-
| Selector | Operator | Value |
10-
| -------- | -------- | ----- |
11-
| User email | is | `warp_connector@<your-team-name>.cloudflareaccess.com` |
9+
| Selector | Operator | Value |
10+
| -------- | -------- | ----- |
11+
| User email | is | `warp_connector@<your-team-name>.cloudflareaccess.com` |
12+
13+
2. In the profile settings, ensure that **Service mode** is set to **Gateway with WARP**.

‎src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ import { Details, GlossaryTooltip } from "~/components";
66

77
To install WARP Connector on a host machine:
88

9-
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Network** > **Tunnels**.
9+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Networks** > **Tunnels**.
1010
2. Select **Create a tunnel**.
1111
3. For the tunnel type, select **WARP Connector**.
1212
4. You will be prompted to turn on **Warp to Warp** and [**Override local interface IP**](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#override-local-interface-ip) if they are currently turned off. These settings allow Cloudflare to assign a unique <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> to each WARP device and route traffic between them.
@@ -44,7 +44,6 @@ To install WARP Connector on a host machine:
4444
```sh
4545
$ warp-cli status
4646
Status update: Connected
47-
Success
4847
```
4948

5049
<Details header="Troubleshoot connection">

0 commit comments

Comments
 (0)