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/).

Another great example how OpenVPN breaks running installations.

-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
>>> 
>> 
>> 
>