on 12-03-2019 18:21
Hi,
I have been Virgin Media (and NTL) customer for the past 12 years. Starting with 2Mb/s connection, I went through multiple upgrades, currently at 350Mb/s.
In the past weeks or maybe months, I have noticed that as soon as I turn torrenting on any computer or server in my house on, the WAN download connection drops to 10Mb/s flat on every device in the house (total). On top of that, I experience massive, 25% packet drops (tested by ping -t 1.1.1.1 and 8.8.8.8). Turn torrent off, and bam, problem solved.
My SuperHub 3 is setup in modem mode. My edge firewall is virtualized pfSense 2.4.4 and VLAN routing is done on Cisco 3560CX. Pretty basic setup that works fine.
Has Virgin Media introduced some sort of policy recently that throttles customer's connection down to make it feel like 2007 again for torrenting, or is my SuperHub 3 modem acting up?
Paying over £50 for 10Mb connection does not seem like a good deal for me any more. There are unthrottled 70/20 options out there for half the price.
25-05-2020 14:41 - edited 25-05-2020 14:44
I've been researching this strange behaviour for a few years now. I made a post with a video back in 2017 that sees exactly the same symptoms as seen here. https://community.virginmedia.com/t5/Speed/Vpn-throttling/m-p/3509177#M172096
I also run Pfsense, however that is irrelevant as I've tried to connect my PC directly to the Super Hub 3 in modem mode and it still does this.
In my case I am running a VPN.
Turns out it's the uTP protocol that's triggering the SuperHub or VM's network (I'm not sure which yet) to throttle the connection down to roughly 10Mbps.
This is actually a very strange occurrence since I'm not sure how VM's network is detecting whether the packets are using TCP or uTP within the VPN tunnel. It's very possible that the way in which these packets are being transmitted could be overloading whatever hardware is in the pipeline, whether that be from the Super Hub 3 end or the cabinet. With the problems we have with the Puma 6 chipset, it would not surprise me at all if the Hub is just getting overloaded for whatever reason that seems to be unique to when uTP is being used.
In Qbittorrent in particular, you have to set the connection to TCP only.
Basically the general fix is to disable uTP protocol in your torrent software. This got rid of the issue 99% of the time for me, however there are some occasional torrents that this does not work on for some reason.
I'm going to be receiving the Super Hub 4 this week, so I'm going to test to see if it still throttles when uTP is enabled. This will tell us whether this is a specific problem with the Hub 3 or whether it's a more widespread issue with VM's infrastructure.
on 26-05-2020 08:08
I will be interested in the results of your findings
Thanks
26-05-2020 19:48 - edited 26-05-2020 19:55
Can confirm it still happens with the superhub 4, but it does cap a little bit higher at 1.7MB/s to 2.0MB/s.
Super Hub 3 capped at 1.4MB/s
on 27-05-2020 14:48
Can you change the LAN IP on the SH4 to for example 172.16.x.x or 10.115.x.x (not just the octets on the 192)
Thanks
on 28-05-2020 09:36
Not good
08-06-2020 16:18 - edited 08-06-2020 16:33
ignore
08-06-2020 16:26 - edited 08-06-2020 16:33
ignore
on 08-06-2020 16:32
on 08-06-2020 16:34
on 08-06-2020 16:49