BakaBT > Need Help? Ask Here

soo.. any way to seed better with comcast?

(1/4) > >>

kenshin-dono:
I usually have problems with seeding. I used to use just regular old bit torrent and sometimes id get to upload at like 100kbs or so for a little while, then it woudl throttle to 50k for a while then putter out. I usually seemd to have problems though and it would only upload at about 5kbs or so for a while. Still i would occasionally get decent little bursts for a while

my speedtest results are usually about 14mbs d.load and 3.8 ul

I tried d.loading Vuze because my friends kept saying how great it was. Well it seems to work terrible for me, i cant upload with it at all, the most i got was about 34kbs for a few seconds and most of the time it just gives about 3kbs for a few seconds then shuts off.

so i reinstalled regular old bit torrent but it seems to be sucking worse than before

I looked around on some FAQ's and saw comcast listed as causing problems with seeding. Is there anything ic an do to get around this? my ratios not that hot, about .7 but im really trying. I leave it on all day but when you get short bursts of 3kbs then it just stops its impossible. Am i just boned or is there any way to get this stupid thing to seed properly? preferably with regular bit torrent, i dont like the layout of vuze

Mag-X:
In uTorrent, you can enable encryption to try getting around Comcast's filters, but they can probably easily detect even that at this point. If that doesn't work, there isn't really anything that can be done. Your ISP is ultimately in control of the traffic that goes over it's network.

kenshin-dono:
i thought of trying the encryption method but i remember hearing that that can lock you out of private trackers.. which i belive this is right? No point in doint it and having it lock me out of the only tracker i care about my upload rate on =P

there was an option in vuze (even though i dislike it) called lazy bitfield that was said it could help.. but it did nothing, and i dont see an option for that in the regular vanilla Bittorrent 6.2 that i prefer

Arveene:
In uTorrent, use Forced encryption, uncheck allow legacy connections. Use a high port number 50000+.

You can also try using uTorrent 1.9.x, it's a beta client, but we allow it for these kinds of purposes. 1.9.x uses UDP which should get around Comcast's traffic shaping / throttling.

Don't keep your connection maxed out or Comcast will throttle your entire connection.

Klocknov:
My major problem with everything is having to share my connection with my brother who uses a shit load of bandwidth and I can't see how far along the cap we are. Last month it looked like I hit over there max amount since the last few days of that period I went from my normal of 250 upload on this line down to barely being able to push 20 out and didn't try to dl things... So that is where I hit problems, I have everything else running fine with uTorrent, though I do occasionally have to flip ports I'm sending over. I would recommend like setting a range of 25 ports in the 50000+ range to flip threw if you see a noticable drop in performance if you choose not to try the 1.9.x route. I'm not much of a fan of beta on these type of programs so I will stick with what is working for me at this moment.

Navigation

[0] Message Index

[#] Next page