Hi,
On Fri, Apr 09, 2021 at 08:16:41AM +0200, Gert Doering wrote:
> That said, maybe we should just make it pushable *and* de-FATAL it for
> TCP mode (pushed or not). So server operators can decide what they want.
Looking into the code, it is pushable today, and ignored for TCP sessions
(it warn
HI,
On Thu, Apr 08, 2021 at 07:05:32PM -0400, Selva Nair wrote:
> On Thu, Apr 8, 2021 at 6:53 PM Mason Walters via Openvpn-users <
> openvpn-users@lists.sourceforge.net> wrote:
>
> > I've ran into this issue with 2.5 clients. Adding 'explicit-exit-notify'
> > to the client's config resolved it fo
Hi
On Thu, Apr 8, 2021 at 6:53 PM Mason Walters via Openvpn-users <
openvpn-users@lists.sourceforge.net> wrote:
> I've ran into this issue with 2.5 clients. Adding 'explicit-exit-notify'
> to the client's config resolved it for me.
>
>
> –explicit-exit-notify [n]
>
I have always felt that this (
I've ran into this issue with 2.5 clients. Adding 'explicit-exit-notify' to
the client's config resolved it for me.
–explicit-exit-notify [n]In UDP client mode or point-to-point mode, send
server/peer an exit notification if tunnel is restarted or OpenVPN process
is exited. In client mode, on exi
Hi,
On Thu, Apr 08, 2021 at 05:27:32PM +0200, Jordan Borgner wrote:
> On 4/8/21 4:37 PM, Gert Doering wrote:
>
> > Use "nobind" in the client config.
>
> No effect. I'll probably just restart the server in the evening.
I saw in your logs that the client was binding to 1194 - which triggers
bugs
On 4/8/21 4:37 PM, Gert Doering wrote:
Use "nobind" in the client config.
No effect. I'll probably just restart the server in the evening.
--
Jordan Borgner
___
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourcefor
On 08/04/21 16:37, Gert Doering wrote:
Hi,
On Thu, Apr 08, 2021 at 03:49:56PM +0200, Jordan Borgner wrote:
I'm facing a situation in which a client can't connect to the server
because an old connection of him is still apparent. So it still listed
in it's status file and the server still tries t
Hi,
On Thu, Apr 08, 2021 at 03:49:56PM +0200, Jordan Borgner wrote:
> I'm facing a situation in which a client can't connect to the server
> because an old connection of him is still apparent. So it still listed
> in it's status file and the server still tries to send packets to him.
>
> When t
I'm facing a situation in which a client can't connect to the server
because an old connection of him is still apparent. So it still listed
in it's status file and the server still tries to send packets to him.
When trying to reconnect, the client does not get prompted for a password.
Is there
