Transmission

What I did next was try a different torrent client, quite a few actually, and not without a few more problems, detailed here: http://forum.utorrent.com/viewtopic.php?id=62224

I'm pretty sure, now I've got everything running okay with this different client that when I run Transmission again it will ...

I've tested the same file download from the Pi*ate b*y, with a different torrent client, offering a ratio of 1.5:1 in terms of bandwidth UL/DL ratio and this has stalled as well, but at around 40% of the file instead of 62% of the file. So this problem is essentially a tracker problem, in my view ...

Although I've set my preferences for a seeding ratio of 1:1, as reported earlier, the algorithm used by either Transmission or the trackers is designed only to deliver DL when UL bandwidth ratio exceeds a 1:1 parity or run to a stall. This drops the tracker into 'suck mode', where its only ...

I'm downloading a smaller file this time, 1.87 GB, and it has run overnight okay with no interrupts to download due to loss of internet line. I noticed I'd forgotten to run Lighthouse scripts to keep the port open so I started it up this morning with Transmission still running. Within two minutes I ...

Thanks for that, I suspected that it was something like that but I didn't know what, exactly. Anyway, it finished off DL pretty well okay this morning, without the wrinkly-eyed spaghetti-western stand-offs, before the shooting starts. I did have an external line interrupt - not just loss of my ...

The problem that |'m now getting relates to the tracker getting ahead as reported in this thread: http://forum.transmissionbt.com/viewtopic.php?f=1&t=8624
Once in this position, if you set your upload rate to zero - in line with a 1:1 parity ratio - the tracker progressively reduces download until ...

Thanks. I've also found a seeding level in the inspector window, which I had set to global rather than seed to ratio, so I've changed it to ratio. But again, perhaps as you say the option may not work until I've got the file, which I'm still some way short of yet. Anyway, I'll watch the tracker ...

Under Preferences>Transfers I've set my automatic stop seeding ratio to 1.0. I'm downloading a 5.8GB file and according to the statistics window I've uploaded 5.89GB and only got 3.6GB back. In the inspector window, I have 4.55 GB (only 3.19 verified), I've only downloaded 3.58 GB, I've uploaded 5 ...

When I was doing my router thermal tests, detailed in this thread: http://forum.transmissionbt.com/viewtopic.php?f=1&t=8054#p40292 I did have a problem with toolbar button confusion, which happend at about 2:30 am in the middle of some other tests that I was preoccupied with. I wanted to pause ...

And a few others too:

Sep 10 08:40:22 Macintosh-2 Firewall[41]: Stealth Mode connection attempt to TCP 192.168.2.2:64351 from 213.123.84.246:80

Sep 10 08:40:22 Macintosh-2 Firewall[41]: Stealth Mode connection attempt to TCP 192.168.2.2:64352 from 217.163.21.36:80

Sep 10 08:40:22 Macintosh-2 ...

Further observations:

Don't know if this is related to the network drop-off problem but a bunch of organisations are trying to strike up stealth mode port connections to my computer whilst I'm downloading this file - from the following IPs:

Sep 9 10:35:28 Macintosh-2 Firewall[41]: Stealth Mode ...

Just a quick follow-up note. On the second day of this second run I found my router had dropped off again over night, so I could buy a new one or fix this one. I thought I'd have no guarantee that a new one would have any better thermal performance or constant duty cycle, so I decided to fix mine ...

Second Run - 5.8GB file, so not quite as optimistic. Off to a pretty slow start with no thermal saturation issues. Port open and hard-wired. I swapped ports a few times early on but it made no difference. Low DL rates at the beginning - 0.07KB/s up to 1.5KB/s and meandering around these low levels ...

Conclusion: hardware thermal saturation

I suppose I should clarify some of the above reported problems to help others who experience the same problem. The problem I've described above was 'thermal saturation' of the hardware I was using and is not, I believe, a specifically software problem for ...

I've had a stab at a bug report for you. Sorry if its in the wrong place, but it does relate to this thread. I hope some of my comments are of some use.

Cheers

=======================================================================================================================

Not Downloading ...