On Fri, Jun 4, 2021 at 3:34 PM Bo Berglund <bo.bergl...@gmail.com> wrote: > > On Fri, 04 Jun 2021 20:17:59 +0200, Bo Berglund <bo.bergl...@gmail.com> wrote: > > >What could be causing this strange behavior? > > > >It seems like when the server has been connected to it goes blind for a while > >but then returns to normal for a new comm session.... > >Don't know how long one has to wait for. > > I have now added the directive: > explicit-exit-notify > > to the client side ovpn files, but it does not make much difference. > > From what I can see now the openvpn server is only able to authenticate and > connect a *single* client at a time! Thus defeating the whole idea behind > using > client-to-client in the first place... > > As soon as one connection succeeds a connection from the other device that > succeeded earlier now fails in the TLS phase.
You haven't shown us the server log without which you cannot make any conclusions. The client log ends at WAIT state which could mean either there is no route to the server or the server is not responding to TLS handshake. Post the server log. My guess would be that there is some messed up routing is happening. Once the RPi is connected your Win10 client may be losing route to the server. Selva _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
