Hi Carlo, >> Did you know the Fonera comes shipped with the openvpn binaries as well? > I was thinking it was only for openvpn server... my mistake. It supports both. The client support can be disabled, but I'm leaving it enabled on purpose to allow people to experiment with stuff like this ;-)
> I will upgrade to 2.3.7 when it will be in a stable version ;-) Ok, makes sense. > I see nothing in the /tmp/openvpn-debub file, because I've already > redirected output in the /tmp/openvpn-log file I was thinking that OpenVPN was perhaps throwing some error before it got a chance to setup the log output file (since the openvpn-debug redirect is handled by the shell just before starting openvpn, it should always work). But if there is no output in there, openvpn is probablly not outputting anything. > But this was a good hint because I saw that the log were truncated... the > VPN connection started and then, in the negotiation phase, ended without > terminate the full process. Which log was truncated? How can you tell? What error did you see, then? > I just added two "forced delay" in the script and now the VPN starts at > boot. OK, I know this isn't' a "clean way" to solve the problem, but for > now is enough. Hmm, I don't think I understand exactly how these delays help here. AFAIK the boot is not performed in parallel, so while this script is sleeping, there is no other stuff running in the background which would cause openvpn to work after those 15 seconds (though I'm not completely sure). > I will wait the stable new firmware (BTW: when?) to apply a clean > solution (as Jon "The Nice Guy" Spriggs suggested in the previous > e-mail). I expect the stable firmware to be released by the end of this year. Gr. Matthijs
signature.asc
Description: Digital signature
_______________________________________________ Development mailing list [email protected] http://fonosfera.org/mailman/listinfo/development
