Archived

This topic is now archived and is closed to further replies.

Firon

µTorrent 2.0 beta 17539

Recommended Posts

I am still having an issue with WebUI with build 17341 where I cannot upload/add a torrent through WebUI. I am running latest wine and tried both versions of WebUI (0.361 and 0.362)

The last version where WebUI uploading works sees to be 17127.

Share this post


Link to post
Share on other sites

I'm experiencing an issue where my down speed drops (from 300+ kbps to under 20kbps) after a few minutes of active downloading. Stopping the torrent and starting it again fixes the issue, but only for another few minutes. The issue seems to only occur when NAT-PMP is enabled (logger says it fails to map the port using NAT-PMP, which is not unexpected on my network). I'm running 17341 on Win7 x64.

Edit: The problem still occurs without NAT-PMP, it just takes a bit longer (it could be completely unrelated to NAT-PMP, my experimentation hasn't exactly been methodical). This is a problem across multiple torrents, by the way. Stopping/starting the torrent restores download speed to 300+ within a few seconds.

Share this post


Link to post
Share on other sites

oblig: What does

Change: complete upload-only extension support

in the new build mean?

Specifically, what is the "upload-only extension"? Google returns this thread...

Ta.

I'd also note that this build is being pushed out by auto update, for those following along at home.

Share this post


Link to post
Share on other sites

80+ hours without crash! WOOOOOOOOOOOOOOOOOOOOOOOOOW! ITS a best bild of 2.X

i wold wont to sent a pie of cake for that to Mater ^)

sry for my eng )

Share this post


Link to post
Share on other sites

Any rough guestimates on when 2.0 will be out of Beta? I'm on too many sites that have it banned because it's not official yet. I'd really like to see how the UDP and uTP protocols are working.

Thanks!

Hmmm, guess I should have posted that in the v2.1 section? :)

(could a kind Mod move it over there?)

Share this post


Link to post
Share on other sites

You can enable uTP in 1.8.x, as well. It's just not on by default and doesn't have all the "tweaks" to it in the 2.0 builds.

Share this post


Link to post
Share on other sites

Ok, but not the same -

"1.8.3 has updated uTP handling code, so it can handle incoming uTP mixed with TCP much better. It is possible to enable outgoing uTP, but it is still not recommended, as the speeds will not be as good as 1.9 will have as we get closer to final."

Share this post


Link to post
Share on other sites

in 1.8.5 - just set advanced->bt.trans_disposition = 15 (for both UDP & TCP) and u r done...

Share this post


Link to post
Share on other sites

#1 in the "peers tab" - you see a [utp] notation #2 not available here... have to use 2.x

as they say - you cannot win them all... :)

Share this post


Link to post
Share on other sites

no. they are not supported only for the udp trackers. peers UDP connections are supported in 1.8.x

Share this post


Link to post
Share on other sites

@DeathStalker: in 1.8.x

If you want to use only uTP, set this variable to 10 (uTP connections) + 16 (new uTP header) = 26. Of course, you need to have a swarm with 1.8.x or 2.x peers.

You can use 10 too (uTP only but current header).

bt.transp_disposition: This option controls µTorrent's level of bias towards using TCP or uTP for transporting data (assuming the peer at the other end of the connection supports both transport protocols). The following is a list of the accepted values:

1 allows µTorrent to attempt outgoing TCP connections

2 allows µTorrent to attempt outgoing uTP connections

4 allows µTorrent to accept incoming TCP connections

8 allows µTorrent to accept incoming uTP connections

16 tells µTorrent to use the new uTP header. This is an improved communication header, but is not backwards compatible with clients that do not understand it.

This option is interpreted as a bitfield, so values can be added together to obtain a combination of behaviors. Setting this value to 255 guarantees that all behaviors are enabled.

Share this post


Link to post
Share on other sites

UDP tracker is only supported in 2.x versions.

You have to differentiate between UDP tracker and uTP (connections and new header).

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.