public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Fix max-clients option
Date: Mon, 04 Nov 2019 17:46:46 +0100	[thread overview]
Message-ID: <ff5d3b8c49745bda22e7ac8594cd8edfa762ebd3.camel@ipfire.org> (raw)
In-Reply-To: <CF7EF2BF-4594-4673-9F3D-EECDA9BA714B@ipfire.org>

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

On Mo, 2019-11-04 at 16:32 +0000, Michael Tremer wrote:
> Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> 
> Interesting is how long this has been in here unnoticed.
A long time...

> 
> > On 4 Nov 2019, at 14:52, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
> > 
> > Fix: Triggered by 
> > https://forum.ipfire.org/viewtopic.php?f=16&t=23551
> > 
> > Since the 'DHCP_WINS' cgiparam has been set for the max-client
> > directive, changes in the WUI has not been adapted to server.conf.
> > 
> > Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> > ---
> > html/cgi-bin/ovpnmain.cgi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
> > index 970444a55..09f0dc42f 100644
> > --- a/html/cgi-bin/ovpnmain.cgi
> > +++ b/html/cgi-bin/ovpnmain.cgi
> > @@ -355,10 +355,10 @@ sub writeserverconf {
> >         print CONF "push \"dhcp-option WINS
> > $sovpnsettings{DHCP_WINS}\"\n";
> >     }
> > 
> > -    if ($sovpnsettings{DHCP_WINS} eq '') {
> > +    if ($sovpnsettings{MAX_CLIENTS} eq '') {
> > 	print CONF "max-clients 100\n";
> >     }
> > -    if ($sovpnsettings{DHCP_WINS} ne '') {
> > +    if ($sovpnsettings{MAX_CLIENTS} ne '') {
> > 	print CONF "max-clients $sovpnsettings{MAX_CLIENTS}\n";
> >     }	
> >     print CONF "tls-verify /usr/lib/openvpn/verify\n";
> > -- 
> > 2.12.2
> > 
> 
> 


      reply	other threads:[~2019-11-04 16:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 14:52 Erik Kapfer
2019-11-04 16:32 ` Michael Tremer
2019-11-04 16:46   ` ummeegge [this message]

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=ff5d3b8c49745bda22e7ac8594cd8edfa762ebd3.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