Hey guys,

Just came accross this new site.

Hundreds of larger and smaller ISPs all over the world try to limit BitTorrent traffic on their networks. Unfortunately, most companies are not very open about their network management solutions, with Comcast as the prime example. Thanks to the Glasnost project, you can now test wheter your ISP is one of the bad guys.

broadband.mpi-sws.mpg.de...rency/bttest.php

Read at, https://ubertt.org/forum...p?f=15&t=316

I myself haven't had the chance to run the test yet as the servers are under very high load, but it will be interesting to see the results.

I'm with iiNet, I won't testing it, as they don't.

"We are sorry. Our measurement servers are currently busy. Please try again later."

Lame :/ I highly doubt I need to worry with Internode though.

BrinK writes...

"We are sorry. Our measurement servers are currently busy. Please try again later."

Yeah still the same here, they are looking for more hosts.

Will be interesting to see what the results are show as tho.

Mmm it'll be interesting if they uncover any dirty secrets about some isp's.

I don't care about throttling, so long as its very clear to the user who's signing up to the plan. Unfortunately its harder than it should be to find out if an isp throttles.

I'll keep an eye on this project. Might get interesting.

Cugel writes...

I'm with iiNet, I won't testing it, as they don't.

Keep in mind it still could be valuable to test ISP's who users are pretty sure they don't in order to see if the tool is accurate...

I did a test, all clear on the simple version. Which seems to merely go by ports, which probably wouldn't mean anything anyway.

Wouldnt it be obvious if you have a 1500/256 connection and have never gotten above 10kbs when downloading? Even with something like open office on bt that has a heap of seeders.

Also Bigpond gets ~150's in utorrent so I'm not worried.

There is already a list of bad ISPs on the Azureus site, plus there is this forum.

If an Oz ISP throttled P2P we would know about it.

What does actually Throttling mean? maxing the connection speed or what?

King Koopa writes...

What does actually Throttling mean? maxing the connection speed or what?

They specifically throttle (i.e. slow down (not spank!)) certain packets that are associated with P2P.

If the packet say is using the bittorent protocol, then they 'slow' these down (I assume by injecting a wait period before forwarding?).

The excuse used is that P2P traffic slows down the network for others. WestNet openly state they use it at such times that network conjestion is occuring - but as others have pointed out - at what point should they order more bandwidth versus slowing down certain protocols?

:-)

Maveri writes...

The excuse used is that P2P traffic slows down the network for others. WestNet openly state they use it at such times that network conjestion is occuring - but as others have pointed out - at what point should they order more bandwidth versus slowing down certain protocols?

Yes its a sign that the ISP is over subscribed and can only provide the lowest common denominator of internet (web browsing). Fairly pathetic.
Generally you'd assume as a user, you'd all be treated equally. Apparently not.

Maveri writes...

If the packet say is using the bittorent protocol, then they 'slow' these down (I assume by injecting a wait period before forwarding?).

There's more than one method in slowing down BT traffic. ISPs can also forge RST TCP packets that cause you to stop downloading/seeding with a peer.

On Optus, tried to do the test but its busy will try again later. But I'm 99.999999999% sure they don't block torrents

C0RE 2 DU0 writes...

But I'm 99.999999999% sure they don't block torrents

I 100% sure they don`t.

All green

Servers are still busy......

Give up for today

:(

If you want to give it a go, just keep trying (quickly). Took me 12 clicks to get through.

I'm with amnet and everything was in the green :)

All clear here, aanet.

Here are my results, I've run the test about 4 times and all were pretty consistent. I'm on EFTel/EGN synced at 8mbit and able to achieve full speeds.

Is BitTorrent traffic on a well-known BitTorrent port (6881) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

- There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP upload achieved minimal 104 Kbps while a BitTorrent upload achieved maximal 282 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

- There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 30 Kbps while a BitTorrent download achieved maximal 41 Kbps. You can find details here. (Note: This part is made irrelevant by the last section)

Is BitTorrent traffic on a non-standard BitTorrent port (4711) throttled?

* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.

- There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP download achieved minimal 250 Kbps while a BitTorrent download achieved maximal 236 Kbps. You can find details here.

* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.

- Your ISP possibly rate limits your BitTorrent downloads. In our tests a TCP download achieved minimal 227 Kbps while a BitTorrent download achieved maximal 52 Kbps. You can find details here.

Is TCP traffic on a well-known BitTorrent port (6881) throttled?

* Your ISP possibly rate limits all downloads at port 6881. In our test, a TCP download on a BitTorrent port achieved at least 30 Kbps while a TCP download on a non-BitTorrent port achieved at least 227 Kbps. You can find details here.

* Your ISP possibly rate limits all uploads at port 6881. In our test, a TCP upload on a BitTorrent port achieved at least 104 Kbps while a TCP upload on a non-BitTorrent port achieved at least 250 Kbps. You can find details here.

Not surprising really since EFTel have admitted to BT shaping, but I didn't think it would be THAT bad. I've already made the switch over to Rapidshare for most of my downloads anyway. Someone should edit the azureus wiki :P

Has anyone tried the test using ports in the range 49152-65534?

Muad'Dib writes...

Has anyone tried the test using ports in the range 49152-65534?

Doesn't seem to let you choose your own ports

Does IPSec fix the throttle seing as the packet is secured?

jeremydt writes...

Does IPSec fix the throttle seing as the packet is secured?

Not really. There are still more advanced tools to detect stuff like that. Depends how much an ISP is willing to invest in this area.

iiNet passed all the tests. :)

Network Monitor FAQ

www.azureuswiki.com/inde...work_Monitor_FAQ

For some time, we have been aware that some network operators have taken steps that are designed to interfere with the free flow in Internet traffic through their networks. Traffic associated with Bittorrent protocol-based applications, like Vuze (Azureus), has been particularly targeted.

Use this in conjunction with the Tester.

at work bigpond past all tests :)