Warp Client Selects wrong Profile for Known Network
I've established a network with a beacon and created the Known Network and a Profile with specific exclusion rules.
When the warp client is disconnected
How can I tell which profile will be applied and why, when connecting the already-detected profile is ignored.
When the warp client is disconnected
warp-cli settings indicates that the correct profile is selected. When the client is connected, the profile is ignored and reverts to the default.How can I tell which profile will be applied and why, when connecting the already-detected profile is ignored.
