Description
Existing documentation URL(s)
What changes are you suggesting?
The purpose and behaviour of the 'WARP mode required' for device profile selectors needs to be clarified since as the moment it is not clear what they do.
For example, the User email selector 'requires' that WARP is running in 'Gateway with WARP' mode, but what does this actually mean?
Does this mean that the WARP client will refuse to put the client in any other mode if this selector is used? Or does it mean that the WARP client must already be in this mode in order to evaluate the selector and switch profile?
Could the User email selector be used to switch the WARP client into a different mode, e.g. DoH-only mode, and have it get stuck there because it will no-longer be able to evaluate the selector to switch back?
What is the impact of having multiple profiles, some of which use selectors which require 'Gateway with WARP', and some which don't?
Additional information
No response