Re: OpenVPN no more --client-(dis)connect scripts can be executed

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3609 bytes --]

Hello,

That reads awful.

Can we please create individual tickets for the individual problems and assign someone to work on those (I assume that would be you Erik :D).

We need to coordinate this and future-proof OpenVPN as best as we can, but it looks like we will break client configuration - again.

If we have to do that and there is no way to avoid it, we need to make our users aware of that of course and give the enough time to prepare for this.

I cannot even say how annoying this is - again. But we must try our best.

-Michael

> On 7 Oct 2020, at 11:37, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Am Mittwoch, den 07.10.2020, 10:22 +0100 schrieb Michael Tremer:
>> Hi,
>> 
>>> On 7 Oct 2020, at 10:21, ummeegge <ummeegge(a)ipfire.org> wrote:
>>> 
>>> Hi Michael,
>>> 
>>> Am Mittwoch, den 07.10.2020, 09:20 +0100 schrieb Michael Tremer:
>>>> Hi,
>>>> 
>>>> Oh so this is a custom thing?
>>>> 
>>>> Obviously most users won’t use this. If you care much about your
>>>> custom script, you can write a script that searches a directory
>>>> and
>>>> calls all scripts in it (like /etc/init.d/networking/red.up/ and
>>>> /etc/init.d/networking/red.down/).
>>> 
>>> OK, will give it a try.
>>> 
>>>> 
>>>> Another great example how OpenVPN breaks running installations.
>>> 
>>> Yes, and there are comming some exiting new examples with the
>>> upcoming
>>> releases 8-| ...
>> 
>> Like what?
> e.g. this 
> https://community.ipfire.org/t/openvpn-2-5-development-version/2173/2
> or 
> https://community.ipfire.org/t/openvpn-2-5-development-version/2173/8
> 
> checkout the deprecated options :-\
>> 
>> -Michael
>> 
>>> 
>>>> 
>>>> -Michael
>>>> 
>>>>> On 6 Oct 2020, at 14:26, ummeegge <ummeegge(a)ipfire.org> wrote:
>>>>> 
>>>>> Am Dienstag, den 06.10.2020, 12:58 +0100 schrieb Michael
>>>>> Tremer:
>>>>>> Why do you have more than one client-connnect/disconnect
>>>>>> script
>>>>>> in
>>>>>> your configuration?
>>>>> 
>>>>> In this case it is a email which will be fired if someone is
>>>>> (dis)connected but there are plenty of potential possibilities.
>>>>> This
>>>>> one is not specified for my use case but may for the OpenVPN
>>>>> scripting
>>>>> architecture in IPFire in general.
>>>>> 
>>>>> Best,
>>>>> 
>>>>> Erik
>>>>> 
>>>>>> 
>>>>>> -Michael
>>>>>> 
>>>>>>> On 5 Oct 2020, at 16:59, ummeegge <ummeegge(a)ipfire.org>
>>>>>>> wrote:
>>>>>>> 
>>>>>>> Hi all,
>>>>>>> am currently in testing scenario with the new OpenVPN-
>>>>>>> 2.5_rc2
>>>>>>> and a
>>>>>>> additional --client-connect/--client-disconnect script.
>>>>>>> Since
>>>>>>> the
>>>>>>> release of OpenVPN metrics -->
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=708f2b7368cc8fbd54a06ca66337ebdcc26b58b4
>>>>>>> the new OpenVPN version lined out that only one script will
>>>>>>> be
>>>>>>> executed.
>>>>>>> 
>>>>>>> openvpnserver[15373]: Multiple --client-connect scripts
>>>>>>> defined.  The
>>>>>>> previously configured script is overridden.
>>>>>>> openvpnserver[15373]: Multiple --client-disconnect scripts
>>>>>>> defined.  The previously configured script is overridden.
>>>>>>> 
>>>>>>> so a question arises (beneath a lot´s others which are here
>>>>>>> OT),
>>>>>>> should
>>>>>>> we make it possible to execute more then one --(dis)connect
>>>>>>> script
>>>>>>> ? If
>>>>>>> so, are there may some ideas for this ?
>>>>>>> 
>>>>>>> Best,
>>>>>>> 
>>>>>>> 
>>>>>>> Erik
>>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> 
>> 
>> 
>