Related to
Cloudflare Tunnel
What is the error message?
2025-03-31T20:50:53.591Z DEBUG actor_connectivity::connectivity: Routes changed: NewNeighbour; Destination: 172.17.1.4; nnectivity::connectivity: Routes changed:
What is the issue you’re encountering
Cannot ping or connect to any routed IPs behind Warp tunnel
What steps have you taken to resolve the issue?
I have configured a new Warp tunnel in the dashboard. I have installed the cloudflare-warp package on an Azure Ubuntu VM and verified that net.ipv4.ip_forward=1. The connector is running and connected in Warp+DoH mode and the tunnel status is “Healthy” in the dashboard.
My Azure VM has a private interface in the 172.17.1.0/24 RFC1918 space. I have configured a Route for this subnet in the dashboard.
In Warp settings, Split Tunnels are activated in Exclude mode and I have verified the subnet in question is not covered by anything in the exclusion list.
In Firewall settings, Proxy is enabled for TCP, UDP, and ICMP. Warp to warp connections is enabled.
What are the steps to reproduce the issue?
I have attempted to ping and browse to any of the resouces on the routed 172.x.x.x subnet from my Warp-connected client machine. All requests time out.
I can see in the log on the Linux VM that the addresses I am attempting to reach are showing up:
2025-04-01T13:41:12.859Z DEBUG actor_connectivity::connectivity: Routes changed:
NewNeighbour; Destination: 172.17.1.4;
2025-04-01T13:41:14.640Z DEBUG actor_connectivity::connectivity: Routes changed:
NewNeighbour; Destination: 172.17.1.5;
Also, a number of packets show up as “tun_packet_unhandled” in the log summary:
2025-04-01T13:41:10.733Z DEBUG tunnel_loop{protocol=“masque” con_id=“xxx”}: warp_edge::tunnel_loop: Tunnel loop statistics stats=TunnelLoopStats { tun_packet_too_large: 0, edge_packet_too_large: 0, tun_packet_too_small: 0, edge_packet_too_small: 0, tun_packet_martian: 0, tun_packet_unhandled: 16, dropped_edge_packet: 0, dropped_tun_packet: 0, successfully_retried_tun_packet: 0 }