Connect from WARP to a private network on Cloudflare using Argo Tunnel
You can create and configure Argo Tunnel connections to or . You can also use Argo Tunnel to connect any service that relies on a TCP-based protocol to Cloudflare's network. Users in your organization can then reach the service by enrolling into your organization's Cloudflare for Teams account and using the WARP agent.
Once enrolled, user endpoints will be able to connect to private IP space and other ranges that you control. Applications running on those endpoints will be able to reach those private IPs as well in a private network model. Coming soon, administrators will be able to build Zero Trust rules to determine who within your organization can reach those IPs.
🗺️ This tutorial covers how to:
- Start a secure, outbound-only, connection from a machine to Cloudflare
- Assign the machine an IP that can consist of an RFC 1918 IP address or range
- Connect to that private IP space from an enrolled WARP agent without client-side configuration changes
- Connect using any TCP-based protocol
⏲️ Time to complete:
$ brew install cloudflare/cloudflare/cloudflared
Once installed, run the following command in your Terminal to authenticate this instance of
cloudflared into your Cloudflare account.
$ cloudflared login
The command will launch a browser window and prompt you to login with your Cloudflare account. Choose a website that you have added into your account. This will authenticate your instance of
cloudflared to your Cloudflare account; you will be able to create a Tunnel for any site, not just the site selected.
Once you click one of the sites in your account, Cloudflare will download a certificate file, called
cert.pem to authenticate this instance of
cert.pem file uses a certificate to authenticate your instance of
cloudflared and includes an API key for your account to perform actions like DNS record changes.
You can now use
cloudflared to control Argo Tunnel connections in your Cloudflare account.
Create a Tunnel
cloudflared tunnel create grafana
You can confirm the ID of the Tunnel by running the following command.
cloudflared tunnel list
Next, you will need to create a route. Routes map a Tunnel ID to a CIDR range that you specify. You can use private IP space specified by or other routes. The private IP space specified should match the private IP space of your subnet or environment where Argo Tunnel will send connections.
This example tells Argo Tunnel that, for users in this organization, connections to
100.64.0.0/10 should be served by this Tunnel. For the purposes of this tutorial, Grafana is running in a Digital Ocean environment where a virtual interface has been applied that will send traffic bound for localhost to
cloudflared tunnel route ip add 100.64.0.0/10 8e343b13-a087-48ea-825f-9783931ff2a5
Similar to the
list command, you can confirm the routes enrolled with the following command.
cloudflared tunnel route ip show
Configure and run the Tunnel
Next, create a configuration file for the Tunnel. The following template contains the required fields but can be further modified as needed.
tunnel: 8e343b13-a087-48ea-825f-9783931ff2a5credentials-file: /root/.cloudflared/8e343b13-a087-48ea-825f-9783931ff2a5.jsonwarp-routing: enabled: true
You can now run the Tunnel. The command below will connect this instance of
cloudflared to Cloudflare's network. Traffic inside of your organization, from enrolled WARP agents, will be sent to this instance when the destination is this private IP range.
cloudflared tunnel run grafana
Route private IP ranges through WARP
Users can reach this private service by logging into their Cloudflare for Teams account and the WARP agent.
By default, Cloudflare WARP excludes traffic bound for RFC 1918 space and certain other routes as part of its . To use this feature the IPs that you specified for your Tunnel must be included which will send traffic for those destinations through the WARP agent and to the Tunnel.
Navigate to the
Policies page of the Gateway section in the Cloudflare for Teams dashboard. Click the Settings tab. The IP ranges listed are those that Cloudflare excludes by default. Choose the range being used for this private connection and delete it.
Connect via WARP
Once enrolled, they will be able to connect to the private IPs configured for HTTP traffic in this example or arbitrary TCP traffic.