From: Gert Doering <gert@...1296...>
To: ???????? ?????????????? <chipitsine@...277...>
Cc: "openvpn-devel@lists.sourceforge.net"
<openvpn-devel@lists.sourceforge.net>
Subject: Re: [Openvpn-devel] GUI repo
Date: Mon, 8 Feb 2016 08:42:38 +0100 [thread overview]
Message-ID: <20160208074238.GE24952@...1296...> (raw)
In-Reply-To: <CAFHpkQEzCUDpHgRZhxYqTBUkvSe7ra5-CiS06Auzke+6vB=dkg@...278...>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Hi,
On Mon, Feb 08, 2016 at 08:35:54AM +0500, ???????? ?????????????? wrote:
> I have one question regarding that.
> when we deployed openvpn, we used to supply our users a config file without
> "nobind" keyword.
>
> it worked for most of our users, however, those who needed 2 or more vpn
> connections complained that "port already bind". so, we added "nobind" to
> client config files and people become happy.
>
> what about that PR. there might be cases when
>
> 1) interactive service installed
> 2) user is administrator
>
> how many openvpn processes will be running ? how many of them will attempt
> to bind to 1194 ?
You still seem to misunderstand what iservice does - iservice does not
automatically run "thousands of OpenVPN processes". It will do what the
GUI tells it to.
So if it does not work without iservice because GUI tries to start two
jobs with "bind 1194", it will not work with iservice either - no
difference here. First bind will succeed, second one will not.
What is "first" depends on what the GUI starts first - it's all controlled
by the GUI, the service does not start anything on its own.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert@...1296...
fax: +49-89-35655025 gert@...1297...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2016-02-08 7:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 20:25 [Openvpn-devel] GUI repo Selva Nair
2016-02-07 21:56 ` Gert Doering
2016-02-08 3:35 `
2016-02-08 5:05 ` Selva Nair
2016-02-08 7:42 ` Gert Doering [this message]
2016-02-08 8:22 `
-- strict thread matches above, loose matches on Subject: below --
2016-02-07 15:42 Selva Nair
2016-02-07 16:00 `
2016-02-07 19:27 ` Gert Doering
2016-02-07 20:12 `
2016-02-07 20:29 ` Selva Nair
2016-02-07 20:32 `
2016-02-07 21:55 ` Gert Doering
2016-02-08 3:27 `
2016-02-08 7:40 ` Gert Doering
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=20160208074238.GE24952@...1296... \
--to=openvpn-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.