Search results
Results from the WOW.Com Content Network
Well, here's an update. I managed to get Transmission back to version 2.2 and get my torrents back fastidiously (it took me over an hour to copy almost 450torrents )copying them one by one from the Application Support/Transmission file that was on my Desktop, because the newly created one, was empty of course.
Transmission version 3.0.0 (bb6b5a062e) I've been using Transmission for a while in different OS's, but just got this one installed and it's not acting properly. I usually just use magnet links to add a torrent, although I tested it out by downloading a torrent file and adding it to Transmission manually and got the same result.
I just installed transmission on a sheevaplug and the download speeds are very slow. Even a ubuntu download which usually downloads at close to 2 MBits with utorrent is crawling at 50 - 100 KBits. When I test the network port using transmission gui, it reports that the port is closed. The ports are forwarded on the router.
3) Once having bound Transmission to my VPN, I'm unclear how to route the rest of my traffic "out" through my regular ISP''s IP. When I set up my VPN using OS 10.6.8's native client in System Preferences, under Network > [my vpn] > Advanced > Options, I was instructed to check the "Send all traffic over VPN connection" box.
The only torrent file that I can find at all in Transmission is the one I already successfully downloaded. I've never added this new one before. Earlier today I was trying a different bittorrent program and got a similar message (but the program was buggy in general and I dismissed it).
Learn how Transmission supports IPv6 and how to enable it for better peer-to-peer communication. See the discussion and feedback from other users and developers on this topic.
I am also having this problem with magnet links; Transmission 2.51 (the current latest) and OS X 10.7.3. These links work perfectly well in µTorrent, but remain stuck at "torrent metadata needed" in Transmission.
A user shares how to fix the port closed problem for transmission-daemon on Linux by disabling IPv6. Other users comment on the solution and provide alternative methods.
The mods at the private tracker site itself say they are fine with the latest versions of Transmission so it's not like the client isn't compatible. Here's my setup: - Running Transmission 1.76+ build 9843 (latest successful artifact available from the nightly build page) - EDIT: I'm now using the 1.80b3 (9787) and it has the same issue.
mikelete wrote:Hi there, Is there any way to set the maxium simultaneous active downloads? This feature is really useful (essential, in my opinion).