Transmission kills my internet connection

[Skyros]

Hi, it my first time to use Transmission, i just upgrade my MBP to Leopard few days ago. i just use Transmission yesterday. Let me say something abou Transmission, it seem a promising torrent client, very nice UI, wont even suck all the bandwidth like Azureus do.

Anyway, this Transmission, the latest stable version cause my ATT 2wire router gateway to crashed and prompt me to reboot the system. so i thought it just the same thing as before, i had this kind of problem before, it not often, just once a month. so i reboot it and try again with transmission, and BAM it crashed my router again. i havent able to try the nightly build but will post the result if the same problem there or is solved.

Now im back to Boot Camp/UTorrent way. a sad panda i am. but keep up with the Transmission, it look great.

[Jethryn Freyman]

Make sure you've installed the 10.5.2 update for Leopard. Also, make sure that your connection limits (in Transmission's advanced preferences) aren't too high. 50 connections per torrent and 400 globally should be fine. If a connection limit of 400 gives you trouble, try 250, or lower if you still get trouble.

You could also try a nightly, at the moment they're very stable and fix an issue that the official 1.05 release had.

[Ideasite]

This problem happens with VIRTUALLY ALL peer-to-peer torrent programs. Unless an application can actively monitor and manage the NAT table in the router, the table will fill more rapidly with these programs than other types of internet applications just because torrent programs make many more connections at a time.

I have had luck reducing my connections as low as 40 and restricting total downloads to 1 or 2 at a time. DL speeds hit 1.7 meg on Time Warner cable.

Router manufacturers need to radically expand RAM for NAT tables because the technology used in torrent programs is certainly useful everywhere.

Until that happens, you might try flashing your router with after market firmware that has better NAT table management capabilities.

The Transmission program might be able to manage NAT table limits better using uPNP, but I'm not sure if NAT table features are a part of uPNP.

I have both an ADSL connection and a cable connection. The ADSL does not have any problems, but I think it's because the bandwidth is so much lower that the NAT table simply does not fill up.

That's just what I know from having used lots of different torrent programs on a Mac.

[Ideasite]

When my connection dies, I can still navigate the router admin pages and even reset the router with them, but it doesn't re-connect to the internet until I power down both the router and the cable modem.

I don't have access to the cable modem admin page(s).

I also read that manually setting the DNS IP addresses in the Mac fixes this problem - I tried it and it doesn't.

I also upgraded to the Feb 29th, 2008 firmware - still dies.

Unless there's a NAT table or some similar issue with the cable modem, I think the cable companies are deliberately messing with peer-to-peer traffic.

[Ideasite]

Bastards: http://alwayson.goingon.com/permalink/post/24687

[bikeham]

I get spinning beach ball lock ups all the time and have to hard reset my Mac (unheard of, shock, horror). It has happened with 1.04 through 1.06 and am using the nightly as we speak.

"Console Messages" conveys the following when I start Transmission:

15/03/08 5:14:01 PM Transmission[213] Can't open input server /Library/InputManagers/MagicMenuEnabler

After the crash, there are no clues in console messages.

Not sure if this is relevant but a cursory search of google tells me that InputManagers aren't supported in Leopard. Is this the achilles heel or am I barking up the wrong tree?

Time wounds all heels.

[santa]

First I would delete any input managers. See if that solves it. Failing that, delete the Transmission folder inside your Application Support folder and download a new Transmission application and try that from scratch. I recently had a situation where Transmission would hang my connection. The prefs or something in the support folder was corrupt.

[Ideasite]

Dumb question, but what are InputManagers?

[santa]

they are programs that install something that does low-level stuff and they can cause real problems. you'll have to google for meaningful information. I just know they are kind of like OS9 Extensions and they can be a source of problems. Look for any items in user/Library/Inputmanagers If you have such folder you have no Input Managers. If you have items in that folder remove them and all their components. Restart. See if by some chance they could be involved. It may be a long shot but anything is possible.

[bikeham]

My Inputmangers directory appears as Inputmagers(Disabled)

So I guess it is disabled.

I am having more success halving the connections limits as mentioned in a previous post, (thanks Freyman). Are they set too high when Transmisson is shipped?

But surely it is bad form for a program to lock the host computer entirely when there is a problem?

[Ideasite]

I don't have InputManagers either at the root level or in the Users' Libraries. I have connections set to a max of only 40 and bandwith throttled to half and it still crashes my router after about 15 minutes.

Interestingly enough, a Windows client on the same router NEVER crashes the exact same router with 200 max connections and set to full bandwidth.

The problem seems to be with the Mac

[bikeham]

I've never seen this happen with Azureus, but it happened twice today during a storm - the power went off and the two torrents I was downloading went back to zero size.

This shouldn't happen right?

[Qliphoth]

Im new to Transmission and running the latest version 1.74, on OSX 10.5.8, at first I thought it was a prob with my router(connected via airport), but just discovered that it is when T is on, that im slowly losing my connection, until it dies completely. Been hoppin around the forums, but havent been able to find a solution?? Any help would be appreciated.

Thanks

[patifr]

Dear all,

I've recently got the same kind of problems with Transmission 1.74 on MAC OS X 10.5.8. First time ever I was forced to make successive hard resets on my MAC!!!
Browsing various sites I found this way of fixing the problem:

- Log in as root on your MAC (be aware that the root user is not activated by default, so you may have to activate it
- Then see here : http://forum.transmissionbt.com/viewtop ... 345#p36753

And problem should go away..

[metaclam]

I don't think this is linked right anymore.

A few posts before where that links to is a post by parodyr involving modifying some system files. is that it? if so, would that also work on snow leopard?

this happens to me every time I start or start transmission & it takes about 1 min for inet connection to come back. annoying but i've got used to it now.

edit: never mind, yes, after reading more of that thread it is the suggestion by parodyr that is meant to be linked. just that link doesn't quite get there -- close though.