Hi,

I'm already using explicit-exit-notify, which doesn't seem to help in this 
specific case.

I'm afraid you're right, further discussion seems a bit off - I will conduct 
further research.

Thank you very much for your assistance!

3. Jul 2017 09:01 by [email protected]:


> Hi,
>
> On Mon, Jul 03, 2017 at 07:52:12AM +0200, > [email protected]>  wrote:
>> You have valid and very helpful comments, but for this specific case I ca 
>> not use --nobind.
>>
>> The client(s) will be updated any day now, but I need to keep --ncp-disable 
>> and varying --cipher's as that's a requirement for me.
>
> You insist on using a combination of *four* things that need to be all
> true at the same time to cause these issues (same username, not using 
> --nobind, using --ncp-disable, plus varying ciphers).
>
> Depending on how your clients disconnect, --explicit-exit-notify might
> help (because that will ensure the server knows "client went away") - but
> otherwise, this is turning into a "if I do this, it hurts" - "then don't
> do this" thread.
>
> gert
>
> -- 
> USENET is *not* the non-clickable part of WWW!
>                                                            //www.muc.de/~gert/
> Gert Doering - Munich, Germany                             > 
> [email protected]
> fax: +49-89-35655025                        > 
> [email protected]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to