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 g...@greenie.muc.de:
> Hi,
>
> On Mon,
Hi,
On Mon, Jul 03, 2017 at 07:52:12AM +0200, open...@keemail.me 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
Hello!
30. Jun 2017 18:56 by g...@greenie.muc.de:
> Hi,
>
> On Fri, Jun 30, 2017 at 06:20:29PM +0200, > open...@keemail.me> wrote:
>> Now, in some cases, when the client connects with different ciphers, the
>> server appears to wrongly choose the peer cipher or data channel enc/dec
>>
Hi,
On Fri, Jun 30, 2017 at 06:20:29PM +0200, open...@keemail.me wrote:
> Now, in some cases, when the client connects with different ciphers, the
> server appears to wrongly choose the peer cipher or data channel enc/dec
> cipher.
>
> In the server logs this is can be observed as:
>
>
Hello list,
I've come across an issue with my OpenVPN setup with a single client.
The single client is allowed to connect multiple times (duplicate-cn on the
server side).
The server's cipher is configured to AES-256-CBC (cipher AES-256-CBC) and an no
ncp-ciphers, so the default of AES-256-GCM
