From 4b90c638d2bf8359340aa9176cfa3600e45e86ed Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Sat, 22 Feb 2025 02:04:06 +0000 Subject: [PATCH 1/2] Fix issue: WorkspaceTaskSubType.BROKEN_LINK --- .../partials/cloudflare-one/tunnel/warp-connector-install.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx index 0081befa3c4ba78..1be86cac83e4918 100644 --- a/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx @@ -17,9 +17,9 @@ To install WARP Connector on a host machine: :::note[Remote SSH connections] If you are managing the deployment remotely over SSH, your connection may drop when you install the WARP Connector. Because the WARP connector immediately starts forwarding traffic to Cloudflare, the remote SSH server's traffic will now route via Cloudflare instead of via the server's public IP. To work around the issue: - - **Option 1**: In your WARP Connector [device profile](#3-recommended-create-a-device-profile), temporarily add the public IP of your local machine to the [Split Tunnel Exclude list](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/). + - **Option 1**: In your WARP Connector [device profile](#3-route-cgnat-ips-through-cloudflare), temporarily add the public IP of your local machine to the [Split Tunnel Exclude list](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/). - - **Option 2**: If your local machine is connected to Zero Trust (for example, via the WARP client), you can SSH to the CGNAT IP of the WARP Connector. Traffic to the CGNAT IP must [route through the WARP tunnel](#4-configure-split-tunnels). + - **Option 2**: If your local machine is connected to Zero Trust (for example, via the WARP client), you can SSH to the CGNAT IP of the WARP Connector. Traffic to the CGNAT IP must [route through the WARP tunnel](#4-route-traffic-from-subnet-to-warp-connector). ::: 8. (Optional) Configure IP forwarding: From f9689e0b764fae65c68189fffd40f2bf753f5736 Mon Sep 17 00:00:00 2001 From: ranbel <101146722+ranbel@users.noreply.github.com> Date: Mon, 24 Feb 2025 13:20:49 -0500 Subject: [PATCH 2/2] Apply suggestions from code review --- .../partials/cloudflare-one/tunnel/warp-connector-install.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx b/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx index 1be86cac83e4918..cc384921859e1f2 100644 --- a/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx +++ b/src/content/partials/cloudflare-one/tunnel/warp-connector-install.mdx @@ -17,9 +17,9 @@ To install WARP Connector on a host machine: :::note[Remote SSH connections] If you are managing the deployment remotely over SSH, your connection may drop when you install the WARP Connector. Because the WARP connector immediately starts forwarding traffic to Cloudflare, the remote SSH server's traffic will now route via Cloudflare instead of via the server's public IP. To work around the issue: - - **Option 1**: In your WARP Connector [device profile](#3-route-cgnat-ips-through-cloudflare), temporarily add the public IP of your local machine to the [Split Tunnel Exclude list](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/). + - **Option 1**: In your WARP Connector [device profile](#2-recommended-create-a-device-profile), temporarily add the public IP of your local machine to the [Split Tunnel Exclude list](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/). - - **Option 2**: If your local machine is connected to Zero Trust (for example, via the WARP client), you can SSH to the CGNAT IP of the WARP Connector. Traffic to the CGNAT IP must [route through the WARP tunnel](#4-route-traffic-from-subnet-to-warp-connector). + - **Option 2**: If your local machine is connected to Zero Trust (for example, via the WARP client), you can SSH to the CGNAT IP of the WARP Connector. Traffic to the CGNAT IP must route through the WARP tunnel. ::: 8. (Optional) Configure IP forwarding: