public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: OpenVPN no more --client-(dis)connect scripts can be executed
Date: Mon, 05 Oct 2020 17:59:16 +0200	[thread overview]
Message-ID: <f4c8879918eeffff38401c9348a1d8f1c86216bb.camel@ipfire.org> (raw)

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

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


             reply	other threads:[~2020-10-05 15:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 15:59 ummeegge [this message]
2020-10-06 11:58 ` Michael Tremer
2020-10-06 13:26   ` ummeegge
2020-10-07  8:20     ` Michael Tremer
2020-10-07  9:21       ` ummeegge
2020-10-07  9:22         ` Michael Tremer
2020-10-07 10:37           ` ummeegge
2020-10-07 12:38             ` Michael Tremer
2020-10-08  8:11               ` ummeegge
     [not found] <d882bc32-2b80-3aa4-893c-a2005bf431f3@gmail.com>
2020-10-08 14:26 ` Michael Tremer
2020-10-08 17:18   ` Adolf Belka
2020-10-11 14:16     ` ummeegge
2020-10-12 10:45       ` Michael Tremer
2020-10-12 11:28         ` Adolf Belka
2020-10-12 14:23           ` Michael Tremer
2020-10-12 15:46             ` Adolf Belka
2020-10-13 11:46         ` ummeegge

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=f4c8879918eeffff38401c9348a1d8f1c86216bb.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --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