Outline ·
[ Standard ] ·
Linear+
P2P µTorrent Thread, version 3
|
eq8all
|
Sep 5 2008, 02:52 PM
|
|
QUOTE(fatboythin @ Sep 5 2008, 05:36 AM) Yup, its the same port, 27220. Try 57220 instead and uhh I've noticed in 1 of your screenies specifically on the DNS settings part. I'm not sure it's a good idea to fill in there with the same IP as the default gateway. Either you put in screamyx's, opendns etc or your ISP's DNS. This post has been edited by eq8all: Sep 5 2008, 02:53 PM
|
|
|
|
|
|
eq8all
|
Nov 27 2008, 07:31 PM
|
|
µTorrent 1.9 Alpha Build 13520Test features' details:- » Click to show Spoiler - click again to hide... « What is not in 1.9:UDP hole punching (yet?) UDP tracker What is in 1.9:uTP, the micro transport protocol. This UDP-based reliable transport is designed to minimize latency, but still maximize bandwidth when the latency is not excessive. We use this for communication between peers instead of TCP, if both sides support it. In addition, we use information from this transport, if active, to control the transfer rate of TCP connections. This means uTorrent, when using uTP, should not kill your net connection - even if you do not set any rate limits. What was in 1.8.1:uTP, but connection attempts were not initiated by default, and there was no control over TCP as described above. You can enable it, but likely you will see the uTP connections not transfering much data, because they are pushed out of the way by TCP. What this means for rate control:You are still free to set rate limits and use external limiters. The "Automatic upload rate" control is flawed enough for most people that it will likely be removed once uTP is well tested and deployed, since it entirely supercedes that feature. How to enable and disable it:Preferences > Advanced, set bt.transp_disposition to: 255 - both TCP and uTP (default) 10 - uTP only 5 - TCP only http://forum.utorrent.com/viewtopic.php?id=49813&p=1 by Firon @niksus: It basically lays BitTorrent on top of UDP, which provides for better flow control, no TCP RST packet attacks, and probably other stuff I'm not thinking of off the top of my head.
@Klaus: uTP has been in the works for a long while now, and parts of it have made their way in to previous versions little by little. Whether that explains what you're seeing, I don't know, but uTP (at least in its current, now mostly-complete, and actually actively enabled form) is new to 1.9.Last edited by Ultima (µTorrent forums/Announcements today 06:43:33) Was about to reply to the other thread that asks for settings but I figured it'd be a bit more proper to respond here. Here are the thumbs, step by step from L-R and pay attention to the details you're familiar or are having trouble with. Sorry I didn't know of any other better way to arrange these to save space. It's a new alpha maybe going to beta phase. Mr.TS might wanna rework the thread's subtitle.       I run this on my Win XP Pro SP3 comp. tcpip.sys patched and paired with Peerguardian 2 and cfosspeed. As pictured, I left Preferences > Advanced, set bt.transp_disposition to: 255 - both TCP and uTP (default), which pretty much means it's by default. This post has been edited by eq8all: Nov 27 2008, 10:19 PM
|
|
|
|
|
|
eq8all
|
Nov 28 2008, 08:51 AM
|
|
@AskarPerang Screenie of which one (settings)? We'll need more specifics.
Btw this is a caution to those looking to test out the alpha build. You wouldn't wanna fall back on the build for proper runs other than just minutes to post the logs back or report other findings to µT's forums. This is because currently it'll generate a rather suspect and a whopper 88MBs for utp.log alone for anything that exceeds a 1 hour run. Plus if you fiddle to look at the logs while the client is running be prepared to crash it.
This post has been edited by eq8all: Nov 28 2008, 08:54 AM
|
|
|
|
|