On 26/9/2015 5:01 μμ, ValdikSS wrote:
> You can push it from the server. The current codebase allows you to push
> almost anything - all pushed options are treated as if they were set on the
> client
> side; thus, inofficially you can push things like 'explicit-exit-notify' ,
> even though the
You can push it from the server. The current codebase allows you to push almost
anything - all pushed options are treated as if they were set on the client
side; thus, inofficially you can push things like 'explicit-exit-notify' , even
though the manual does not mention it.
On 26.09.2015 16:54,
On 26/9/2015 3:49 μμ, ValdikSS wrote:
> Please don't reply outside of maillist. Press "reply list" or "reply all"
> instead of usual "reply".
Thank you again for your latest advice.
I inadvertently deleted the list address instead of your personal one in
the recipients list! Sorry for this!
I
Please don't reply outside of maillist. Press "reply list" or "reply all"
instead of usual "reply".
On 26.09.2015 15:44, Nikolaos Milas wrote:
> On 26/9/2015 2:21 μμ, ValdikSS wrote:
>
>
> Thank you much for your advice!
No problem.
>
> I guess I could rather switch to TCP. I've heard it might
I suppose you're using UDP. This happens because UDP is stateless protocol and
server can't understand if the client disconnected right away unlike TCP.
OpenVPN supports special disconnect command which would probably solve your
problem
Add the following line in your client config:
explicit-exi
Hello,
I am using OpenVPN Server 2.3.5 on CentOS 6.7 x86_64.
It works fine, but I am having a problem:
When a client disconnects (mostly using OpenVPN GUI on Win Vista and
later versions, up to Win 10), the OpenVPN server delays to "understand"
the disconnect and consequently delays to run the
