Strange behavior of Managed Networks

Hi, I don’t know whether I do not understand how WARP Managed Networks work or is it some bug in the WARP client. I’ll be short in explaining.
I have 3 locations with 3 different subnets.
Location1> 192.168.1.0/24
Location2> 192.168.2.0/24
Location3> 192.168.3.0/24
I have created “beacons” on the three networks and they are detected by WARP Client. I have made profiles with expression if Managed network matches “Location1” than to include Split Tunnel routes to other 2 locations. For example if “Location1” is detected than Included split tunnel are 192.168.2.0/24 and 192.168.3.0/24
Settings are successfully applied to WARP clients but I cannot reach Location2 and 3.
If I add Split Tunnel route to specific computers on other networks eg. 192.168.2.12/32 I can connect to those specific computers.
Can someone explain why I cannot add whole subnet of other locations?

1 Like

After experimenting for a while I can conclude that current version of WARP client for Windows and Linux does not add On-Link routes to whole subnets of all managed networks you have defined. I think that managed networkS is supposed not to add route only to detected network location. It you are in Location 1 and you add those routes manually in Windows:
route add 192.168.2.0 mask 255.255.255.0 172.16.0.2
route add 192.168.3.0 mask 255.255.255.0 172.16.0.2
you can access whole subnets from 192.168.1.0 subnet and have that subnet excluded.
Cloudflare One in Android works fine. It detects managed networks and adds routes properly.

1 Like