Jump to content

Throttling and IPv6


Recommended Posts

I'm currently running Rogers as my ISP here in Ontario, Canada who is really bad for throttling and blocking encrypted traffic. While I have spent the last few days trying to start a torrent (initial seed), reading forums, trying different settings etc. During this very frustrating process, which the only solution to seems to be a paid vpn service, I have noticed that with a very few exceptions I've noticed that IPv6 connections are always much faster. So much so that I would exclude all other connections and seed solely to IPv6 ones just for the fact that I could get my torrent out there much faster!

My connection is 10Mb/s down and 512 Kb/s up and it is setup using the speed guide settings.

A current example is I currently have 8 peers connected, 7 of which are regular IPv4 address getting between 0.2 - 2.0 KB/s. Peer number 8 is an IPv6 address who is averaging about 11 KB/s with peaks of close to 20. While I was typing all that I had a different IPv6 address come and go with a sustained 30 KB/s!!!

The only thing I can think of that might cause this is that for whatever reason IPv6 address seem to bypass my ISP's throttling.

Has anyone else noticed this or know what would cause it? I would love a way to exploit this as with a 10 Mb/s down and 512 Kb/s up connection it's very hard to not be a leech even without the throttling.

Link to comment
Share on other sites

I tested out the ipfilter option and while it did block all IPv4 addresses I also received these errors for IPv6 addresses:

[2009-05-29 04:03:28] [2001:0:4137:9e50:881:3886:bb8a:ebe3]:37541: Connecting: source: C

[2009-05-29 04:03:28] [2001:0:4137:9e50:3487:5ae:e726:bb8c]:39877: Connecting: source: C

[2009-05-29 04:03:28] [2001:0:4137:9e50:881:3886:bb8a:ebe3]:37541: Disconnect: Peer error: The requested address is not valid in its context.

[2009-05-29 04:03:28] [2001:0:4137:9e50:3487:5ae:e726:bb8c]:39877: Disconnect: Peer error: The requested address is not valid in its context.

[2009-05-29 04:03:31] [2001:0:4137:9e50:30d4:f72c:9c09:9253]:15821: Connecting: source: C

[2009-05-29 04:03:31] [2001:0:4137:9e50:30d4:f72c:9c09:9253]:15821: Disconnect: Peer error: The requested address is not valid in its context.

Not sure why but I'll look around and see if I can find a solution.


Okay so I have unblocked my tracker (The Pirate Bay) and I have now started to receive some connections but most of them will connect then almost instantaneously disconnect. Every once in a while I will get a peer that'll stay connected for about a minute at high speeds, anywhere from 20-47 KB/s.

Also does anyone know what IP addresses I'd have to unblock to allow DHT, Local Peer Discovery and Peer Exchange?

On an interesting side note, my method of filtering seems to almost exclusively use uTorrent peers. I have seen a few Mainline and BitTorrent peers though.

Link to comment
Share on other sites

Well both the IPv6 addresses and switching to port 1720 worked for a bit but now they both seem to have been throttled. :-(

I'm going to try uTorrent 1.9 now.

Update #1:

Seems to be working so far although I'm keeping my fingers crossed.

Update #2:

Well after nearly 30 minutes of constant 47 KB/s uploads (my limit) I was ready to declare changing to uTorrent v1.9 a success but it seems that within the last 15 minutes my connection has again been throttled to under 10 KB/s with a few spikes. It could be just time of day throttling but I'm not sure.

Link to comment
Share on other sites

Well, I'm not sure what features you're talking about but for the last 13 hours I've had minimum average uploads of 40+ KB/s with a few drops in speed that lasted for about 15 minutes max. Also the 47KB/s limit is set by me, not rogers.

Link to comment
Share on other sites

Sorry, I was under the impression you only had 0.5 megabit/sec upload.

If you have less than 20 total peers to choose from to upload to, it's possible to have slowdowns just due to some/many being slow.

But it seems you've mostly dodged whatever Rogers is using to detect BitTorrent...for now.

I'm sure they'll change their methods in a couple months to change that. :(

Link to comment
Share on other sites

Oh, I do have 0.5 Mb/s upload limit and I could easily give all of my bandwidth and get 60+ KB/s but then I can't use anything else on the internet very effectively.

As for Rogers changing their methods, I'm expecting them to. It just depends on if a software change on their end can throttle uTP or if they have to change out some hardware.

I also have over 180 peers to choose from so I'm sure it's not lack of choice or speed! :-)

Link to comment
Share on other sites

As of right now I have 28 of 174 peers connected (2 in swarm). I've also been at 47KB/s for 10+ hours non-stop with barely a hiccup in speed. :D


It's really weird, it appears to me that I double posted every post I made in this thread! Although I know that when I made my last post I hadn't. :/

Link to comment
Share on other sites

So 16 total upload slots (if 4 torrents active) and more allowed if upload speed <90% max.

If you're only running 1 torrent, raise upload slots to 5 or 6...should vastly reduce very slow peers from tying up all your upload slots at once.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...