NA
NA
NA
I have two hosts connected to cf tunnel using cloudflared. I need to be able to connect to one from the other. They are in the same local subnet in azure and can ping each other.
Follow this article: Create private networks with WARP-to-WARP
Cool, I’ll give it a shot.
I’m a bit unclear on the IP assignment aspect of this. In the warp to warp documentation it mkes reference to IPs in the CGNAT range:
Once enrolled, your users and services will be able to connect to the virtual IPs configured for TCP, UDP, or ICMP-based traffic. You can optionally create Gateway network policies to define the users and devices that can access the 100.96.0.0/12 IP space.
But when I look at a connected windows client and run ipconfig I see nothing of the sort:
Unknown adapter CloudflareWARP:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2606:4700:110:8143:cd33:688b:ad58:b070
Link-local IPv6 Address . . . . . : fe80::83b:d647:4bed:d388%25
IPv4 Address. . . . . . . . . . . : 172.16.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
I feel like I’m missing something simple and obvious to assign IPs.
If you’re trying to route through cloudflare then you need to specifically enable “Allow WARP to WARP connection” in your dashboard. That is step #3 in the guide linked above and at least with my setup caused the clients to allocate IPs in the CGNAT space.
If you don’t want to route through cloudflare then you could look at the split tunnel exclude setup and exclude the server IPs from WARP.