Hi, On Fri, Apr 27, 2018 at 12:25 PM, Leroy Tennison <leroy.tenni...@verizon.net> wrote: > Is there a way to get these messages to be sent to the log file specified in > OpenVPN's configuration file? I see a reference to the "--echo [parms...]" > configuration but there is no explanation about the definition of parms. > Thanks for any and all help.
Messages to the management starting with >CLIENT:ENV are used to pass the environment set to the management. Similar info is passed to scripts and plugins when those are used for tasks like authentication or tls-verify. These are not meant for the log file and cannot be logged. If you want to extract env variables, you have to grab them from scripts or from the management interface. ECHO: --echo "foo" will cause ">ECHO: foo" to be sent to the management interface. Although it can be used in the local config, its real purpose is to push from the server to send a string to the client's management interface. For example, the client's management i/f may be controlled by a GUI. Then echo allows the server to send a message to the GUI. The parameter "foo" is an opaque string and openvpn per se does not attach any meaning to it. Its left for the server setup and the consumer of the message (say the client-side GUI) to define them. For example, very recent versions of Windows OpenVPN-GUI interprets a few "echo directives" like "setenv x y" (to mean set OPENVPN_x = y in the environment of the scripts run by the GUI) or "forget-passwords" (to mean clear any passwords saved by the GUI) etc. There is an ongoing effort to standardize such echo directives, but not yet finalized. Selva ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
