I’m currently testing Zero Trust in combination with the WARP client as a VPN replacment for a small business. It’s working great for the most part.
However, I’ve recently upgraded the WARP client to 2023.7.7.0 on Windows 11, and it isn’t now detecting when I’m in the office where there is a ‘beacon’ configured to signify this is a managed network. As a result the correct WARP settings profile isn’t being applied (along with some specific split tunnel exclusions).
My colleague who is testing with me is on the previous client version and is detecting the managed network correctly and therefore loading the correct split tunnel prefixes.
Could this be a case of a bug in the new client? Or is there something else I can check?
Recent versions 2023.7.* don’t seem to work with macOS either with managed network configs.
In previous versions. the daemon.log would contain:
2023-07-31T22:58:27.280Z INFO main_loop: warp::warp_service: Detected alternate network name=Some("TestNetwork")
and download the correct split tunnel config with include mode, while the new versions seems to lose connectivity (not pingable) to the IP with the managed network fingerprint server after WARP is connected. Shortly after the WARP connection, the detection failed with
2023-07-31T23:02:14.776Z INFO main_loop: warp::warp_service: Detected alternate network name=None
And proceed to download the default config in exclude mode. The local IP with the fingerprint server is not accessible until WARP is disconnected.
The latest beta doesn’t work either. With 2023.7.243.1, the local IP with the fingerprint server is still not reachable when WARP is connected. It’s will detect the network correctly again when WARP is disconnected. It has more debug logging though:
Right. The funny thing is that you can NOT report bugs (the web UI of reporting problems directs to this community) if you’re on a free plan. Considering many are evaluating these features before deciding to upgrade to a paid plan, Cloudflare should reduce the friction of direct bug reporting and give people visibility of the status of such bugs.
Still only 2023.3.450.0 works good with managed networks. I had issues described here
and I stumbled upon this this post and solved the problem. Issues were with Windows and Linux clients. On Android worked like a charm.
But still, after 6 months later CF developers can’t manage to make Managed networks to work as they should.