> > > > This node where the logs were from (server): > OpenVPN 2.4.7 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] > [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019 > > Other (client) > OpenVPN 2.4.0 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] > [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 29 2022 > > Please do not tell me to upgrade I will upgrade it in the next 5 years but > this was working just fine till now. >
These version combinations will work on a good day, but when there is a network glitch, they could go into a restart dance with both backing off exponentially and missing each other. This issue was fixed in 2.5.3. If the above is indeed the issue, a quick way to recover is to restart the server and client at the same time as Gert mentioned. But that will last only until the next bad day. > Here is the log from the client: > By matching logs I mean client and server logs at time frames that overlap. We want to see what the server is doing when the client is trying to connect. Selva
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
