Leaderboard

I would be interested about Staffs opinion about this one: https://torrentfreak.com/piracy-shield-iptv-blocking-orders-apply-to-all-dns-vpn-providers-231211/

Sadly there isnt a real "technology and privacy" education here in Italy. Even more, the Privacy Shield has been promoted and required by the Lega Calcio (soccer league) to "protect from illegal streaming of the matches" and here in Italy it seems soccer being more important than privacy and freedom.

Hello! Server load is indeed, and it has always been, one of the variables which are taken into calculation to determine the server rating and therefore recommend a server over another. Furthermore we have other inner variables which are monitored and are indicative of a server overload. In extreme cases yes, a server may be even closed to new connections due to overload, nothing new here. Such events are quite rare. Where does this assumption come from? There's no evidence that OpenVPN users are slowing down WireGuard users. The problem is mainly on the OpenVPN client side, as users running OpenVPN on agnostic networks and/or on devices not supporting AES-NI might be unable to reach the performance which they would enjoy with WireGuard. Again, whether or not prioritizing WireGuard over OpenVPN on the client side through our software default settings is not a problem due to OpenVPN stealing CPU time to WireGuard on server side (as incorrectly understood by @ms2738 too, we see now), as all servers have plenty of CPU available time for WireGuard, but a problem of customer satisfaction (in our previous message we mentioned the pros and cons which make the choice non trivial). Kind regards

This is what I do: https://github.com/tool-maker/VPN_just_for_torrents/wiki/Running-OpenVPN-on-Windows-without-VPN-as-Default-Gateway Works for Wireguard too. You add routing table entries to put the original default gateway back in effect (using a provided script - copy and paste). Basically you have all public IP addresses routed outside the VPN. And then bind the torrent client to the VPN interface (or address) to have it use the VPN. In Windows, a program bound to the VPN interface will ignore routing table entries that are not for the VPN interface. So it sees the VPN as the only route. I have used this (I wrote the scripts there) for many years. Some people complain that this is too much reading/too technical/too much work. But you really just have to copy and paste a couple of .bat scripts for the routing. Also, a caveat. This really does rely on the torrent program binding properly to the VPN interface. From that page: "If you are using uTorrent, uTorrent (older releases at least) will ignore your instruction to bind the VPN and use the default gateway if the address you specify does not exist." Recent versions of qBittorrent seem to have become unreliable for this too. I use Transmission (transmission-daemon.exe). For safety, I use Windows firewall to block the torrent program from using the real interface. The method is to block out-going traffic for that program from IP ranges 192.168.0.0/16 (for IPv4) and 2000::/3 (for IPv6). This presumes that your router uses NAT for IPv4 (with the usual LAN private address range) but not for IPv6. You can start Windows Firewall by executing "wf.msc". Or find it in the start menu. Add the rules in "Outbound Rules". One for IPv4 and one for IPv6. The address goes in the "Scope" tab in "Local IP address". Check "Block the connection" in the "General" tab. The program path goes in the "Programs and Services" tab in "This program".