correction: > (i) --proto-force is in effect : configs not matching with the forced protocol are disabled
configs --> connection entries > (ii) --http-proxy-override : UDP profiles get disabled. profiles --> connection entries On Tue, Jan 10, 2023 at 4:42 PM Selva Nair <selva.n...@gmail.com> wrote: > Hi, > > I see two situations under which a connection-entry (remote) could be > disabled while iterating through the list of remotes: > (i) --proto-force is in effect : configs not matching with the forced > protocol are disabled > (ii) --http-proxy-override : UDP profiles get disabled. > This looks like an unused option. Is it dead code no longer in use? > > Are there any other cases? > > I'm trying to get this info into the GUI for handling > "--management-query-remote". Selecting a disabled entry from the UI would > lead to erratic behaviour. Ideally this info (CE_DISABLED state) should be > included in the response to "remote-entry-get" command, but too late for > that to happen in 2.6. It didn't occur to me when that command was > implemented. > > We now have a config-parser in the GUI and can get the info from the > config file if we know for sure what conditions lead to the flag > CE_DISABLED. > > Thanks, > > Selva >
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
