I have no specific set up which is relevant. My network has never been fast until recently - the testing I did internally was with another server on my LAN. Externally I have no issue with what we do.
Note that if countries are blocking VPN apart from 443 then you'll have problems with OpenVPN on 1194, but you can change the port.
I have no idea what could be wrong to slow you down, but it could depend on where you are connecting from as well. As ClearOS is on your LAN, you can test from your LAN by connecting to it then upload or download something to 10.8.0.1, the ClearOS OpenVPN IP.
So you are running ClearOS standalone. It should still give you good speed. Remember the speed could be limited at either end. It is the lower of the local uplink speed and remote downlink speed when uploading from the local end, and vice-versa when downloading. Public AP's may stop you. You'd need to check your connection logs to see if the connection made it as far as the server.
I have no special settings at all. If you have speed issues, your problem is elsewhere.
When you are testing, what are you local and remote uplink and downlink speeds? What is the result of "lspci -k | grep Eth -A 3"?
Please edit you post to only include the logs around your connection attempt. I don't want to look through it all.
2 - ???? Are you saying ClearOS is not your gateway and is at 192.168.1.2? In that case you will want a port forward in your router, but not in ClearOS. The important one is UDP:1194 for OpenVPN. Also note that 192.168.1.0/24 is not a good subnet for an OpenVPN server.
What is your LAN layout as I can see another subnet, 10.210.0.0/16 in some of your log.
1 - have a look in /var/log/openvpn. If you don't have it, use WinSCP.
2 - What! You can't port forward everything! That could be your problem
3 - It is possible but sort out 2 first before you can check.
4 - by doing 6. Yer, your address seems to be routeable.
5 - Yes (in ClearOS)
6 - OK
Leave the client firewall and AV on.
Please show the log on ClearOS for the time you made the connection on your client.
I've tried nmap to you on tcp:1194 (not used by OpenVPN normally but it is a good check) and it came back as closed. It should come back as open, so I suspect either the firewall is not open, you have set up port forwarding for OpenVPN, your ISP is blocking you, or you have a non routeable public IP, perhaps using a cell connection. Make sure you don't have port forwarding enabled for OpenVPN in ClearOS.
To you get your public IP back from "curl ifconfig.co" or does it return a different IP.
Then I am afraid I don't know how to do it or how to troubleshoot. I suspect the culprit is a program called syswatch (which is a ClearOS program) which is written in perl. I have no idea how to debug it and have no experience of perl. I do note there is a flag in /etc/syswatch which enables a debug mode but I have never tried it.