Implemented detection of OpenVPN tunnel device type

This will later be used to be able to support OpenVPN in tun mode
as well as the now only supported tap mode.  It will first try to
detect the tunnel type based on the 'dev_type' environment variable
if available.  If not, it will try to figure it out based on the
device name.  If this fails, it is possible to force the eurephia
to a specific device type by setting the openvpn_devtype config
variable.

Signed-off-by: David Sommerseth <dazo@users.sourceforge.net>

1 files changed, 4 insertions, 0 deletions

diff --git a/man/eurephia-variables.7 b/man/eurephia-variables.7
index 6505a45..967c761 100644
--- a/man/eurephia-variables.7
+++ b/man/eurephia-variables.7
@@ -52,6 +52,10 @@ This defines how long a eurephia administration utility may have an open session
 .TP
 .B eurephiadm_xslt_path
 The \fBeurephiadm\fR utility uses XSLT templates for generating the output to the screen.  This variable gives you the possibility to have your own set of templates in a different directory instead of using the system wide XSLT templates installed by default.  This variable is not set by default.
+.SH "OPENVPN RELATED VARIABLES"
+.TP
+.B openvpn_devtype
+The \fBeurephia-auth\fR plug-in will try to auto-detect the device type, which must be either tun or tap.  If this auto-detection fails, this configuration variable needs to be set to \fBtun\fR or \fBtap\fR.  This value must correspond to the OpenVPN configuration.
 .SH "SEE ALSO"
 \fBeurephiadm\-config\fR(7),
 \fBeurephia_init\fR(7),