Transmission disconnecting internet?

[timelawd]

This is just an innocent and naive question (maybe stupid):

Is there a possibility that Transmission could be the cause of my DSL modem/router getting disconnected from Internet access (not DSL, just Internet) ? It happens from time to time.
I noticed it happening three times after the last download was completed (seconds after the "downloaded" sound) and Transmission was only continuing to upload/seed. The other disconnections I only noticed when returning to my desktop after several hours of coffee break.
I used Transmission for two years now and am using 1.91 at the moment. Had no problems up until 4 days ago.
I called my service provider. Nothing wrong on their side.
My router/DSL (THOMSON ST585i v6) is directly connected to my Mac via Ethernet and UPnP is enabled. Transmission shows port always open.
As Transmission is almost always running, I can't be sure if it is the culprit. Even though the, few times it wasn't active, I had no disconnection.
This isn't a huge problem, but unfortunately, when disconnected it takes at least 20 minutes to have a new Internet connection.
Please let me know if this is a possibility and whether you know what could be wrong (with me).

Thanks a lot for reading me.

Transmission team, keep up the good work. Thanks a lot for the great app.

[Ranko]

I have a similar, but not exactly the same problem, my modem, on random occasions, will simply freeze entirely. It will stay frozen for 5-10 minutes before warm re-booting on it's own.

I know Transmission is the culprit, as it will not crash as long as Transmission is not running, but I cannot conceive HOW it can do this. Unless it's some memory buffer issue in the modem's firmware.

[Ranko]

Tried that x190, my normal settings are 40u/400d, and I reduced them to 10u/10d, still crashes the modem at random.

[jeff]

Transmission is likely overwhelming your router's NAT tables. Reduce the number of peers in Transmission's preferences and it'll likely fix it.

[Rezz]

I've had the same problem. Definitely Transmission doing it since it only happens when Transmission is running. What would you recommend the peers setting be set at? I've got it at whatever the default is at the moment. Has the peer fix worked for those that have had the problem?

[metaclam]

>If you need more peers for a particular torrent, stay within global limits.
>At least one forum poster has indicated his router could only handle 70 connections for bt.

Are you suggesting that some torrents will connect to more peers than the global limits? When would it ever not?

And I'd like to really control these global limits, while allowing new torrents I create to actually start seeding and automatically stopping others. But transmission doesn't ever start any torrents if you set the number of max active transfers. They always just say waiting to seed.

[Rezz]

Here's the numbers I have used with no problems for over 18 months. Results may vary by router.

100 global/10 per torrent/10 max active torrents.

>If you need more peers for a particular torrent, stay within global limits.
>At least one forum poster has indicated his router could only handle 70 connections for bt.

Thanks x190. I'm going to give that a try and keep my fingers crossed.

[Rezz]

Looks like that did the job. At 100 global it was a vast improvement but I still did get a couple of disconnects. I decided to try Global at 70 and since then, no disconnects at all. Thanks again x190.

[Rezz]

Sure thing. I'll check back in a couple weeks and let you know.

[metaclam]

I'd still like an answer about "max active torrents" setting. Setting that to 10 seemed to help. but it was useless because torrents i created never started, while torrents "seeding" but doing nothing (0% transfers) kept "seeding" anyway. I wonder about what effect those hundreds of "seeding" but not active torrents do to these router-tables?

I had global limits set well below 100 -- more like 30.

I have not used transmission in a few days now and my internet connection is zippy and alive. Be nice to be able to use it again, but that issue seems like it needs to be fixed.

[metaclam]

Queueing, I found, is tricky and you would need to experiment with settings. I find it much easier to manually pick and choose the torrents I want active. My opinion only.

I really appreciate your involvement in these forums, x190, so don't get me wrong. But that's exactly my point in harping on this. I'm not about to manually manage 500+ torrents on any regular basis. It should be obvious that home routers generally can't cope with lots of connections, and none of us cheapskaes is about to go invest $500+ in a commercial router.

So a good torrent client has to not only really respect the settings you make and never exceed them, but smartly manage what torrents connect within those set limits.

My question about whether those "active" and "seeding" but not transferring torrents could be causing problems goes unanswered still. I can only stress that there should be a way for an infinite number of torrents to be "seeding" but idle (i.e., available), and only start transferring when higher priority torrents (ones you seed, ones on preferred trackers) are idle. Then they should pause when those priority torrents need the connections/bandwidth to upload. Those seeding-but-idle torrents shouldn't be eating connections. I don't know how it works, but presumably they have to listen to requests periodically. OK, so let one "listen" in turn every X seconds. You see what I'm on about, I hope.

[rlinsurf]

I have further to this. I have been posting a similar experience here:
http://forum.transmissionbt.com/viewtop ... 489#p46489

To put it briefly, simply using TR seems to bring all other internet services to a halt, even when DHT is disabled, peers are <100, and when all downloads/uploads are 0.0k. When TR is quit, all services return.

Here, it has been suggested that a single .torrent might be the culprit. I now have confirmation of that effect. Previous to adding a single torrent, my internet and all services, including BT, were operating normally, it was only after the addition that the services failed. When the torrent had finished, and removed it from the list, all services returned pretty much immediately.

If any of the Transmission Team would like to see the .torrent, please PM me to upload it to you.

[rlinsurf]

And a bit more. The 2 other files which I had been downloading previous to adding the trouble file had been showing some progress, then fell to 0 shortly after the add. I thought it was simply coincidence. But I've now noticed that both files have started downloading again, shortly after removing the offending file.

[Rezz]

Hello all, It's been almost two weeks now since adjusting my settings and I've had near perfect results once I got the right settings. The settings that work for me are Global peers set at 70. At 100 I got far less disconnects but still got a couple a day. Since my last post I've had it set at 70 Global and 20 for new transfers and I have had only one disconnect but I'm fairly sure that was unrelated to Transmission. In any case, one disconnect in nearly three weeks. Not too bad.

My modem is a DSL Speedstream 5100 on a eMac OSX 10.4.11, power PC G4. The transmission version is Mac 1.54 (8615).

[Inuyasha]

Transmission hammers the read and write cache which causes the RAM to get eaten up and it destabilizes OS X, but that's SNAFU. But watching the error logs, the problem just gets worse until the networking stack crashes along with any I/O operations. It's very obvious because the hackintosh I use now has a very slow IDE hard drive that's easy to overload, but I've seen the networking die on my Mini and PowerBook too. Might not be the exact same problem as everyone else but it sure matches the title