|
| 1 | +--- |
| 2 | +pcx_content_type: reference |
| 3 | +title: Tips and best practices |
| 4 | +sidebar: |
| 5 | + label: Tips and best practices |
| 6 | + order: 4 |
| 7 | +--- |
| 8 | + |
| 9 | +## VPC deployments |
| 10 | + |
| 11 | +When setting up WARP Connector on a virtual private cloud (VPC), you may need to configure additional settings in the cloud service provider. |
| 12 | + |
| 13 | +### GCP |
| 14 | + |
| 15 | +For Google Cloud Project (GCP) deployments, [enable IP forwarding](https://cloud.google.com/vpc/docs/using-routes#canipforward) on the VM instance where you installed WARP Connector. |
| 16 | + |
| 17 | +### AWS |
| 18 | + |
| 19 | +For Amazon Web Services (AWS) deployments: |
| 20 | +- Stop [source/destination checking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html) on the EC2 instance where you installed WARP Connector. |
| 21 | +- In your [subnet route table](https://docs.aws.amazon.com/vpc/latest/userguide/subnet-route-tables.html), route all IPv4 traffic to the EC2 instance where you installed WARP Connector. For example: |
| 22 | + |
| 23 | + | Destination | Target | |
| 24 | + | ----------- | ------ | |
| 25 | + | `0.0.0.0/0` | `eni-11223344556677889` | |
| 26 | + |
| 27 | +## WARP Connector with cloudflared |
| 28 | + |
| 29 | +WARP Connector and [`cloudflared`](/cloudflare-one/connections/connect-networks/private-net/cloudflared/) can run together on the same Linux host. This configuration is useful when you want to use WARP Connector as a gateway for your private network, while also using the `cloudflared` daemon to expose specific applications. |
| 30 | + |
| 31 | +By design, WARP Connector captures all outbound traffic and routes it through Cloudflare's network. This prevents `cloudflared` from making its own [required outbound connections](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-with-firewall/#required-for-tunnel-operation) to Cloudflare, causing the tunnel to fail with connection timeouts. |
| 32 | + |
| 33 | +To allow `cloudflared` to connect, use [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) to explicitly exclude the [Cloudflare Tunnel destinations](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-with-firewall/) from the WARP tunnel. For example, if you are using Split Tunnels in **Exclude** mode, add the following hostnames (or their corresponding IP ranges) to your Split Tunnel exclusion list: |
| 34 | + - `region1.v2.argotunnel.com` |
| 35 | + - `region2.v2.argotunnel.com` |
| 36 | + |
| 37 | +:::note |
| 38 | +Split Tunnels is the only supported method of running both connectors on one machine. Due to its low-level integration with the kernel networking stack, WARP Connector will override any routing configurations made by commands such as `ip route add` and `iptables`. |
| 39 | +::: |
| 40 | + |
| 41 | + |
| 42 | + |
0 commit comments