Re: [Openvpn-devel] couple of questions on trac#665

Hi, On Wed, Dec 28, 2016 at 11:56 PM, Илья Шипицин wrote: > > I seem to see several times issues like described in #665 > I have seen this in the past but, iirc, without the FlushipNetTable error, though not 100% sure of that. However, > > what seems to be strange is

[Openvpn-devel] couple of questions on trac#665

Hello, I seem to see several times issues like described in #665 what seems to be strange is couple of things: 1) "OR" clause. why not "AND" ? https://github.com/OpenVPN/openvpn/blob/master/src/openvpn/tun.c#L6012-L6013 2) error message seems to be irrelevant

[Openvpn-devel] Fwd: Re: [Openvpn-users] 2.4, windows tap driver problem

Copying with the attached logs forwarded to the devel list for more expert opinion Hi, Thanks for the logs. The repeated .. Route: Waiting for TUN/TAP interface to come up... in the logs is the same as what I wrote about previously -- I think setting the tunnel IP by dhcp fails but openvpn

Re: [Openvpn-devel] couple of questions on trac#665

2016-12-29 10:23 GMT+05:00 Selva Nair : > Hi, > > On Wed, Dec 28, 2016 at 11:56 PM, Илья Шипицин > wrote: > >> >> I seem to see several times issues like described in #665 >> > > I have seen this in the past but, iirc, without the FlushipNetTable

Re: [Openvpn-devel] couple of questions on trac#665

2016-12-29 10:23 GMT+05:00 Selva Nair : > Hi, > > On Wed, Dec 28, 2016 at 11:56 PM, Илья Шипицин > wrote: > >> >> I seem to see several times issues like described in #665 >> > > I have seen this in the past but, iirc, without the FlushipNetTable

Re: [Openvpn-devel] couple of questions on trac#665

2016-12-29 9:56 GMT+05:00 Илья Шипицин : > Hello, > > I seem to see several times issues like described in #665 > > what seems to be strange is couple of things: > > 1) "OR" clause. why not "AND" ? https://github.com/OpenVPN/ >

[Openvpn-devel] [PATCH 1/1] fix timeout in non-TLS mode with systemd

From: Christian Hesse In non-TLS configuration we wait for the remote peer to connect before issuing "Initialization Sequence Completed". So prevent to time out by telling systemd service manager we are ready for now. Status will be "Non-TLS mode, ready for now. Waiting for

Re: [Openvpn-devel] [PATCH 1/1] fix timeout in non-TLS mode with systemd

Hi, On Wed, Dec 28, 2016 at 02:07:21PM +0100, Christian Hesse wrote: > @@ -73,6 +77,21 @@ tunnel_point_to_point(struct context *c) > return; > } > > +#ifdef ENABLE_SYSTEMD > +/* In non-TLS configuration we wait for the remote peer to connect > + * before issuing

Re: [Openvpn-devel] [PATCH 1/1] fix timeout in non-TLS mode with systemd

Gert Doering on Wed, 2016/12/28 19:57: > Hi, > > On Wed, Dec 28, 2016 at 02:07:21PM +0100, Christian Hesse wrote: > > @@ -73,6 +77,21 @@ tunnel_point_to_point(struct context *c) > > return; > > } > > > > +#ifdef ENABLE_SYSTEMD > > +/* In non-TLS

Re: [Openvpn-devel] [PATCH 1/1] fix timeout in non-TLS mode with systemd

Hi, On Wed, Dec 28, 2016 at 08:37:48PM +0100, Christian Hesse wrote: > > We definitely need a better approach than "litter ENABLE_SYSTEMD all > > over the code". > > Well, openvpn supports a number of modes of operation... Some of these have > other requirements than others. This I understand

Re: [Openvpn-devel] [PATCH 1/1] fix timeout in non-TLS mode with systemd

Hi, On Wed, Dec 28, 2016 at 2:37 PM, Christian Hesse wrote: > > For informational purpose we could add even more calls. That would allow to > set intermediate status message, something like: "Up and running, currently > serving 25 client connections." If the daemon has to send