µTorrent downloading/uploading when I have stopped/completed...

[Panarchy]

Hello!

I have an important question to ask.

With µTorrent, for some reason when I open µTorrent (and I have all the torrents, either stopped, or completed and then stopped [so that the green tick appears]) my µTorrent continues to download & upload (seed)?

Please tell me how I can fix (stop this from happening) this,

Thanks in advance, please reply,

Panarchy

[DreadWingKnight]

http://utorrent.com/faq.php#Why_does_it_show_download_speed_when_seeding.3F

http://utorrent.com/faq.php#What_is_DHT.3F

[Panarchy]

Thanks.

Can I disable this somehow? Because if I leave µTorrent open, even when without anything downloading/seeding (everything either stopped, or stopped after completed) it doesn't need to get info on peers, because;

1. I don't host any torrents

2. I'm not currently downloading or uploading anything

Please tell me how to do this,

Thanks in advance,

Panarchy

[DreadWingKnight]

DHT doesn't care what torrents you have active. If there are torrents active somewhere, even if you aren't running them, there's info that needs to be stored about them.

If you don't want this, you need to disable DHT in your preferences.

[docski]

i downloaded a program but i cannot open it. do i have to download a program to open it.

[DreadWingKnight]

docski, your issue is not related to uTorrent.

Once uTorrent says the download is complete, our support ends.

[Panarchy]

But, docski, make sure you have done Force Torrent Re-Check thing, it might not be complete. That has happened to me before.

DreadWingKnight, thanks for telling me what DHT is and how to disable it.

I will do so.

Thanks,

Panarchy

[Calamity]

Just a little friendly advise Panarchy, but I wouldn't wanna do that if I were you.

I mean it's still your decision and I'm not telling you what to do here, but globally disabling DHT for all current and future torrent jobs is, AFAIC, unwise. DHT provides too many benefits than I can readily count right now. Just try Googling DHT for more information if you doubt my words. DreadWingKnight only suggested the steps on how to do it because you were asking him for that. But that doesn't mean he's recommending that you should actually do so. And I highly doubt anyone else here will, either. Unless of course, you are experiencing severe difficulties because of it.

And as I can gather from your posts, it's not really the case here. At worst, DHT only borrows a few bytes of bandwidth--sporadically. But so what? Even my old friend with a very slow dial-up connection doesn't even notice it. My unsolicited advise to you is this: Disable DHT as you see fit on a per-torrent basis. You can do this either before a torrent job starts (seeding or otherwise), or through its Properties dialog box when it's already active.

[Switeck]

If you're on dial-up, I definitely recommend disabling DHT for ANY torrent that already has more than 20 live connections (peers+seeds) on it.

If you are on marginal networking hardware and/or software (D-Link routers, wireless connections, USB modems)...then once again I recommend disabling DHT.

If all you ever download is popular torrents with over 40 live connections (peers+seeds) on it, then DHT will probably net you no speed improvement. On private torrents DHT is disabled anyway -- but the DHT network continues to run.

*IF* you disable DHT, then you don't need to forward UDP packets for µTorrent's incoming port.

I normally keep DHT disabled. My networking hardware and software gets a little unreliable with it enabled. (D/C's every few hours briefly)

I have used DHT to rescue a dead torrent that the tracker had long-since taken down.

The DHT format implemented in µTorrent has been criticized as both a "mess" and does not interface with Azureus' much larger DHT network...last I heard. This means just because µTorrent's DHT doesn't find more peers+seeds doesn't mean they're not out there.

Peer Exchange allows you to gain some of the benefits of DHT without paying the DHT UDP traffic costs. It reuses existing peers+seeds connections to ask THEM if they have any other peers+seeds they're connected to. This certainly helps ensure those peers+seeds are actually live. I wouldn't disable Peer Exchange whether I have DHT enabled or not.

[Calamity]

Hi, Switeck. I agree with your point about DHT having only nominal speed improvements--if any. And this is especially true in cases of narrowband and unreliable technologies (hardware or software).

But truth be told, speed improvements are not really DHT's biggest selling point for power-seeders like me. For us, DHT's ability to keep a torrent alive, kicking and seeding (almost indefinitely), is what keeps us coming back to it. Even the overhead it creates is just minimal on average, even on my friend's old dial-up connection as I mentioned before. But for a stable broadband setup (even on mid-range), it amounts to practically nothing!

Since I don't have first-hand knowledge of Panarchy's exact situation, I guess your advise may be more applicable to him than mine is. But I wanted to make it clear to everyone, that they shouldn't be too quick to write off DHT without factoring in its many practical real-world benefits first, for the short-term and in the long-run.

[Switeck]

So long as a significant fraction of people run it that CAN run it without problems, DHT will be fine.

DHT is enabled by default, and most people have neither a reason or knowledge to disable it.

I also get DHT info indirectly via Peer Exchange.

I will write it off personally except in spot cases until it's either more universal (LOTS of BitTorrent clients don't support µTorrent's DHT version...some have no DHT at all) or even less bandwidth using.

It's a personal preference currently IMO...which isn't the case for sharing if using BitTorrent!

[Calamity]

I totally agree, Switeck (even with your later points, to some extent). And I really appreciate your warning us, but if I were to truly take your reservations to heart, then the next logical step--for me and other DHT supporters--would be to abandon uTorrent altogether and replace it with another BitTorrent client that has "better" DHT.

Forgive me if I sound like a cheesy product endorser for what I'm about to say *wink*, but in my personal case--and perhaps in quite a few others I suspect--going with another BitTorrent client (with a "better" DHT-equivalent) is just not an option. Now I know uTorrent's DHT/trackerless implementation may not be perfect yet and it has its shortcomings--mostly in the "universal support" department--but then again, who doesn't have this problem? uT's DHT, despite its flaws, is still more than worth the trouble--on the whole. In fact, the reason why it sometimes sticks out like a sore thumb, is because of uTorrent's other qualities! *wink*wink*

Hehe, but seriously though, and I'm not just saying this because I'm one of those uT loyalists or fanatics or something--and I'm not--but for now, or until a MUCH "better" DHT-capable client comes along, uT is simply my only choice when it comes to BT software (and I've tried quite a few). And with uT, comes its still-nascent DHT implementation. So for better or worse, people like me are stuck with and just have to live with it. Sigh...

But in fairness, it is also true that not everyone is a believer in the benefits of DHT. In fact, some people I know downright hate it. A good example of this (besides private trackers, of course), would be some friends I know who simply don't want their torrents staying active for very long, claiming various reasons. None of which I can honestly agree with. But hey, it's a free country. :/

[Switeck]

I am only a downloader of EXISTING torrents from links on popular web pages...were I seeking new torrents with no web page to support them, then I certainly would use DHT (wouldn't have a choice really.)

It's simply a matter of numbers...Azureus's DHT still has the largest majority of "loose" peers and seeds to connect to, and µTorrent cannot access them directly via µTorrent's DHT. Likewise, there may even be the reverse -- µTorrent's DHT network may have peers/seeds not directly available to Azureus. This is mitigated by the use of Peer Exchange which *IS* fully supported by both (and other) clients. But even that will only help if both networks manage to find members in the other networks. You have to connect to at least 1 peer or seed to find any more via Peer Exchange...but DHT can start from nothing.

A major issue with DHT is say the files are identical in 2 separate torrents...1 is the full series and the other is just a single episode of it. Because the torrents use different piece sizes (such as 1 MB for the full series and 256KB for the single episode), there's not likely to be ANY sharing of information between the 2 torrents. Even if the 2 torrents had the SAME piece size, it probably wouldn't help unless the single file was the first file in the multi-file torrent. AFAIK, There's no "overall" file hash for a single file in a multi-file torrent unless it perfectly fits inside a single piece. (This type of scenario I've manually done myself...having downloaded a single episode earlier and adding it to a multi-file torrent -- so I have something to share when I start AND I don't have to download as much. This is probably the absolute limits of the ability and/or willingness of the average BitTorrent running person, IMO.)

Another case would be for 2 media files (2 torrents) which differ only in their MP3 tags...once again, probably no overlap can be found by DHT.

DHT won't (and shouldn't) find stopped torrents that someone has. And I don't know if it'll find queued or paused torrents either.

So this mostly leaves DHT for "public" torrents where the tracker is down or blocked, many of which the peers and seeds are either already connected to each other when the tracker goes down or forms a mini-seed network via Peer Exchange. As far as I know, µTorrent will continue retrying ips found in its Peer List for that torrent when the tracker is down/blocked, even if DHT *AND* Peer Exchange are disabled...and even do so for private torrents with the tracker down!

When my upload's already maxed out filling the demand of existing peers on the torrents I'm sharing, I see little need or desire to turn on DHT to see if I can find MORE hungry peers. I've gotten burned by getting more demand than I bargained for using other file-sharing networks and to a MUCH lesser extent running super-popular torrents while not firewalled...and don't want potentially 1000+ ips trying to connect to me at once. I call that a self-inflicted Distributed Denial of Service (DDoS) attack. I download torrents regularly that have over 1,000 peers+seeds on them...I'm not joking when I say this isn't just a minor issue. BitTorrent does an excellent job limiting outgoing connection attempts but only a mediocre job preventing incoming connection attempt overflows. Once your ip is sent via the tracker to many peers + seeds, they can exchange your ip via both DHT and Peer Exchange even if the tracker is told to no longer hand out your ip. Trackers are supposed to only hand out recently connectible ips, but many trackers hand out dead and firewalled ips.

It's not that I don't see the usefulness of DHT or even the necessity for many people to use DHT. I simply don't agree that almost everyone should have it enabled. I'm not even sure it helps firewalled people much if any...as I think you HAVE to be unfirewalled to even participate in the DHT network. And for a LOT of networking hardware and software, even DHT's low UDP packet rate is enough to make them slow down or crash. (D-Link and Belkin routers in particular!)

Come to think of it, even dial-up users (and me during DDoS attack-sized torrents) may be better off disabling Peer Exchange too if the torrent is busy enough.

[Lord Alderaan]

Instead try to realise the truth.

What truth?

There is no file.

A torrent is divided in pieces and not files. So you cannot seed one file in one torrent from another file in another torrent even if they are identical. You could theoretically seed a piece in one torrent from a piece in another torrent if they are identical but the likely hood of this happening if the full torrents aren't identical is virtually nil. And the extra programming and data exchange this would take to enable this on DHT or PEX makes it impractical.

I agree that in most cases DHT is virtually useless. In most cases people can get enough peers through the tracker. But it can really be a great help in rare occasion. And that is why DHT is worth it. Right now I can think of

* Public trackers going down (temp or perm).

* Torrents getting removed from a public trackers while there are still peers downloading.

In those cases DHT often allows you find new peers for or to resume (after a µtorrent restart or something) that torrent and.

[Firon]

When Demonoid was down, many torrents continued normally because of DHT.

[Calamity]

I am only a downloader of EXISTING torrents from links on popular web pages...

I understand. However, though I do download my fair share of stuff--God knows I do--I'm actually more of a seeder/sharer than anything else. I hope this somewhat helps in understanding my mindset and why DHT is so indespensable to me (and to like-minded people). It's also why I passionately advocate P2P like it's a religion, whether on the BT or the eD2K network.

It's simply a matter of numbers...Azureus's DHT still has the largest majority of "loose" peers and seeds to connect to

So true. Mass appeal has always been Azureus' greatest ally, DHT speaking or otherwise. But AFAIC, that's not enough to make me switch. Though I must admit, this fact alone has made me turn my head more than once.

Likewise, there may even be the reverse -- µTorrent's DHT network may have peers/seeds not directly available to Azureus. This is mitigated by the use of Peer Exchange which *IS* fully supported by both (and other) clients.

You'll get no arguments from me here. In my eyes, Peer Exchange is like DHT's baby brother. So using it, at least to me, is simply a given.

You have to connect to at least 1 peer or seed to find any more via Peer Exchange...but DHT can start from nothing.

Exactly. Just one of the reasons why I fell in love with it. Hehe.

DHT won't (and shouldn't) find stopped torrents that someone has. And I don't know if it'll find queued or paused torrents either.

Well I can't be absolutely sure of course, but from my personal experience, I think it does. As I said before, I seed/share like a nutcase. And no, I don't do it for the upload ratios/credits if that's what you're thinkin'! For me, it's really just a matter of principle. I guess you could say it's my own way of defying Big Brother; and of fightin' for the little guys. Oh great, now I sound like a superhero. But seriously though, I honestly and sincerely believe in the precepts of P2P, OpenSource and everything else that encourages freedom for all (okay, I'm gonna stop now). In any case, that's the reason why I almost never stop my torrents, they're either actively running or queued. "Why almost then", you ask? Well because I can't help it, if it's really dead. And by dead, I mean those torrents with no trackers, no Peer Exchange and--you guessed it--no DHT!

When my upload's already maxed out filling the demand of existing peers on the torrents I'm sharing, I see little need or desire to turn on DHT to see if I can find MORE hungry peers.

Well as I've said before, I don't really see it as a burden, at least to me. And it's not like I actually go lookin' for them. If there happens to be "hungry" peers trying to connect, I see no fault in helping them out IF I can do so. Yes, they could just be hit-n-runners for all I know, but it's their karma that's at stake, not mine.

...running super-popular torrents while not firewalled...

Then you are obviously braver than me. Hehe.

I simply don't agree that almost everyone should have it enabled.

Oh quite the contrary, actually. What I was encouraging, was that not everyone should be advised to have it disabled.

I'm not even sure it helps firewalled people much if any...as I think you HAVE to be unfirewalled to even participate in the DHT network.

Yes, it does work firewalls and no, you don't have to be "un-firewalled" to be able to take advantage of the DHT network. I use a combination of software firewalls (with ZoneAlarm Pro 7+ currently, and Sygate Pro before it) and my own BLM-compiled ipfilter.dat file (with PeerGuardian2 before it). Granted, they're not hardware security solutions (which is probably what you meant), but as you can gather from my continuing enthusiasm for DHT, I never had a problem, xDoS Attacks or otherwise.

And for a LOT of networking hardware and software, even DHT's low UDP packet rate is enough to make them slow down or crash. (D-Link and Belkin routers in particular!)

Well thanks for the tip then. Now I know what brands of equipment to never use. Haha.

@ Lord Alderaan:

...DHT often allows you find new peers for or to resume (after a µtorrent restart or something) that torrent and.

Exactly. Now I don't know what you mean by "a restart", but as long I've been using µTorrent and DHT, I've never needed a restart--ever. Not even when I need to reload an updated ipfilter.dat file I compiled using BLM. :/

@ Firon:

When Demonoid was down, many torrents continued normally because of DHT.

AMEN.

[Lord Alderaan]

I'll explain what I mean with the restart:

Tracker goes down. 5 mins later you close µtorrent. Now start µtorrent and it'll start those torrents again. However the tracker cannot be reached so you cannot get a list of peers. But through DHT you will be able to find peers to connect to and resume downloading (or seeding).

(Conveniently ignoring the fact that people will try to connect to you because they still have you in a peer list they got from the tracker when it was still online. However this effect would die out over time and this wouldn't matter at all if you are unconnectible.)

[Calamity]

Hehe, oh now I get it! You meant to say that--using DHT--you can continue a (trackerless) torrent in the event of a µTorrent restart or something similar (like a crash). Sorry, I misinterpreted your shorthand. I thought you were saying that you can do these things but only after a restart of µT has occured. Which led me to clarify that no such "event" need be invoked by DHT users. Well, no harm, no foul. I agreed with you anyway, so never mind.

In any case, my original points stand.

[Lord Alderaan]

I reinforced your point.

DHT is useless 95% of the but invaluable the other 5% which makes it worth it.

[Switeck]

"Well I can't be absolutely sure of course, but from my personal experience, I think it does."

I would be EXTREMELY WORRIED if DHT started uploading STOPPED torrents. That'd be reason right there to NEVER enable DHT.

I'd even be annoyed if µTorrent reactivates paused or queued torrents.

I stop torrents all the time because I don't have the upload bandwidth to upload more than a few at once. I have pointed out in other posts that a very low upload speed per upload slot on a torrent can be more harmful to the torrent swarm than totally leeching.

Another thing, I've seen innumerable posts about DHT not working because they didn't port forward UDP to µTorrent's listening port. A computer can have all kinds of routers and firewalls...but if they're all forwarded or allowing traffic, they are transparent and as far as µTorrent is concerned...µTorrent is NOT firewalled. Which is probably why it works for you.

[Calamity]

I reinforced your point.

DHT is useless 95% of the but invaluable the other 5% which makes it worth it.

That's correct. Your arguments were a subset of my arguments. And that is why I AGREED with you using the word "Exactly". You do remember?

As for DHT being useless 95% of the (time), well, without a scientific or statistical study of real-world DHT usage over a given period of time, I'm afraid I can only consider that as speculative, at best. In light of this fact, I can neither agree NOR disagree with your personal estimate of DHT's usefulness.

I would be EXTREMELY WORRIED if DHT started uploading STOPPED torrents. That'd be reason right there to NEVER enable DHT.

So we won't get into a cycle of misreadings, please let me clarify my statement by re-quoting our exchanges.

First you said:

DHT won't (and shouldn't) find stopped torrents that someone has. And I don't know if it'll find queued or paused torrents either.

So I responded with:

Well I can't be absolutely sure of course, but from my personal experience, I think it does. As I said before, I seed/share like a nutcase. And no, I don't do it for the upload ratios/credits if that's what you're thinkin'! For me, it's really just a matter of principle. I guess you could say it's my own way of defying Big Brother; and of fightin' for the little guys. Oh great, now I sound like a superhero. But seriously though, I honestly and sincerely believe in the precepts of P2P, OpenSource and everything else that encourages freedom for all (okay, I'm gonna stop now). In any case, that's the reason why I almost never stop my torrents, they're either actively running or queued. "Why almost then", you ask? Well because I can't help it, if it's really dead. And by dead, I mean those torrents with no trackers, no Peer Exchange and--you guessed it--no DHT!

As you can see, after I said "I think it does", I proceeded to explain what I meant by that, by first DECLARING that I almost never stop my torrents unless they're really dead (again, please read above to see how I define dead torrents). Then I added that my torrents are "either actively running or queued", again to DECLARE the status of most of my torrents. If it's still NOT clear enough, then let me elaborate on my original statement by "expanding" it below:

"I can't be absolutely sure if DHT can find stopped torrents--I wouldn't know, as I don't have ANY stopped torrents (what's the point of keeping (permanently) stopped or dead torrents anyway?)--BUT from my personal experience, I think DHT DOES find queued torrents--I would know, as I have LOTS of queued seed jobs."

In other words, when I stated "I think it does", what I meant by "it" are my queued torrents, NOT my stopped torrents, as I don't have those.

I'd even be annoyed if µTorrent reactivates paused or queued torrents.

Whoa there, hold on a second here. Now I don't see a problem with µTorrent "activating" queued torrents. 'Cause what exactly is wrong with that? Isn't that the whole point of being queued--in ANY queue? Being queued means you're next in line for "activation", sooner if not later. That's why you put them in the queue in the first place! If you don't want your torrents gettin' themselves "activated" by µT, then you shouldn't be puttin' them in the queue, at all. You can just pause or stop 'em. Now as for paused torrents, well who said anything about µT spontaneously reactivating them? I KNOW I didn't say that, 'cause I'd be annoyed too if that keeps happening.

I stop torrents all the time because I don't have the upload bandwidth to upload more than a few at once.

Again, I understand. And that is why I KEEP saying that a dedication to seeding is NOT for everyone.

A computer can have all kinds of routers and firewalls...but if they're all forwarded or allowing traffic, they are transparent and as far as µTorrent is concerned...µTorrent is NOT firewalled. Which is probably why it works for you

Now again, who was it that said that I allow ALL traffic? I don't need to allow ALL traffic just to be able to use µTorrent and its DHT capabilities. And as for µT not being "firewalled", if what you mean by that is that it's NOT being blocked by my firewalls, well of course it's not! Why in the world would I wanna do that anyway? The main purpose of firewall solutions (hardware or software) is to block UNAUTHORIZED or unwanted network traffic from coming in or going out. But since I DO want µTorrent's network traffic (including its DHT traffic) to continue going out and coming in (using its assigned ports, of course), why then would I wanna block it? And just because µT is unblocked--or unfirewalled as you call it--does NOT mean that my WHOLE computer is automatically unfirewalled or "transparent". In fact, it's sealed tighter than a submarine, and just as silent. All it means, is that my µT is readily accessible by other µTs (or other BT clients). Now, does that make µT "sort of transparent" to malicious entities masquerading as BT clients on the BT network? Well, everything's possible, of course. But this is true regardless of whether or not you use DHT! So if we then use your (security) rationale, that would make ALL µTorrent users "transparent". And that's forgetting about other clients.

In any case, that is where complementary security solutions like PeerGuardian or BLM's blocklists can lend you a helping hand, screening out many potential bad sources before they get a chance to get in. And if those aren't enough, and you're as paranoid as I, you can still enable µTorrent's own security measures (like its Protocol Encryption) that add additional layers of security (and privacy).

Now, before you claim that these solutions are "not perfect", let me say this first: Of course they're not! Is there a "perfect" solution out there that I haven't heard of? Even the Pentagon's bloody security couldn't be perfect. But nevertheless, just like theirs, my security is FAR from being "transparent". And it woks NOT just for me, but also for dozens of other seeder friends of mine. And I suspect the same for hundreds of other users as well, if not thousands. It's just very hard to believe that out of the countless µTorrent users out there, my friends and I are the only ones who have been able to find a way to make µT and DHT work successfully--and SECURELY at that.

[Switeck]

If I had a queued torrent spontaneously start itself up and then µTorrent queued up my downloading torrents BECAUSE someone found a torrent I had queued up...via DHT, I would be a bit pissed.

...or if µTorrent just started MORE queued torrents without queuing up some already-active torrents because someone found those torrents via DHT...I would be pissed.

If I had a torrent paused, and someone finding it via DHT causes my torrent to become unpaused, I would be very pissed.

None of those cases are examples where stopped torrents get started, but I included that as an example of something I would NEVER tolerate.

I don't know if it does those things, however I would consider every one of them to be undesirable if it did. You said you think it does at least 1 of those...Or I misunderstood you entirely.

It is precisely because I am trying to keep alive some older torrents that are a couple GB's in size that I don't want these things. If all of a sudden my upload speed for those torrents goes from >10 KiloBYTES/sec to less than 1 because of strange DHT behavior...yeah, I'd have a problem with µTorrent not doing what I want it to. And if I couldn't disable DHT, I'd be seeking a different BitTorrent client.

When I say µTorrent is firewalled or unfirewalled, I am generally talking about whether or not incoming connections MEANT for µTorrent (on its 1 listening port) are blocked or not. The computer µTorrent is running on is presumed to be firewalled from the majority of unsolicited internet traffic in any case, as just part of basic security. It is even possible for a computer to be PARTIALLY firewalled, where some incoming connections make it through to µTorrent...and some don't.

µTorrent can work behind a router's NAT. It can be software firewalled. You may never get a single incoming connection. But µTorrent can still work ok unless your firewall/s also block OUTGOING traffic too (outgoing traffic like web surfing for example). µTorrent will generally work better if it can receive incoming connections. (Except perhaps for my extreme "DDoS attack" examples, that is. And even then, the majority of the problems are caused by bad networking hardware or software. A good router might not crash from receiving 1,000+ connections in a minute.)

There are a LOT of posts of DHT not working due to firewall problems. The rest of µTorrent works ok. Some of these people even get incoming connections just fine. But DHT is firewalled...and thus blocked...possibly only because UDP wasn't forwarded along with TCP on their router. So I'm thinking that µTorrent can't be firewalled if you want DHT to work at all. And like it or hate it, if DHT is only supported by the fraction of BitTorrent users that AREN'T firewalled...that's almost certainly less than half right there.

BearShare had daily stats of all the connected nodes it could find. It showed typical firewalled rates at ~60% when the measurements were first started ...and over 70% about 2 years later. So only about 3 out of 10 people on the network could accept incoming connections. This was around 2002-2004 and on a different file-sharing style (Gnutella network)...however the numbers are still somewhat relevant because the same things that made people firewalled then are MORE prevalent now: routers, software firewalls, extreme settings, and even spyware/viruses! In BitTorrent's defense, I'd say you're FAR less likely to get a virus using it than from a general purpose file-sharing network like Gnutella. ...unless that's what you're seeking.

With more people on faster broadband than slower or dial-up now, I'd expect the conditions to actually accelerate. More people have multiple computers, and thus likely routers to connect all of them to the internet at once...or Windows Internet Connection Sharing enabled, which is a disaster in its own right. Some modems supplied by ISPs contain mini-routers and/or firewalls in them...especially the newer ADSL modems. Software firewalls aren't just dedicated firewalls like Zone Alarm and Windows XP SP2's firewall anymore. Antivirus and antispyware software are now including "internet protection" which is a software firewall in disguise, that most people don't even know exists -- let alone how to configure! A common misconception as of late was half open connection limit needed to be as high as possible to maximize download speed. If µTorrent's half open connection max is set too high, it can even cause firewall-like conditions -- or even system crashes. That may even be a major reason many people in the last year started posting here. Viruses and spyware can mess up a computer's networking so badly that appearing firewalled is the LEAST of the problems. =D

[Panarchy]

Well guys, I will enable µTorrent and have the upload limit on unlimited, DHD enabled during 'peak' time, as I am going to upgrade (within a fortnight) to a different ISP, which will upgrade my download/upload limit, from 12GB to 150GB. (for 4c more!).

And I will also get a speed boost! From 6000 to 8000 KB/s, too: 16000 to 20000 KB/s!

So this is one heck of a speed boost!

And thanks to the scheduling thing in µTorrent, I can enable it only from 1AM till 7AM! (My new ISP will be 110GB off-peak, but only 40GB on-peak!)

And I want to reserver the 40GB for downloading other things, like iso's and things from IRC.

And for using anywhere.fm to upload my music library to the internet!

Thanks µTorrent!

Panarchy

[Switeck]

Panarchy, as generous as your monthly bandwidth quota sounds...you'll probably need to limit your upload speed pretty low still to keep from overshooting it.

40 KB/sec all day for instance is over 3 GB.

~12 KB/sec all day is 1 GB.

[Panarchy]

Okay... thanks.

I will only put it on 20Kb/s.

Also, what relation does speed of upload and speed of download have in µTorrent?

Thanks in advance,

Panarchy