Warp Network Tunnel Status Validation

Zero Trust WARP
1

While configuring site-to-site connectivity with selective access to internet resources, including CF DNS, I’ve noticed that the Warp client reports successful authentication without updating Status in the CF zero trust dashboard.

Ideally, we would have a procedure for validating connectivity in stages, progressing from a proxy host with the Warp client installed, authenticated, and active, then proceeding to validate the local private network node’s access to DNS, RHEL repos, and other specified WAN resources.

Does this sounds like a reasonably generic procedure worth documenting?

3

I’ve also observed that activating the warp client prevents ssh access to private network nodes from the proxy, both for notes with tunnel entries, and for those without. The L3/L2 network +VLAN configuration appears correct prior to introducing Warp.