Connect private networks
Creating a private network has two components: the server and the client. The server’s infrastructure (whether that is a single application, multiple applications, or a network segment) is connected to Cloudflare’s edge by Cloudflare Tunnel. This is done by running the
cloudflared daemon on the server. Simply put, Cloudflare Tunnel is what connects your network to Cloudflare. On the client side, end users connect to Cloudflare’s edge using the Cloudflare WARP agent. This agent can be rolled out to your entire organization in just a few minutes using your in-house MDM tooling.
- on your devices in Gateway with WARP mode. The Cloudflare certificate is only required if you want to display a custom block page or filter HTTPS traffic.
- to determine which devices can enroll to your Zero Trust organization.
1. Connect the server to Cloudflare
To connect your infrastructure with Cloudflare Tunnel:
In the Private Networks tab for the tunnel, enter the IP/CIDR range of your private network (for example
10.0.0.0/8). This makes the WARP client aware that any requests to this IP range need to be routed to your new tunnel.
2. (Recommended) Filter network traffic with Gateway
By default, all WARP devices enrolled in your Zero Trust organization can connect to your private network through Tunnel. You can configure Gateway to inspect your network traffic and either block or allow access based on user identity.
Enable the Gateway proxy
- In the Zero Trust dashboard, go to Settings > Network.
- Enable Proxy for TCP.
Route private network IPs through Gateway
By default, WARP automatically excludes some IP addresses from Gateway visibility as part of its . For example, WARP automatically excludes RFC 1918 IP addresses such as
10.0.0.0/8, which are IP addresses typically used in private networks and not reachable from the Internet. You will need to make sure that traffic to the IP/CIDR you are associating with your private network are sent to Gateway for filtering.
To configure Split Tunnels settings:
- Check whether your is set to Exclude or Include mode.
- If you are using Exclude mode, the IP ranges you see listed are those that Cloudflare excludes from WARP encryption. If your network’s IP/CIDR range is listed on this page, delete it.
- If you are using Include mode, the IP ranges you see listed are the only ones Cloudflare is encrypting through WARP. Add your network’s IP/CIDR range to the list.
Create Zero Trust policies
You can create Zero Trust policies to manage access to specific applications on your network.
Go to Access > Applications > Add an application.
Select Private Network.
Name your application.
For Application type, select Destination IP.
For Value, enter the IP address for your application (for example,
Select Next. You will see two auto-generated Gateway Network policies: one that allows access to the destination IP and another that blocks access.
Modify the policies to include additional identity-based conditions. For example:
Action Selector Operator Value Allow Destination IP in
User email Matches regex
Block Selector Operator Value Block Destination IP in
Access rules are evaluated in order, so a user with an email ending in @example.com will be able to access
10.128.0.7while all others will be blocked. For more information on building network policies, refer to our .
Select Add application.
Your application will appear on the Applications page.
3. Connect as a user
End users can now reach HTTP or TCP-based services on your network by navigating to any IP address in the range you have specified.
To check that their device is properly configured, the user can visit
https://help.teams.cloudflare.com/ to ensure that:
- The page returns Your network is fully protected.
- In HTTP filtering, both WARP and Gateway Proxy are enabled.
- The Team name matches the Zero Trust organization from which you created the tunnel.
Check the local IP address of the device and ensure that it does not fall within the IP/CIDR range of your private network. For example, some home routers will make DHCP assignments in the
10.0.0.0/24 range, which overlaps with the
10.0.0.0/8 range used by most corporate private networks. When a user’s home network shares the same IP addresses as the routes in your tunnel, their device will be unable to connect to your application.
To resolve the IP conflict, you can either:
Reconfigure the user’s router to use a non-overlapping IP range. Compatible routers typically use
Tighten the IP range in your tunnel configuration to exclude the
10.0.0.0/24range. This will only work if your private network does not have any hosts within