Leaderboard

Fixed.

@monstrocity Hello, we're very glad to see that the problem is resolved. 2048 packets make the output queue huge, but actually it is proportional to the amount of concurrent connections limit you have set in your torrent software. qBittorrent comes with a limit of 500 by default. The other error you report pertains to a disconnection, unrelated to TCP_OVERFLOW. If you get such disconnections more often when you torrent, please warn us. For the readers: overflow in the TCP output queue is a problem that does not exist in UDP. Kind regards

Added tcp-queue-limit 2048 in OPVN custom directives through Eddie using Hummingbird 1.01 and so far not seeing any TCP_OVERFLOW errors. Will report if the error returns. Thanks. Noting other Hummingbird errors through Eddie: ERROR: KEY_STATE_ERROR TCP recv error: Connection reset by peer ERROR: NETWORK_RECV_ERROR EVENT: TRANSPORT_ERROR Transport error on '37.120.210.221: NETWORK_RECV_ERROR [ERR] ERROR: TRANSPORT_ERROR Client terminated, restarting in 5000 ms... ERROR: N_RECONNECT log.txt

@monstrocity Please increase the maximum amount of packets allowed in the TCP queue with directive tcp-queue-limit n (n is the amount of packets) according to the amount of concurrent, global TCP connections your system needs when you run a BitTorrent software. OpenVPN 3 default limit is 64 packets. For example, add to your profile the following line: tcp-queue-limit 256 Please test again and check whether the problem is resolved. Of course consider to increase the amount of packets beyond 256 if you see the problem persisting. Your feedback is very much appreciated. Kind regards

@jeuia3e9x74uxu6wk0r2u9kdos Hello and thank you! It's still a beta version, but we expect to release a stable version really soon. We will also evaluate the feedback of course, please keep testing and report (if any) glitches or bugs as you have always done, thank you for your patience. Kind regards