El jue, 17-06-2010 a las 17:34 +0200, Cesar Garcia escribió: > No he tenido nunca este problema, pero parece como si el problema lo > provocará la configuración del parámetro --script-security > > Esto aparece en la documentación: > > --script-security level [method] > This directive offers policy-level control over OpenVPN's > usage of external programs and scripts. Lower level values are > more restrictive, higher values are more permissive. Settings > for level: > > 0 -- Strictly no calling of external programs. > 1 -- (Default) Only call built-in executables such as > ifconfig, ip, route, or netsh. > 2 -- Allow calling of built-in executables and user-defined > scripts. > 3 -- Allow passwords to be passed to scripts via environmental > variables (potentially unsafe). > > The method parameter indicates how OpenVPN should call > external commands and scripts. Settings for method: > > execve -- (default) Use execve() function on Unix family OSes > and CreateProcess() on Windows. > system -- Use system() function (deprecated and less safe > since the external program command line is subject to shell > expansion). > > The --script-security option was introduced in OpenVPN > 2.1_rc9. For configuration file compatibility with previous > OpenVPN versions, use: --script-security 3 system > >
Efectivamente, César, ese era el problema. Al configurar el nivel a 2 me permitió correr mi scritp y creó del dispositvo tun0. Muchisimas gracias. Saludos, -- MSc. Carlos O. Cazorla Machado Administrador de Redes y Sistemas e-mail: [email protected] Linux User 379000 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1276791175.10569.20.ca...@localhost
