Slow and varying speed

Mastiff

I have (with help from the braniacs on the forum, of course) set up a bridge between my two networks, something I haven't had in a few years. But file copying and everything else is extremely slow and varied. A largeish AVI file on 836 MB copies at maybe 700 KB/s for a few seconds, goes down to 0, stays there for a while, goes back up to maybe 2.4 MB/s and so on. It seems like the full copy will take 1 hour and 45 minutes. I have a 300/300 mbit/s in one end (the one I will be copying from) and a 50/20 mbit/s in the other end (where I will be copying too, so that would be the 50). I know that this is not the most efficient way to copy files, but it's very convenient. If I do the same thing over the VPN with multi-part FTP, it doesn't go any faster. It actually goes slower! 140 Kbps, so 14 hours... :lol:

I know something must be wrong because even a simple thing as using VNC over the VPN is incredibly sluggish, actually unusable if I don't go to a lower color setting. I have to use CloudBerry Remote Assistant to the other side and make sure it doesn't do LAN connection, because then it will be as slow as VNC. That is snappy, without any problems. There are no errors at all in the log files, actually not one log line after the initial connection, so it doesn't seem like it's because it's instable.

## server.ovpn ##
port 11720
proto udp
dev tun
ca ca.crt
cert server.crt
key server.key
dh dh2048.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
route 192.168.2.0 255.255.255.0
push "route 192.168.0.0 255.255.255.0"
push "dhcp-option DNS 192.168.0.1"
client-config-dir ccd
keepalive 5 10
compress
max-clients 1
persist-key
persist-tun
topology subnet
status openvpn-status.log

In the ccd directory I have a file named Hytteserver with this in it:

ifconfig-push 10.8.0.4 255.255.255.0
iroute 192.168.2.0 255.255.255.0

## Hytteserver.ovpn ##
client
proto udp
dev tun
remote MY IP 11720
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
ca ca.crt
cert Hytteserver.crt
key Hytteserver.key
compress
verb 3

Is there something here that can explain it? Can it be the compression that should be changed? The client and server are both small business server class motherboards with fast Xeon CPUs and 32 gig RAM running Windows Server 2016 and 2019.

I have no idea if it's related, but it seems like something forces this to tap even if I have set it to tun. Or maybe it's just me not understanding tun and tap at all.

Sun Mar 08 22:19:50 2020 open_tun
Sun Mar 08 22:19:50 2020 TAP-WIN32 device [OpenVPN] opened: \\.\Global\{47B3B53A-D6E5-46FA-B6D5-A25AD74DE773}.tap
Sun Mar 08 22:19:50 2020 TAP-Windows Driver Version 9.24 
Sun Mar 08 22:19:50 2020 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.4/255.255.255.0 [SUCCEEDED]
Sun Mar 08 22:19:50 2020 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.4/255.255.255.0 on interface {47B3B53A-D6E5-46FA-B6D5-A25AD74DE773} [DHCP-serv: 10.8.0.254, lease-time: 31536000]

TinCanTech

Mastiff wrote I know that this is not the most efficient way to copy files, but it's very convenient. If I do the same thing over the VPN with multi-part FTP, it doesn't go any faster.

How are you copying the file ?

Mastiff

Regular file copying in Windows. And then FTP, which is worse. But the VNC part is worse.

Pippin

Sounds like MTU issue, try

mssfix 1400

on client side,

Also add

explicit-exit-notify

on client side.

Manual 2.4:
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage

TinCanTech

Pippin wrote Sounds like MTU issue

Old myths die hard .. 😉

Mastiff

Sounds like an internal issue in the forum staff! :mrgreen: But adding those two didn't change anything, unfortunately. And I have found another problem too: It seems like the VPN tunnel makes the server double-headed. It slows down copying of files from the Windows Servers to their own subnet clients as well. I see the same symptoms I had when I accidentally connected two ports on a new four port server board to two different subnets that both had a connection to the Internet. Is there something I can do about that?

TinCanTech

How about using Linux not Windblows ..

Mastiff

The day you get Linux to run the suite of proprietary key server programs I need for my job, sure! :mrgreen: The reason I have Windows Servers is that it's the only OS they will run on, and that means I can work at home or at the cabin.

TinCanTech

Use Linux for your VPN.

Mastiff

You mean like a pair of pfSense VM's running the tunnel, and then have that connected to the Server's physical network with static routes?

TinCanTech

Personally, I would not use pfSense but .. what ever floats your boat.

Also, you could try the new Windows version of OpenVPN 2.5 with the WinTUN driver:
https://openvpn.net/community-downloads/

Mastiff

Thanks for the tips! I would use pfSense because I'm familiar with that, for OpenVPN to NordVPN, and for all my firewall services. But I'll try tht WinTUN version first!

300000

because you run udp so the speed is that varied so what you need to do now is chagne to tcp and add so thing to make it works for you , your internet speed is perfect working .

first charge to tcp not use udp
and adding this in your client congif file and try run it again to see if it works for you

tls-timeout 90
tun-mtu 60000
mssfix 0
hash-size 137552 155372
bcast-buffers 15310720
rcvbuf 9999990
sndbuf 9999990
proto tcp
tcp-nodelay
fragment 0
remap-usr1 SIGHUP

on the server just charge from udp to tcp and adding

tun-mtu 60000
rcvbuf 9999990
sndbuf 9999990

with this config this will be working for you when you copy file over internet or vnc on remote computer . the speed is ok for you.

TinCanTech

Instructions above for randomly stabbing in the dark ..

300000

@mastiff. Just do as I wrote and try it first to see the speed . It is very easy to make the charge in Windows

Mastiff

@300000, I had to remove some lines from the client because they were only for "mode server". And mode server crashed with other stuff. But when I was done and had it up and running, there was no change.

@TinCanTech, the new version didn't seem to change anything either. So I'm going to take a break and install Server 2019 on the second Windows Server and see if that changes anything.