WARP Connector Tunnel

TLDR: Replace Cloudflare Argo Tunnel with a Warp Connector tunnel. Seeking 1:1 functionality (or as close as possible). ----- Hey All, Recently I started using Cloudflare for most of my hosting needs, and discovered the Cloudflared/Argo Tunnels only support outbound traffic. I read that Cloudflare Warp allows bidirectional traffic across what is simply a glorified Wireguard connection to Cloudflare's network. I seem to be having trouble configuring this in the same way that I had an Argo tunnel operating, and am struggling to figure out why. The goal is to allow a device that I connect with Zero Trust (Laptop) to ping services/utilize services on my server through a Cloudflare Warp Tunnel. I followed the guide here: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/private-net/warp-connector/, and am able to ping the target server through Cloudflare (I can see the logs from systemd on the server, as well as the ip of the laptop sending the request). The part I am confused about is actually routing a subnet (in this case a docker user defined bridge) through a 'private network' in CF. I have the subnet created for 172.20.0.0/16, and have the routes visible on both Warp Clients, but when I try to ping the bridge gateway on the server from the laptop, the request times out. If anyone has any advice on a direction it would be greatly appreciated.