Hey Rod,
I must have something misunderstood.
The patch reverts some of the broken changes from core update 61 and does not break anything else.
So, it someone did not touch the settings since core update 60, they won't experience any trouble. That's what I want.
Installations done with core update 61 have screwed up already.
If you both, Rod and Erik, can confirm that, I will merge the patch for core update 63.
Michael
On Thu, 2012-09-06 at 17:25 -0500, R. W. Rodolico wrote:
Ok, I did some additional tests. Note that I am talking about a change in core61 (and apparently used in thirteen also) which breaks existing installs. Forcing the optional parameter fragment to be used by the server breaks existing installs; this was what alerted me to the issue when I got a complaint from a client using OpenVPNGUI on their Windows machine.
Additionally, the default clean install of core61 has the same issue, as verfified by both myself and ummeegge, ie doing a clean install and clean config of OpenVPN results in an unworkable system until fragment is manually removed from the server.conf file.
Strongly recommend ummeegge's patch be applied to thirteen.
Everything else appears to be working well on thirteen (at least the parts I use). Going to stress test the QOS in a few minutes.
Rod
On 09/06/2012 04:34 AM, Michael Tremer wrote:
As mentioned on the forums thread, it is unacceptable that all client packages need to be re-installed. The patch cannot break any existing configuration!
Michael
On Thu, 2012-09-06 at 01:39 -0500, R. W. Rodolico wrote:
there was a bug for core61, I found a problem with OpenVPN. The discussion is at http://forum.ipfire.org/index.php/topic,6773.0.html. This problem still exists in the beta.
ummeegge created a patch that repairs the issue, and it should be put into ovpnmain.cgi. It appears, in the tests I ran, to solve the issue.
Rod _______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development