Everything I've read about Comcast's network management policies says that they've stopped messing with Bittorrent traffic. But every time I use a BT app, seeding completed torrents is very problematic. I have no problems downloading torrents, and there is no problem uploading data while I'm downloading. But as soon as a torrent finishes downloading, it's like the client can't connect to most of the peers on the torrent. What happens is, when my client (uTorrent) tries to connect a peer (leecher), the peer is added to the peer list for a few seconds, but then that peer disappears from the list, like the connection has been chopped off. And this happens repeatedly. As a result, my upload speed is very low for completed torrents. Only a few peers "slip through the cracks" and maintain connection.
The seeding issue has existed on my service for years. This is not a problem with the router or with the configuration or with the signal. I have had this happen over several modems. I've tried multiple BT clients. All show the same symptoms. Again, I have no problem uploading torrent data at full speed as long as I'm downloading the same torrent. It's just that my client can't keep a connection to other peers as long as I'm seeding. I also don't have any problems uploading data using any other protocol, including eMule, FTP, etc.
I know Comcast officially used to throttle BT traffic years ago, but it's like they forgot to turn off the Sandvine boxes in my area. I'm from the NW suburban Chicago area. Can someone from Comcast look into this for me?
I don't think you're on the right track thinking that Comcast is forging packets again. Comcast has changed their ways and have made very good efforts to be transparent about their network management scheme. It's possible you are being subject to congestion managment tho. But, Comcast does not block P2P traffic or torrent applications as part of its current network congestion management technique.The technique does not manage congestion based on activities, protocols or applications; it only focuses on the heaviest users in real time.
Yeah, I understand that CC doesn't interfere with protocols, nerdburg. That's actually why I posted. Something is happening with my service that shouldn't be happening. I have never experienced this general congestion management BTW. It's only this specific issue with BT.
I'm not saying they started to throttle BT again. I'm saying they never stopped in my case. My BT seeding hasn't worked properly since probably 2007. That's why I'm wondering if this is because of some oversight or something. Maybe they forgot to disable their Sandvine devices in my area.
Also, forging TCP Reset packets is not the way they do it anymore, if that's what you're talking about. Modern BT clients use both TCP and UDP. If it was just the fake reset packets, UDP connections would still work just fine. From my observations, what they do is detect the BT handshake based on heuristics like packet timing and size. They don't even need to look at the packet contents. It's all very clever. And then they simply block all packets between me and the remote ip/port. So from my end, it looks like the other peer just dropped off the face of the earth.
I've been having the exact same issue. Tried everything I can and it must be on Comcast's end. The only solution I've found -- and it's not really a solution -- is to throttle my download speeds so that I can seed to 100% ratio before I've finished leeching.
Weird thing is, for me this just started about a month ago. Prior to that everything was fine. I've tried directing the traffic through :80 to no avail. Haven't tried VPN tunneling yet. I'm not a hard core bittorrent user, I just hate to not fully seed.
I'm from suburban Chicago. You say this started a month ago? You know, in your case, it might not be Comcast's fault, but something else. I don't think Comcast would just start throttling BT all of a sudden. Maybe you're just downloading overseeded torrents? Do you get peers that drop off a few seconds after they connect to you?
It honestly sounds like you guys have just got a bad string of torrents. However in Utorrent which I would personally recommend you use make sure you have forced outgoing encryption/allow incoming legacy connections.
Also making sure you do not have a low upload speed set from within Utorrent and check your queueing tab in Utorrent preferences.
Being on Ubuntu, I've been favoring Deluge for a client, but just found that uTorrent runs fine under wine. uTorrent screams by its use of uTP and grabs losts more peers through a better working PEX and DHT implementation than Deluge. Don't ask me why.. I'm just a user.
Guys, I don't think this is a problem with Comcast anymore. I actually changed my mind about them throttling BT. So don't blame Comcast. I think the explanation is simply that most torrents I download are overseeded. A lot more people have broadband than did a few years ago. Because of that and internet speeds having risen substantially, the ratio of seeders to leachers has in turn increased dramatically.
The error messages I observed in utorrent are probably due to the program trying to link up with other seeders. The problem is not dropped connections. That's just the way uTorrent works.
Also, what might help with seeding in uTorrent is raising your maximum upload slots per torrent and maximum connected peers per torrent. Contrary to what someone said, you don't have to enable encryption since Comcast doesn't mess with BT. (And even if they did, encryption would be pointless since throttling technologies are way ahead of builtin protocol obfuscation.) It may even hurt your throughput. This also applies to features like lazy bitfield, which I have turned off. And of course, use uTorrent if you're using another client, as someone has mentioned.
(which everyone should read before making his/her first post) state
2. Use Profanity
Please keep your posts clean. Our forums have an automated profanity filter to block out inappropriate language. Please do not circumvent it by finding colorful ways to approximate or disguise those words. If you are caught trying to bypass the filters in any way, your posting privileges may be revoked.