gomp Posted September 25, 2008 Report Share Posted September 25, 2008 As topic says I was using 1.7.7 for weeks with no problems on router whatsoever, even under heavy conditions with max connections set to 500 and 20 upload slots.I upgraded to 1.8, the conditions were much lighter, only 4 upload slots per torrent (total 12 on 3 torrents), only seeding as I finished downloading so much less active connections. Upload also capped lower for good measure. Within 10 minutes the router crashed and rebooted itself, it then did it 5 more times in a row over the next 20 minutes before I stopped utorrent and investigated it. On the router I have now massively reduced the udp timeout for nat sessions, it seems on 1.8 udp nat sessions randomly shoot up to about 600 far exceeding my max limit set in utorrent which is currently now set to 75 per torrent and 150 global max. But thankfully now with my lower timeout (30 seconds) they also go down fast and the router has stopped rebooting.For good measure I tried out 1.7.7 again for a bit and the same thing doesnt happen.Any ideas? thanks Link to comment Share on other sites More sharing options...
DreadWingKnight Posted September 25, 2008 Report Share Posted September 25, 2008 Does 1.8.1 do the same thing? Link to comment Share on other sites More sharing options...
gomp Posted September 25, 2008 Author Report Share Posted September 25, 2008 I will see if I can manually fetch 1.8.1 was it released very recently? I only installed 1.8 yesterday, if I click check for updates it says unable to contact utorrent server. --update below--ok running latest 1.8.1 beta now and it still does it, I have tracked it down further its to do with dht network. When dht disabled it doesnt happen, dht enabled on 1.7.7 doesnt do this.this is stats from router with max connections set to 150 in utorrent. TCP : 56 sessions, Default Timeout 300 Seconds UDP : 504 sessions, Default Timeout 30 SecondsOthers : 0 sessions, Default Timeout 60 Seconds Total : 560 sessionsand this is after turning off dht. TCP : 62 sessions, Default Timeout 300 Seconds UDP : 18 sessions, Default Timeout 30 SecondsOthers : 0 sessions, Default Timeout 60 Seconds Total : 80 sessions Link to comment Share on other sites More sharing options...
Ultima Posted September 25, 2008 Report Share Posted September 25, 2008 Just leave DHT disabled, I suppose. DHT has always caused this...(Is your firewall allowing µTorrent 1.8 to send UDP packets, but blocking 1.7.7?) Link to comment Share on other sites More sharing options...
gomp Posted September 25, 2008 Author Report Share Posted September 25, 2008 well initially the port was only forwarded for tcp on both 1.7 and 1.8, after I seen the problem I then changed the forwarding for udp and tcp but it didnt change the behaviour at all, no firewall is blocking utorrent it has full internet access. The check for update works now in 1.8.1 if I understand right my nod32 broke it in 1.8. Link to comment Share on other sites More sharing options...
Firon Posted September 26, 2008 Report Share Posted September 26, 2008 NOD32 IMON should be disabled even if you update to the newer version. It has the potential to break HTTP in any application. Link to comment Share on other sites More sharing options...
gomp Posted September 27, 2008 Author Report Share Posted September 27, 2008 that would mean I need to enable amon, which of course scans everything I do and is a bigger performance hit. Link to comment Share on other sites More sharing options...
Firon Posted September 27, 2008 Report Share Posted September 27, 2008 Or just use it as an antivirus only. If you want a firewall, then get a real one, like Comodo. Link to comment Share on other sites More sharing options...
leeannejane33 Posted September 27, 2008 Report Share Posted September 27, 2008 ive been having no speed at all for last couple days.... i even tried deleting utorrent and reinstalling it and still no joy..... sum one on here said to set my speed at xx256 which i did and still no joy.. i had great download speeds last week which i could do a film in a day...... any ideas wats gone wrong Link to comment Share on other sites More sharing options...
Switeck Posted September 27, 2008 Report Share Posted September 27, 2008 leeannejane33,Your ip maps out to an AOL proxy. uTorrent cannot use generic web surfing proxies.And if that's not the cause...Your real ISP (the one AOL gets internet access from) probably started disrupting BitTorrent traffic in your area. Link to comment Share on other sites More sharing options...
gomp Posted September 28, 2008 Author Report Share Posted September 28, 2008 good god dont reccomend comodo haha, that is so bloated and intrusive every machine I have put it on has had problems galore.nod32 v2 is a AV only, it is probably the most favoured AV ever to exist due to it been light and not bloated.If I am honest utorrent is the only app I have ever heard off been broken by imon (in compatible mode). Is there an explanation as to why 1.7 had no problem but 1.8 does? Link to comment Share on other sites More sharing options...
thelittlefire Posted September 28, 2008 Report Share Posted September 28, 2008 It was broken. That's why it's on the http://utorrent.com/faq.php#Incompatible_software list... at least with 2.7 Link to comment Share on other sites More sharing options...
Firon Posted September 28, 2008 Report Share Posted September 28, 2008 IMON corrupts HTTP requests that are split up into multiple socket calls. It's a very nasty bug on their part.Comodo is fine as a firewall. The Defense+ function is a bit annoying (generates too many popups), but it can be disabled. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.