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
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.1 Reply
Somehow I've been able to get this to work for my test network. But I have no idea what I did.
And now it's not working again. When the warp client is disconnected, the settings show the correct known network profile. When I connect it reverts to the default profile.
SIGH Silly me. Profiles, known networks are beta. and from the community and discussion it's non-functional beta on all platforms except maybe windows. Nevermind.