Slashdot Mirror


Virgin Media UK Begins Throttling P2P Traffic

An anonymous reader writes "The ISP which advertises itself as 'The fastest in the UK' and offers speeds of up to 100mbps has said it needs to throttle file sharing traffic to prevent slowness in other areas such as online multiplayer gaming. Trialing of the new traffic management plans commenced on March 2 and will only apply to upstream traffic, therefore download speeds will be unaffected. The clampdown will apply on top of the existing traffic shaping Virgin Media has in place and will affect all packages, including the previously unmanaged 100mbps deal. This policy, which applies to all broadband packages, is restricted to P2P applications and Newsgroups (which are commonly used to distribute large amounts of data)."

6 of 220 comments (clear)

  1. welp.... by CSFFlame · · Score: 4, Interesting

    And this is why all traffic should be obfuscated, if not encrypted. The ISPs have no business knowing what the content of the packets going across their wires are.

    1. Re:welp.... by Anonymous Coward · · Score: 3, Interesting

      tcptraceroute hotfile.com (usual port 80)

      XX manc-bb-1b-ae0-0.network.virginmedia.net (62.253.187.178) 15.334 ms 13.543 ms 17.212 ms
      XX know-core-1b-pc200.network.virginmedia.net (195.182.178.150) 14.972 ms 14.482 ms 15.388 ms
      XX wb7301a.network.virginmedia.net (62.30.0.204) 16.185 ms 14.264 ms 16.043 ms
      XX h3.hotfile.com (74.120.10.111) [open] 16.225 ms 15.056 ms 15.300 ms

      traceroute hotfile.com

      XX manc-bb-1b-ae0-0.network.virginmedia.net (62.253.187.178) 14.269 ms 39.439 ms 14.050 ms
      XX know-core-1b-pc200.network.virginmedia.net (195.182.178.150) 17.034 ms 16.912 ms 17.596 ms
      XX wb7301a.network.virginmedia.net (62.30.0.204) 14.581 ms 16.816 ms 17.377 ms
      XX brhm-bb-1a-ge-720-0.network.virginmedia.net (62.30.249.46) 18.815 ms 21.178 ms 19.656 ms
      XX 168.ge-1-3-3.mpr1.lhr2.uk.above.net (213.161.65.149) 30.848 ms 31.543 ms 30.107 ms
      XX above-ntt-2.lhr2.uk.above.net (64.125.12.134) 33.592 ms 29.077 ms 33.319 ms
      XX ae-2.r22.londen03.uk.bb.gin.ntt.net (129.250.2.77) 24.697 ms 25.470 ms 25.507 ms
      XX as-0.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.254) 119.334 ms 123.381 ms 107.119 ms
      XX ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 127.396 ms 104.020 ms 124.070 ms
      XX ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 103.490 ms 128.170 ms 109.354 ms
      XX as-1.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.42) 147.037 ms 168.994 ms 137.006 ms
      XX ae-2.r07.dllstx09.us.bb.gin.ntt.net (129.250.3.67) 147.517 ms ae-7.r08.dllstx09.us.bb.gin.ntt.net (129.250.2.154) 142.261 ms ae-2.r07.dllstx09.us.bb.gin.ntt.net
                  (129.250.3.67) 136.803 ms
      XX xe-0-4-0-4.r08.dllstx09.us.ce.gin.ntt.net (157.238.224.174) 150.740 ms xe-0-4-0-3.r07.dllstx09.us.ce.gin.ntt.net (157.238.224.142) 155.470 ms xe-0-4-0-
                  4.r08.dllstx09.us.ce.gin.ntt.net (157.238.224.174) 151.680 ms
      XX h3.hotfile.com (74.120.10.111) 153.151 ms 151.471 ms 150.152 ms

      what's that skippy? a 'transparent' network monitoring box looking at all the web traffic going to hotfile.com you say?...

      Its Virginmedia, we're used to this sort of shit from them...

    2. Re:welp.... by Fatal67 · · Score: 3, Interesting

      Encrypted p2p traffic looks just like encrypted p2p traffic. Most dpi vendors already have fingerprints for it.

    3. Re:welp.... by FutureDomain · · Score: 3, Interesting

      You can encrypt the port numbers, but not the IP packet. We need a good encrypted transport protocol that encrypts everything except the IP header and maybe a session id (so each session can use its own keys). ISPs will know what computer each packet is going to, but not the content, port number, sequence number, etc.

      --
      Hydraulic pizza oven!! Guided missile! Herring sandwich! Styrofoam! Jayne Mansfield! Aluminum siding! Borax!
  2. Not True by Spad · · Score: 3, Interesting

    Firstly, they've been doing this since before Christmas and it doesn't just affect uploads but does appear to be largely port-based throttling. It's pretty poor at "identifying" P2P traffic and a lot of people have had problems with gaming performance since they started trialling it.

    Secondly, this is what happens when you have a race to see who can claim to have the "Fastest home broadband", as has happened in the UK. When Virgin's top package was 10MBit, they didn't have any traffic management in place, but as soon as they jumped it to 20MBit to "beat" the ADSL providers offering 12MBit, they introduced their "STM" system for management and it's only got worse as they've jumped to 50MBit and now 100MBit. Yes, they've been upgrading their network infrastructure, but not fast enough to cope with the "upgrades" in speed that they're offering their users.

    Finally, and probably sadly, they still offer one of the better broadband connection packages in the UK because, while they are increasingly crippling your connection for large parts of the day, at least they're open about it and when it's *not* being crippled it's better that 99% of the ADSL alternatives.

  3. Re:Translation by timbo234 · · Score: 3, Interesting

    In the case of Australia plenty was done to provide real competition, and we now have tons of ISPs strongly competing against each other. The problem was that the underlying physical network was owned by the privatised formerly-government monopoly and there was no realistic way for someone else to run their own cables to every home and business in the country, thus we have the NBN. A public monopoly providing fibre is better than a private monopoly providing shitty copper cable, slow speeds and stingy bandwidth limits.

    --
    Pre-canned Evolution Links for all those Slashdot holy wars.