Connect two or more private networks

This guide covers how to connect two independent subnets with WARP Connector. Each subnet must run its own WARP Connector on a Linux host. Installing on your router is the simplest setup, but if you do not have access to the router, you may choose any other machine on the subnet.

    flowchart LR
      subgraph subnet1[Subnet 10.0.0.0/24]
      router1["WARP Connector #1
        10.0.0.1"]
      end
      subgraph subnet2[Subnet 192.168.1.0/24]
        router2["WARP Connector #2
        192.168.1.97"]
      end
      router1<-->C((Cloudflare))<-->router2

In this example, we will create a WARP Connector for subnet 10.0.0.0/24 and install it on 10.0.0.1. We will then create a second WARP Connector for subnet 192.168.1.0/24 and install it on 192.168.1.97.

Prerequisites

• A Linux host ¹ on each subnet.
• Verify that your firewall allows inbound/outbound traffic over the WARP IP addresses, ports, and domains.

1. Install a WARP Connector

To install WARP Connector on a host machine:

1. In Zero Trust ↗, go to Networks > Tunnels.

2. Select Create a tunnel.

3. For the tunnel type, select WARP Connector.

4. You will be prompted to turn on Warp to Warp and Override local interface IP if they are currently turned off. These settings allow Cloudflare to assign a unique CGNAT IP to each WARP device and route traffic between them.

5. Give the tunnel any name (for example, Subnet-10.0.0.0/24) and select Create tunnel.

6. Select the operating system of your host machine.

7. On your host machine, open a terminal window and run the commands shown in the Zero Trust dashboard. Those commands will install the WARP Connector, enable IP forwarding on the host, and connect WARP Connector to your Zero Trust organization.

   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, temporarily add the public IP of your local machine to the Split Tunnel Exclude list.

   • 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:

   Enable IP forwarding to persist after reboot

   echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-warp-svc.conf
   sudo sysctl -p /etc/sysctl.d/99-warp-svc.conf

   Configure IP forwarding with iptables

   If you are setting up WARP Connector on a host with iptables enabled, make sure that your iptables FORWARD chain includes rules to accept the desired traffic. For testing and troubleshooting purposes, you can set the default policy for the WARP interface to ACCEPT:

   iptables -A FORWARD -i CloudflareWARP -J ACCEPT
   iptables -A FORWARD -o CloudflareWARP -J ACCEPT

9. To verify that the WARP Connector is connected to Cloudflare:

   $ warp-cli status
   Status update: Connected

   Troubleshoot connection

   If WARP is disconnected, try the following troubleshooting strategies:

   • Run warp-cli connect.

   • If your private network uses a firewall to restrict Internet traffic, ensure that it allows the WARP ports and IPs.

   • Review your WARP daemon logs for information about why the connection is failing.

WARP Connector software is now installed but not yet routing traffic.

2. (Recommended) Create a device profile

A dedicated device profile 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:

1. Create a new profile that matches on the following expression:

   Selector	Operator	Value
   User email	is	warp_connector@<your-team-name>.cloudflareaccess.com

2. In the profile settings, ensure that Service mode is set to Gateway with WARP.

Note

warp_connector@<your-team-name>.cloudflareaccess.com will only match WARP Connectors deployed with WARP client version 2024.9.346.0 and above. WARP Connectors deployed using the legacy workflow will use the generic email for service token registrations (non-identity@<your-team-name>.cloudflareaccess.com).

3. Route traffic from WARP Connector to subnet

1. In Zero Trust ↗, go to Networks > Routes.
2. Select Create route.
3. In CIDR, enter the private IPv4 address range that you wish to route through this WARP Connector (for example, 10.0.0.0/24). WARP Connector does not currently support IPv6 routes.

   Note

   If you do not already have a private network range, you can choose a subnet from one of these pre-defined CIDRs ↗.

4. For Tunnel, select the name of your WARP Connector (Subnet-10.0.0.0/24).
5. Select Create.
6. In your WARP Connector device profile, configure Split Tunnels so that traffic to your private network CIDR (10.0.0.0/24) routes through the WARP tunnel. For example, if you are using Exclude mode, delete 10.0.0.0/8 from Split Tunnels and re-add the following IPs: 10.0.1.0/24, 10.0.2.0/23, 10.0.4.0/22, 10.0.8.0/21, 10.0.16.0/20, 10.0.32.0/19, 10.0.64.0/18, 10.0.128.0/17, 10.1.0.0/16, 10.2.0.0/15, 10.4.0.0/14, 10.8.0.0/13, 10.16.0.0/12, 10.32.0.0/11, 10.64.0.0/10, 10.128.0.0/9

The WARP Connector will now forward inbound requests to devices on the subnet.

    flowchart LR
      subgraph subnet1[Subnet 10.0.0.0/24]
      router1["WARP Connector #1
        10.0.0.1"]
			device["Device
        10.0.0.2"]
      end

      C((Cloudflare))--Requests to 10.0.0.2--> router1 --> device

4. Route traffic from subnet to WARP Connector

Depending on where you installed the WARP Connector, you may need to configure other devices on the subnet to route outbound requests through WARP Connector.

    flowchart LR
      subgraph subnet1[Subnet 10.0.0.0/24]
      router1["WARP Connector #1
        10.0.0.1"]
			device["Device
        10.0.0.2"]
      end

      device --Requests to
			192.168.1.0/24 --> router1 --> C((Cloudflare))

Option 1: Default gateway

If you installed WARP Connector on your router, no additional configuration is necessary. All traffic will use the router as the default gateway.

Option 2: Alternate gateway

If you have access to the router but installed WARP Connector on another machine, you can configure the router to forward traffic to the WARP Connector. This typically involves adding a static route for the destination IPs that you want to connect to through Cloudflare. Refer to your router documentation for specific instructions on how to add an IP route.

Add route to router

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).

When a device on the subnet sends a request, the router will first redirect the traffic to the WARP Connector host. WARP Connector encrypts the traffic, changes its destination IP to the WARP ingress IP, and sends it back to the router. The router will now forward this encrypted traffic to Cloudflare.

Note

Ensure that your routing rules do not forward the WARP ingress IP back to the WARP Connector.

Option 3: Intermediate gateway

If you do not have access to the router, you will need to configure each device on the subnet to egress through the WARP Connector machine instead of the default gateway.

Add route to devices

You can configure all traffic on a device to egress through WARP Connector with its local source IP. All traffic will be filtered by your Gateway network policies.

Linux

sudo ip route add default via <WARP-CONNECTOR-IP> dev eth0 metric 101

Ensure that the metric value is lower than other default gateways.

macOS

sudo route -n change default <WARP-CONNECTOR-IP> -interface en0

Windows

route /p add 0.0.0.0 mask 0.0.0.0 <WARP-CONNECTOR-IP> metric 101

Ensure that the metric value is lower than other default gateways.

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.

Linux

sudo ip route add <DESTINATION-IP> via <WARP-CONNECTOR-IP> dev eth0

macOS

sudo route -n add -net <DESTINATION-IP> <WARP-CONNECTOR-IP>

Windows

route /p add <DESTINATION-IP> mask 255.255.255.255 <WARP-CONNECTOR-IP>

Verify routes

To validate subnet routing, check your routing table and ensure that traffic is routing through the CloudflareWARP virtual interface.

5. Install another WARP Connector

Repeat steps 1, 3, and 4 above to install an additional WARP Connector on subnet 192.168.1.0/24. The device profile created in Step 2 will apply to all WARP Connectors.

    flowchart LR
      subgraph subnet1[Subnet 10.0.0.0/24]
      router1["WARP Connector #1
        10.0.0.1"]
      end
      subgraph subnet2[Subnet 192.168.1.0/24]
        router2["WARP Connector #2
        192.168.1.97"]
      end
      router1<-->C((Cloudflare))<-->router2

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.

    flowchart LR
      subgraph subnet1[Subnet 10.0.0.0/24]
        device1["Device
        10.0.0.2"]--"ping
        192.168.1.100"-->router1["WARP Connector #1
        10.0.0.1"]
      end
      subgraph subnet2[Subnet 192.168.1.0/24]
        router2["WARP Connector #2
        192.168.1.97"]-->device2["Device
        192.168.1.100"]
      end
      router1-->C((Cloudflare))-->router2

Note

If you are testing with curl using private hostnames, add the --ipv4 flag to your curl commands.

Footnotes

1. Check the system requirements. Package dependencies are the following: curl, gpg, iptables, iptables-persistent, lsb-core, and sudo.

   ↩

Was this helpful?

What did you like?

Accurate

Easy to understand

Solved my problem

Helped me decide to use the product

Other

What went wrong?

Hard to understand

Incorrect information

Missing the information

Other

Thank you for helping improve Cloudflare's documentation!