ping the WARP Connector LAN IP

Author: ranbel

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/site-to-site.mdx

@@ -185,7 +185,7 @@ Repeat steps 1, 3, and 4 above to install an additional WARP Connector on subnet
 
 ## 6. Test the WARP Connector
 
-You can now test the connection between the two subnets. For example, on the `10.0.0.2` device run `ping 192.168.1.100`.
+You can now test the connection between the two subnets. To test connections to the WARP Connector host, on the `10.0.0.2` device run `ping 192.168.1.97`. To connect to a device behind WARP connector, run `ping 192.168.1.100`.
 
 ```mermaid
     flowchart LR

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/user-to-site.mdx

@@ -105,7 +105,7 @@ route /p add 100.96.0.0/12 mask 255.255.255.255 <WARP-CONNECTOR-IP>
 
 ## 5. Test the WARP Connector
 
-You can now send a request from a WARP client user device to a device behind WARP connector. For example, on the WARP client device run `ping 10.0.0.2`.
+You can now send a request from a WARP client user device to your subnet. To test connections to the WARP Connector host, on the WARP client device run `ping 10.0.0.1`. To connect to a device behind WARP connector, run `ping 10.0.0.2`.
 
 ```mermaid
     flowchart LR

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

@@ -19,7 +19,7 @@ To install WARP Connector on a host machine:
     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](#2-recommended-create-a-device-profile), temporarily add the public IP of your local machine to the [Split Tunnel Exclude list](/cloudflare-one/team-and-resources/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 <GlossaryTooltip term="WARP CGNAT IP">CGNAT IP</GlossaryTooltip> of the WARP Connector. Traffic to the CGNAT IP must route through the WARP tunnel.
+    - **Option 2**: Connect your local machine to Zero Trust (for example, via the WARP client) and SSH directly to the WARP Connector's LAN IP. Traffic to this IP must route through the WARP tunnel.
     :::
 
 8. (Optional) Configure IP forwarding: