UPDATE Re Comcast is using Sandvine to manage P2P Connection
Just an update -- it's been 3 months since my original post, which I tried to make as accurately as possible. Naturally, I've learned a few things since then.
HOWEVER -- please still see the first post and my commentary that follows it. All the proof is here, and it is easily testable and reproducible -- that it is happening is non-disputable. Unless my testing is somehow flawed, These are facts.
However, you will have to decide for yourself whether it is done in an acceptable way or at an acceptable level. Those issues are opinions.
Here are some developments, just in case you haven't been keeping up with the thread...
I have received multiple reports from anonymous "insiders" that my reports and findings are "on track."
What is working for me:
Encrypted tunnels to a point outside the Comcast network (VPN, SSH tunnel, etc.)
Forcing encryption (works for me, but not for many others who have tried it)
When downloading, make sure that the user has met his uploading goal by the time that the download completes. The easiest way to accomplish this is to set a download rate slower than the uploading rate.
Tolerating the up to 40% rate RSTs when using BitTorrent to upload a file and not forcing encryption. Even at that seemingly high rate, I can still reach my preferred 16 KB/s (256 Kbps) upload limit.
What is not working for me:
Setting your firewall to drop RST packets. Since the RST is confirmed to be sent in both directions, ignoring the RST on only one side creates a useless half-open connection.
Reporting the issue to Technical Support
Gnutella uploads -- almost always blocked (nearly 100%).
Tolerating RSTs when using ED2K to share files. Although some uploads go through, way too many fail. Additionally, the ED2K anti-abuse routines in most clients will ban users who accept requests and then later fail to upload when a request is made for parts of files that I have. This means that I cannot download from them, and they are holding parts I need of these same files. The ED2K implementation of Sandvine at Comcast is very broken!
Significant reports I've read but can't confirm:
Seeding is "impossible" -- numerous reports, it just doesn't happen to me.
Forced Encryption does not help in many reported cases.
Cannot upload 2 GB of data without a reset, using FTP or Lotus Notes -- I haven't tried it.
Forced encryption is working better than leaving it off but its still not the same as before. Harder to keep my ratios up on private trackers now. I usually get to around 40% RST connections when using the .bat file also.
Going to test on the p2p application that pushes patches through on World of Warcraft next time a big patch comes out and see what kind of outcome it has in store.
I tested my Utah comcast connection last night, seeded about 10GB to approx 20 peers maxed at 220KB per second upload the entire time. I didn't download any part of the torrent, it was a 3.5GB file i already had. So far in the last couple weeks I've been able to seed around 35GB of data on various torrents/trackers
I don't have encryption forced so i cant comment on whether all the connections were encrypted or not.
I guess what I'm saying is that i don't notice anything unusual (yet).
I've notice my bit torrent share ratios have dropped over the past few months. My seeding stops after the download completes. Where do I change the setting to forced encryption? On my bit torrent client? On my lynksys router? I'm technology challenged but can follow directions.