µTorrent 2.0.2 released

[DreadWingKnight]

If you disable uTP, you don't connect to anyone who is set to uTP only.

You still connect to any with TCP enabled in any way.

[heidelberg23]

@rafi: Yep, uTP creates a great many overhead traffic and PPS. Many russian ISPs blocked uTP traffic because of high PPS.

[nivaldin]

what is PPS?

[heidelberg23]

@nivaldin: Packets Per Second

http://www.cisco.com/web/about/security/intelligence/network_performance_metrics.html

[rafi]

@booze/nivaldin: as a compromise, you can still allow only incoming uTP connections (B-4a in my sig)

[booze]

Ok thanks guys, don't really care if i can't connect to uTP only clients so that's no problem.

[Zarggg]

I find it funny how I still get full bandwidth utilization on well-seeded torrents with good trackers (i.e., *nix distros) even with uTP and net.calc_overhead turned on, and decent speeds (~200 - 600kB/s on average) on other torrents.

Are all you naysayers implying I'm going insane and am not actually downloading at 1200kB/s (10Mbit)?

[eliot_cougar]

I still don't see the BEP22 fix Greg Hazel has made long ago... It prevents Windows to use its DNS cache system which returns NETBIOS name on FQDN request... (Stupid Win)

[rafi]

is advanced->isp.bep22 true ?

[eliot_cougar]

Ofcourse it's enabled... I'm talking about this bug: http://forum.utorrent.com/viewtopic.php?pid=469446#p469446

It's Windows-specific, if you try to get FQDN for your own machine like this:

socket.gethostbyaddr('your.own.ip.addr') or this socket.getfqdn('your.own.ip.addr')

Windows will return your NETBIOS name instead...

We have found that you have to set additional flag DNS_QUERY_WIRE_ONLY to force Windows to bypass cache and do real DNS request... Greg has wrote some advanced code to make that work, but it still doesn't seem to be included in the latest revisions...

[Bence]

hi,

I have to use uTP only, my isp seems to block my connections if i use tcp too. All is well this way but overhead is kinda huge. Is it any better in the alpha? (2.1)

I'm fine with this anyway, just asking. (by huge i mean around 30% or more sometimes)

thanks.

[rafi]

Nope. 2.1 has the same uTP code. I confirmed this long time ago. It seem to be by design. Some tweaks are in my sig, but are mostly ineffective.

[fowl]

"Transferred last 31 days" in statistics dialog is actually showing downloads (what I selected in transfer cap).

[2010-05-20 02:02:07]  Banned 85.241.123.29:52711: [µTorrent 2.0.1 (100.0)]: -UT2010-0K%7c%3c7%d4%26%d3%1f%b5z%92 (448 kB downloaded, 64.0 kB bad)[2010-05-20 02:09:45]  Banned 75.110.149.140:25823 [uTP]: [µTorrent 2.0.2 (100.0)]: -UT2020-%c0L%b8%b8W%2f%ee%2a9%ef%ec%0b (80.0 kB downloaded, 64.0 kB bad)[2010-05-20 02:10:03]  Banned 143.167.185.128:58825: [µTorrent 2.0.1 (100.0)]: -UT2010-0K%c7%a8%f0b%3asP%c1%d5X (960 kB downloaded, 64.0 kB bad)[2010-05-20 02:11:57]  Banned 74.89.102.136:55076 [uTP]: [µTorrent 2.0.1 (100.0)]: -UT2010-0K%c6%cfE%22%3b%9e2%cf-%ba (5.18 MB downloaded, 64.0 kB bad)[2010-05-20 02:14:22]  Banned 124.170.93.223:34568 [uTP]: [µTorrent 2.0 (100.0)]: -UT2000-8H%d3%3f%c6bA%e5%a4%b8%d2%25 (3.75 MB downloaded, 64.0 kB bad)[2010-05-20 02:16:21]  Banned 92.0.37.169:42615 [uTP]: [µTorrent 2.0.1 (100.0)]: -UT2010-0K%a0g%2f%0c%9d%f3%c2%ab%d1%bd (10.6 MB downloaded, 96.0 kB bad)[2010-05-20 02:16:28]  Banned 212.24.173.242:50855: -UT2000-xGNK%91%dcT%d8%adR%a1%20 (240 kB downloaded, 64.0 kB bad)[2010-05-20 02:17:21]  Banned 82.18.98.61:1887: [µTorrent 2.0.2 (100.0)]: -UT2020-%c0L%3e%bb%f2v%5d%f3%f7%aa%ef%c9 (416 kB downloaded, 64.0 kB bad)[2010-05-20 02:22:53]  Banned 86.160.170.157:23642 [uTP]: [µTorrent 2.0 (100.0)]: -UT2000-8H%a1%11%b1%d2%c2%0f%07%12%e3%88 (336 kB downloaded, 64.0 kB bad)[2010-05-20 02:23:27]  Banned 94.6.51.145:33097 [uTP]: [µTorrent 2.0 (100.0)]: -UT2000-8H%c6%e5%92%97g%25%b8SJ%12 (80.0 kB downloaded, 64.0 kB bad)[2010-05-20 02:31:21]  Banned 94.21.116.3:54312 [uTP]: [µTorrent 2.0.2 (10.3)]: -UT2020-%c0L%11%28V%17%baE%ad%3d%07%de (688 kB downloaded, 64.0 kB bad)

Does this indicate some sort of spoofing or something? I didn't think anyone else had implemented µTP yet?

[mss73]

-- 2010-05-13: Version 2.0.2 (build 19648)

- Change: disable net.calc_overhead by default to improve speeds for users with low caps

if someone have channel 100 kb up and set 100kb up in uTorrent.

real speed will be 100 minus overhead

Plus! His browser (and other programs) will work very slow.

What improvement is there?

How this setting may improve speed on low channel? Fail.

[DreadWingKnight]

Idiot users were using 1kbyte/sec upload caps when their lines are capable of 100.

[Firon]

You can still turn it on yourself though.

[KSUdvm2b]

Something minor I just noticed with 2.0.2:

http://tinyurl.com/2abdu42

[ovejero]

Hi guys!

Has anyone noticed hash checking problems or is it something in my end?

[moogly]

Which hash checking problems? What's the error you see?

[rafi]

Given the info he gave us - it's surely something in his end

[heidelberg23]

You intend to fix this mess in the statusbar? This mess to manifest only at the local peers connections.

http://s55.radikal.ru/i149/1005/fd/e29931c8c00d.jpg

[DreadWingKnight]

Check with the russian translator.

[schnurlos]

@DWK, seems not to be a translation problem. If you select to see all info (D,L,O,T - U,L,O,T) as heidelberg23 does it, the place between the T (total download) and the U (upload) is cut.

[heidelberg23]

schnurlos, you are right - just a cutting problem.

[rlewis60]

does this apply to a mac?