From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: openvpn broken in 13
Date: Fri, 07 Sep 2012 12:26:04 -0500 [thread overview]
Message-ID: <assp.059700e7d1.504A2E2C.7070309@dailydata.net> (raw)
In-Reply-To: <1347028907.17767.159.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2628 bytes --]
All of my tests so far have shown the patch to be effective. I agree
that it was likely a bug that crept in on the new code (would be nice to
have some effective beta testing -- oops, I'm the one that should have
done that).
Rod
On 09/07/2012 09:41 AM, Michael Tremer wrote:
> 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(a)lists.ipfire.org
>>>> http://lists.ipfire.org/mailman/listinfo/development
>>>
>>
>
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
next prev parent reply other threads:[~2012-09-07 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 6:39 R. W. Rodolico
2012-09-06 9:34 ` Michael Tremer
2012-09-06 14:16 ` R. W. Rodolico
2012-09-06 22:25 ` R. W. Rodolico
2012-09-07 14:41 ` Michael Tremer
2012-09-07 17:26 ` R. W. Rodolico [this message]
2012-09-10 8:08 ` Michael Tremer
2012-09-10 9:02 ` Erik K.
2012-09-17 19:00 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=assp.059700e7d1.504A2E2C.7070309@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox