"Comcast is using an application from the broadband management company Sandvine to throttle BitTorrent traffic. It breaks every (seed) connection with new peers after a few seconds if it?s not a Comcast user inside your community boundary. According to some Comcast technicians, who were brave enough to tell the truth, these Sandvine boxes are installed at the cable modem termination system. As a result, it is virtually impossible to seed a file, especially in small swarms without any neighboring Comcast users."
My first sign of a glimpse of hope. After leaving UTorrent on for ages Harry Potter. Its Uploading slow but at least its going! My Utorrent settings are as follows: http://img526.imageshack.us/img526/6536/18669917wg7.png
25
200
50
Thats what the top right box #'s are. Only one out of many torrents is actually uploading. The other ones were attempting to upload before but now have no peers, seeds, leechers, etc.. Maybe nobody is attempting to DL. I'm not sure if I should DL a new torrent to test seeding on that.
I am wondering if you tried just the basic encryption, without any of the other suggestions.
There is a lot of exaggeration in many of those articles about the Comcast/Sandvine issue.
I have seen well over a 100 people with this issue (myself included) and for about 2/3rds of people, using only encryption (allowing legacy connections) has resolved the issue.
The trouble is that the articles can cause an over reaction, which will itself be the cause of problems connecting to peers.
For instance,I see that you have disallowed incoming legacy and disabled DHT.
Those options should not be used unless necessary as they will reduce the number of people that can connect to you.
If incoming legacy is allowed, with forced encryption, this would allow uTorrent (and Azureus) users, who do not have encryption on, to connect to you.
Once connected their client would automatically begin using encryption.
However, none of these non-encryptors can connect to you as you are set up now.
DHT also allows more peers to find you.
So if you have not tried just the basic, then you should see if things run better that way.
If you have and are still having trouble, then I am not certain that there has been a real resolution of this issue for people in your position.
It appears that using SSH tunneling would be the best option in that situation.
If you have tried the basic and it does not work, then I am not sure that anything will work.
My guess would be that SSH tunneling would be the best shot.
I have not seen one person come back at a forum and say that the Level 5 encryption suggested by Azureus worked for them.
The same is true of SSH tunneling.
I am not saying they do not work, but I have followed this with interest and have not seen anything be successful yet for the 1/3rd of users that basic encryption does not work.
Quote:thats how the program distinguishes p2p traffic
I am not so certain of that as I, and most people affected by Sandvine, did not need to curtail those and still can seed.
And as I said above, it has not appeared to help anyone to disable those.
