rafi Posted September 22, 2010 Report Share Posted September 22, 2010 Firon wrote:The timer is supposed to wrap every 49.7 days, not 3 weeks.@Firon:1. 2.04 was not out for that long, and yet you see the problem reports here and now2. alus said it was 22 days for him, on IRC3. 2.2 will not be out in 3 weeks4. ...but I guess you should do what you always do... Link to comment Share on other sites More sharing options...
TraderJones Posted September 24, 2010 Report Share Posted September 24, 2010 about half of the 2.0.x clients that I've seen over the last 48 hours now exhibit the behavior of this bug now.... so much for a "small number" of users affected.(and I've restarted my system and the router to make sure it's not something on my side). Link to comment Share on other sites More sharing options...
Firon Posted September 24, 2010 Author Report Share Posted September 24, 2010 The problem is a bit worse than I thought. It breaks -all- uTP traffic after 22 days, including all new connections. I initially thought it'd just break existing connections and new ones would be fine.I'll see about revving 2.0.4 today or over the weekend. Link to comment Share on other sites More sharing options...
rafi Posted September 24, 2010 Report Share Posted September 24, 2010 Thank you very much Edit:Oh, I forgot to mention: my ISP loves this new auto-disconnect feature... Link to comment Share on other sites More sharing options...
Firon Posted September 25, 2010 Author Report Share Posted September 25, 2010 New 2.0.4 up with the fix. We're autoupdating 100% of users. Link to comment Share on other sites More sharing options...
mcaspi Posted September 25, 2010 Report Share Posted September 25, 2010 I disabled uTP on my client. Found out that some isp's don't like uTP transfers. Shawcable is one of them. The moment the connection is changed to uTP speeds drop to 0. And this is one of the suggested changes in the settings to speed up transfers. Link to comment Share on other sites More sharing options...
Switeck Posted September 25, 2010 Report Share Posted September 25, 2010 mcaspi, uTP causing speed drops to 0 can be attributed to multiple causes...can you test some things to rule out other causes?(Like testing without a router, as some go into block-ip frenzy when they see the blizzard of UDP packets uTP makes.) Link to comment Share on other sites More sharing options...
mcaspi Posted September 25, 2010 Report Share Posted September 25, 2010 Don't use a router. The problem happens with some peers, not all of them. I can run the client using uTP but the thing is that the transfers with some peers will drop to 0 so I don't use it. That is why I guess it is related to the isp's. Link to comment Share on other sites More sharing options...
WavSlave Posted September 25, 2010 Report Share Posted September 25, 2010 I'm not sure if this is a big deal but after having installed 2.0.4.22150 the help file it downloaded says it's for 2.2.21586. Just FYI. Link to comment Share on other sites More sharing options...
Switeck Posted September 25, 2010 Report Share Posted September 25, 2010 "I can run the client using uTP but the thing is that the transfers with some peers will drop to 0 so I don't use it."I have that problem on ComCast, and attribute that mostly to older uTorrent versions' broken uTP implementation as well as having a tenuous connection to them.I've seen uTP "overcompensate" for lag and drop to near-0 speeds for no apparent reason. Link to comment Share on other sites More sharing options...
mcaspi Posted September 25, 2010 Report Share Posted September 25, 2010 Thanks. I'll continue to watch this. Link to comment Share on other sites More sharing options...
ftheup Posted September 26, 2010 Report Share Posted September 26, 2010 i think it is yust another phone companz bulshit,so that what it is this update Link to comment Share on other sites More sharing options...
hjhjhj Posted September 26, 2010 Report Share Posted September 26, 2010 Copy Peer List 188.115.133.38:046.118.70.135:095.133.109.200:0194.105.196.36:079.139.185.190:046.114.61.114:094.253.108.139:095.68.135.33:0194.6.165.178:095.143.213.231:0178.137.10.130:0109.94.73.227:0212.92.244.195:091.192.136.65:077.79.172.153:092.243.181.219:02.95.50.136:0194.187.105.178:092.113.12.233:0109.75.198.86:082.196.88.42:095.129.166.87:0193.160.224.4:095.139.244.253:095.133.207.143:092.112.22.20:095.190.121.15:070.56.127.149:0109.197.142.172:095.132.107.116:046.109.58.228:093.81.126.105:082.131.50.22:095.81.222.116:0212.86.253.132:095.129.166.101:0109.94.73.150:077.121.124.160:0 Link to comment Share on other sites More sharing options...
mcaspi Posted September 26, 2010 Report Share Posted September 26, 2010 I have that problem on ComCast, and attribute that mostly to older uTorrent versions' broken uTP implementation as well as having a tenuous connection to them.If that is so, why not disable uTP in those cases by software. I (2.0.4) download at 20-30 kB/s from a Bittorrent 7.0 peer using tcp. uTP drops it to 0. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 26, 2010 Report Share Posted September 26, 2010 hjhjhj: what of it? Link to comment Share on other sites More sharing options...
rafi Posted September 26, 2010 Report Share Posted September 26, 2010 I guess he points at port ":0" . uT keeping track of incoming connections that way is really confusing. More over uT also count them at the main view-peers' list. I suggest that as long as you don't have a valid IP:PORT pair - at least don't count them toward the total peers' display. Link to comment Share on other sites More sharing options...
Domokun Posted September 26, 2010 Report Share Posted September 26, 2010 µTorrent needs to fix the downloading of the translations. Each time I install µTorrent on a clean Windows 7 install and download the Dutch translation, µTorrent ends up being half translated. About 50% English and 50% Dutch even though the Dutch translation is 100% complete. Link to comment Share on other sites More sharing options...
rafi Posted September 26, 2010 Report Share Posted September 26, 2010 Does it happen with other languages too ? If not - maybe the translation itself is corrupt ? Link to comment Share on other sites More sharing options...
Domokun Posted September 26, 2010 Report Share Posted September 26, 2010 Does it happen with other languages too ? If not - maybe the translation itself is corrupt ?I don't know, if people who are German or Norwegian or whatever have this problem too I hope they report it as well. The translation itself is not corrupt because when I manually download the language pack and apply it to µTorrent, it works fine. So something during the downloading of and applying the language during the official µTorrent installation goes wrong. Link to comment Share on other sites More sharing options...
Switeck Posted September 26, 2010 Report Share Posted September 26, 2010 mcaspi said, "If that is so, why not disable uTP in those cases by software. I (2.0.4) download at 20-30 kB/s from a Bittorrent 7.0 peer using tcp. uTP drops it to 0."Because some peers/seeds now only work with uTP. And as you're seeing, others might only work properly with TCP. I've got my end set up to receive incoming uTP connections but not make any outgoing uTP -- letting the other ends decide what to use.To get uTP incoming only, but TCP both ways... Set bt.trans_disposition to 29. Link to comment Share on other sites More sharing options...
mcaspi Posted September 26, 2010 Report Share Posted September 26, 2010 I did that change even before you wrote it (asked just to make sure). In this certain connection speed dropped to 0. It looks like the remote client chooses uTP as the connection type. It looks to me that certain client versions can't make a good uTP connection and that is why I choose to disable it. Link to comment Share on other sites More sharing options...
mcaspi Posted September 27, 2010 Report Share Posted September 27, 2010 Another case. My 2.0.4 connected to 2 peers using 2.0.4 on the same ISP (them) and transfering TCP. When I enable uTP, the transfer continues to one of them. To the other, the transfer drops to 0. In my opinion uTP needs more testing. Link to comment Share on other sites More sharing options...
TraderJones Posted September 27, 2010 Report Share Posted September 27, 2010 Another case. My 2.0.4 connected to 2 peers using 2.0.4 on the same ISP (them) and transfering TCP. When I enable uTP, the transfer continues to one of them. To the other, the transfer drops to 0. In my opinion uTP needs more testing.It could be that one has the firewall/router configured correctly and the other doesn't, or that one's router can't handle uTP well. There's a number of reasons other than bad ISPs that need to be addressed by the end user. I'm not saying the uTP implementation is perfect, just that there's more possible issues out there. Link to comment Share on other sites More sharing options...
moogly Posted September 27, 2010 Report Share Posted September 27, 2010 Yep, that example doesn't prove anything. Many scenarios can correspnd to this observation. Link to comment Share on other sites More sharing options...
mcaspi Posted September 27, 2010 Report Share Posted September 27, 2010 Whatever reason it is, observations show me more active connections and faster transfers using TCP and part of the problem might be uTorrent's fault. Maybe this TCP/uTP issue is why many users complain that the new versions are slower than the older ones. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.