Jump to content

µTorrent 1.7 beta 2951


Firon

Recommended Posts

  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

Yes, it's normal when you're using DHT.

Hmm, correct me if I am wrong but of what I have read I understood it as DHT only made use of UDP, but the majority of these connections are with TCP?

I am worried as before testing uT I used Az and although I d/l with 300Kb/s and u/l 100 Kb/s I had no major problems to use Firefox and browse the web at the same time, but since I changed to uT I have started to experience browse problems, appearently because my router seem to timeout my outbound http requests. I even tried to use another computer on my private network to browse but I simply couldn't get out to the outside and a ping to my router gateway (internal or external) ip simply gave timeout.

Link to comment
Share on other sites

Even when you don't use DHT, there are still seeds+peers on the torrents you were on that have your ip and TRY to connect to it from time-to-time. These connection attempts may last for days...till you change your internet ip address that is! After 1 week's time, you should expect the random connect attempts to die down to less than 10 per minute.

Link to comment
Share on other sites

ok thanks for the answers. I am still bugged by though how this can be so extensive to the point of timing out my router - although uTorrent still seem to work fine. Well I will test a bit more now when both uT and Outpost have been updated to latest versions and see how it goes.

Link to comment
Share on other sites

Long time no post. Hope everyone is well.

Great update. So far we've only seen the GUI bugs that have been reported. Considering our work and need for security I think our network is a tad more extensive than the average home users depending on the office and chosen network. Sadly we actually have to have two offices. We'd never get anything done sharing a work and play space. ;)

So far my better (more techie inclined) coder half hasn't noticed the uPnP issues when using µT with the client/work paid network/connection (Cisco 1811W + a mix of Windows Server 2k3 & XP Pro) nor the personal network/isp (D-Link dir655 + XP Pro).

Will keep you guys posted if anything changes.

yettyn: Outpost

Not to start the battle of firewalls thread BUT I've used and ended my use of Outpost. It generally doesn't work well with various p2p protocols no matter how it's configured.

True.. it works well when browsing the net but I was never able to get top performance on any p2p network (including torrenting, emule, winmx, etc, etc) when using Outpost. P2P'ing w/ outpost has always resulted in high system resource usage.

You may wish to try another firewall. Avoid ZoneAlarm if you do. As that has been known to always be troublesome when using various p2p systems.

Keep up the great work.

Link to comment
Share on other sites

Well Outpost or not, it's seem very obvious though as soon as I launch uT I get problems to access anything with FireFox, even if I Paus all (4) torrents there is still problem but a tad better. Closing uT no problems at all. And I want to point out this also was the case before I started to use Outpost.

I just installed Outpost yesterday and before used just Windows own fw. I never saw this in any of the other clients I have tested (started out with BitTorrent and then changed to Az and now uT 1.7). It's possible Outpost give worse performance, but I don't think it's related to this. Unfortunately, if what you said is true, I took the offer (after hearing lots recommendations for Outpost) of a 3 years subscription ;-(

I am not going to jump off uT for this as I still think it's the best client (although I loved Az "Gaint Eye") but I feel there must be something wrong with this and if it's uT we want to solve it of course.

I have a 4/2 Mb connection, and have set uT with max 250 global connections and max 50 for each torrent, u/l 70 kb/s so I don't really try to squees the most of of it.

btw, I am not sure if this belongs to this thread, if not just let me know and I will open annother in troubleshooting or what would be suitable?

Link to comment
Share on other sites

> dont know if this has been reported before. in the add dialog of uT 1.7 build 1137, holding down

> shift key and select files won't do range selection like it used to be.

As others mention we are working on it; in the meantime though if you prefer the listview version better there is (as of around mid 1000 builds) an advanced option for that named "gui.addpre_uselistview".

Link to comment
Share on other sites

Well I might have found something here, but as I'm no network expert I am not sure. I though I should watch activity in Outpost to see what happened when I started uT and while it was running. I then noticed that it opened one port after the other and finally when I closed it (have to or I can't get here) it had opened more then 600 ports although there was only 60 connections. And it was not that 600 was a max or something, I just stopped it there. But before I stopped it I first Paused and then Stopped the torrents, one after one, assuming that would close down ports but not really. But that's maybe ok as after a while the counter started to decrease slowly... but it all sounds strange to me.

I figure that might was behind why I had problem to "wake up" my computer this morning, all ports was probably exhausted. Now I wonder, I read in the change log a "race condition" was fixed in 1137 (was running this morning), but I run 1170 now, can this be it still being an issue?

Link to comment
Share on other sites

Another bug?

I inserted a port number 52115 in connection settings and received this message in log:

[23:07:29] UPnP: Discovered new device: http://(IP deleted)/upnp/control?WANIPConnection

[23:07:32] UPnP: ERROR 401 mapping port 52116 -> (IP deleted)

[23:07:39] Unable to map NAT-PMP Port.

Link to comment
Share on other sites

I noticed for one of my torrents the value of "tracker status" column all the time jumped between different values like "working", "timeout", "hostname not found" etc. which made me look at the General tab. It showed the torrent was announced all the time to different trackers, so I opened the torrent file in my editor and found this on the first line

d8:announce41:http://inferno.demonoid.com:3401/announce13:announce-listll41:http://inferno.demonoid.com:3401/announceel30:http://tracker.prq.to/announceel40:http://tracker.bitebbs.com:6969/announceel45:http://www.torrent-downloads.to:2710/announceel42:http://denis.stalker.h3q.com:6969/announceel40:http://www.torrentrealm.com/announce.phpel42:http://tracker.torrent.to:2710/announceudpel36:http://tk2.greedland.net:80/announceel40:udp://tracker.bitcomet.net:8080/announceel47:http://tpb.tracker.thepiratebay.org:80/announceel51:http://tpb.tracker.thepiratebay.org:80/announce.phpel43:http://tracker.torrentbox.com:2710/announceel42:http://tracker2.torrentum.pl:6969/announceee7:comment1180:Visual Studio 2005 AiO (April 2007), 3 DVDs, En-US, all platforms.

also if I just start the other torrents and not this one, I have no problem to use my Firefox browser opening pages, but if I run this one = "goodbye to Firefox"

Now I wonder if this might be a specially crafted torrent, done just to cause problems or possibly to exploit this in uTorrent as I think this is what makes it crazy about opening ports until the system is haused.

the torrent was originally published at demonoid but I found it one mininova as I don't have an account at the former place.

Link to comment
Share on other sites

No it isn't quite how I thought, uT does open more and more ports all the time, however if just seeding the progress is so much slower. But eventually it has eaten all resources there is. Am I the only one experiencing this btw?

I don't know what is expected as "normal" for how many ports opened by uT though. They seem to be opened in sequence, one after the other, increasing range. I can't tell if it ever closes any ports, the counter jumps back 1 or a few steps from time to time, but it might be from other processes running as well. If I pause or stop the torrents it slowly starts to release ports one by one.

I am using the uncompressed 1170 btw

Link to comment
Share on other sites

ok found why not getting green light

private tracker problem

cause by port forwarding : if you look at logger you see that UPnP:descovered new device :http:/your route i.p :52869 <--- now i tried using incoming port 55555 and allow it in my route threw port ...load utorrent and it stil use port 52869 ..so i re-did route with port 52869 that worked

ok second i put in incoming port to 52869 ..in return i get UPnP :error 718 mapping port 52869 ...

still testing

Link to comment
Share on other sites

Hmm for me.. the UPnP is mapped but the NAT-PMP is unable to get mapped.. Dunno if this really affects much though..

[21:37:45] UPnP: Mapped port 35434 -> 192.168.15.100:35434

[21:37:50] Unable to map NAT-PMP Port.

And for me I always used Random Port, and usually did this by actually hitting 'Random Port' and never had any problems with it until I tried out 1.7.

So not too sure what is going on.. and yes I have done more auto/manual forwarding of ports to my router and never had any problems with 1.6.1, most came from the beta, and even when I revert back to 1.6.1 I get problems, so I sticking with the latest beta.

Link to comment
Share on other sites

yettyn,

Ok, the torrent tracker code you posted contains:

udp://tracker.bitcomet.net:8080/announceel47

µTorrent doesn't support udp trackers, so that alone may explain part of the problem.

Secondly, there is a few things in advanced settings that controls how FAST µTorrent makes new connections. They are probably set too high for your "slow" firewall program. Try reducing half open max and bt connect max.

Download/upload speeds aren't likely to be a problem so long as there's fewer than probably 60 connections TOTAL.

Link to comment
Share on other sites

DreadWingKnight

I forwarded ports by myself. In my router is also inserted port number 52115, so as in uTorrent. But uTorrent shows in the log port number 52116 and cannot map it.

[09:08:42] UPnP: Discovered new device: http://192.168.2.1:5440/upnp/control?WANIPConnection

[09:08:43] UPnP: ERROR 401 mapping port 52116 -> 192.168.2.101:52116

[09:08:52] Unable to map NAT-PMP Port.

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...