I have defined a known network and a profile for that network. It is enabled and it is the first profile entry in the list. The computer connecting is a Macbook running Ventura.
Warp cli version: 2023.7.159.0
When I disconnect with warp-cli, and check the settings the network profile displayed is the correct one for the known network. [1] When I connect the warp client to the ZT network, a different profile is applied. [2] The beacon is on one of the two excluded networks for the known network profile.
Is there a way to see, from the client, which profile is in force and why that profile was selected? Is there a way to check connection/selection activity from the web dashboard?
[1] Disconnected
markllama:~ mark$ warp-cli disconnect
Success
markllama:~ mark$ warp-cli settings
Merged configuration:
(derived) Always On: false
(network policy) Switch Locked: false
(network policy) Mode: WarpWithDnsOverHttps
(default) Disabled for Wifi: false
(default) Disabled for Ethernet: false
(reg defaults) Resolve via: 3a9aa959ebf84a4674c0ea9624a4b255.cloudflare-gateway.com @ [162.159.36.1, 2606:4700:4700::1111]
(default) Onboarding: true
(network policy) Exclude mode, with hosts/ips:
192.168.1.0/24 (A home network in RFC1918)
192.168.2.0/24 (A home network in RFC1918)
...
[2] Connected
markllama:~ mark$ warp-cli connect
Success
markllama:~ mark$ warp-cli settings
Merged configuration:
(derived) Always On: true
(network policy) Switch Locked: false
(network policy) Mode: WarpWithDnsOverHttps
(default) Disabled for Wifi: false
(default) Disabled for Ethernet: false
(reg defaults) Resolve via: 3a9aa959ebf84a4674c0ea9624a4b255.cloudflare-gateway.com @ [162.159.36.1, 2606:4700:4700::1111]
(default) Onboarding: true
(network policy) Exclude mode, with hosts/ips:
mycompany.somewhere.com (somewhere is whitelisted by source IP)
...