Re: [Openvpn-users] [ext] Does anyone suggestion regarding this error?

2023-02-10 Thread Huma Yari
Yes, one of our colleagues is in China and he must use our vpn to continue his work and he is strongly complaining regarding the slow download speed, and we cannot understand the reason. He is the only one who has this problem, others do not have slow download speed problem. I would like to sha

Re: [Openvpn-users] [ext] Re: OpenVPN-2.6.0-I004-amd64.msi still fails to work on Microsoft Windows 11 if opvpn-dco is enabled

2023-02-10 Thread Hans via Openvpn-users
Wasn’t compression done by openvpn considered a security risk, and to be avoided. Afaicr, Stephan Karger stated that compression should be done elsewhere. From: "Gert Doering" mailto:g...@greenie.muc.de>> Date: Friday, 10 February 2023 at 10:14:40 To: "Ralf Hildebrandt" mailto:ralf.hildebra...@

Re: [Openvpn-users] [ext] Does anyone suggestion regarding this error?

2023-02-10 Thread Ralf Hildebrandt via Openvpn-users
* Huma Yari : > We are having openvpn and it is a few days that I can see the following error > in our server log file: So, just a few guidelines how to approach this: 1) Find out something about that IP. Where's that located? Solution: Probably the city Sanya, province Hainan, China. The

Re: [Openvpn-users] Does anyone suggestion regarding this error?

2023-02-10 Thread Gert Doering
Hi, On Fri, Feb 10, 2023 at 03:03:35PM +0200, Lev Stipakov wrote: > Looks like you have a tls-auth key in your server config and some > client is trying to connect without tls-auth in its config. "client or just a random portscanner" Basically, tls-auth is doing what it's supposed to do: drop un

Re: [Openvpn-users] Does anyone suggestion regarding this error?

2023-02-10 Thread Lev Stipakov
Looks like you have a tls-auth key in your server config and some client is trying to connect without tls-auth in its config. pe 10. helmik. 2023 klo 14.42 Huma Yari (huma.y...@kingart-games.com) kirjoitti: > > Hello everyone, > > > > We are having openvpn and it is a few days that I can see the f

Re: [Openvpn-users] [ext] Does anyone suggestion regarding this error?

2023-02-10 Thread Ralf Hildebrandt via Openvpn-users
* Huma Yari : > Hello everyone, > > We are having openvpn and it is a few days that I can see the following error > in our server log file: > > Feb 10 10:44:33 openvpn 34974 TLS Error: cannot locate HMAC in incoming > packet from [AF_INET]59.50.242.0:56359 Is that server using TCP or Udp? --

[Openvpn-users] Does anyone suggestion regarding this error?

2023-02-10 Thread Huma Yari
Hello everyone, We are having openvpn and it is a few days that I can see the following error in our server log file: Feb 10 10:44:33 openvpn 34974 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]59.50.242.0:56359 Feb 10 10:44:34 openvpn 34974 TLS Error: cannot locate HMAC in inco

Re: [Openvpn-users] [ext] Re: OpenVPN-2.6.0-I004-amd64.msi still fails to work on Microsoft Windows 11 if opvpn-dco is enabled

2023-02-10 Thread Gert Doering
Hi, On Fri, Feb 10, 2023 at 09:45:41AM +0100, Ralf Hildebrandt via Openvpn-users wrote: > > It does, and it matters a lot. Mullvad breaks the OpenVPN protocol > > with their server configs (they should never ever push "comp-lzo" > > settings to a client that is not signalling it's willingness t

Re: [Openvpn-users] [ext] Re: OpenVPN-2.6.0-I004-amd64.msi still fails to work on Microsoft Windows 11 if opvpn-dco is enabled

2023-02-10 Thread Ralf Hildebrandt via Openvpn-users
* Gert Doering : > What they need to do is to enable "compression migrate" on the server > side, and stop unconditionally pushing "comp-lzo no" to clients that > are not signalling that they can handle this. Ah THAT's what we need to use :) -- Ralf Hildebrandt Charité - Universitätsmedizin Berl

Re: [Openvpn-users] [ext] Re: OpenVPN-2.6.0-I004-amd64.msi still fails to work on Microsoft Windows 11 if opvpn-dco is enabled

2023-02-10 Thread Ralf Hildebrandt via Openvpn-users
> It does, and it matters a lot. Mullvad breaks the OpenVPN protocol > with their server configs (they should never ever push "comp-lzo" > settings to a client that is not signalling it's willingness to accept > them). That's a bit like the problem we had locally. We were pushing "compress" to 2