DSM-G600, DNS-3xx and NSA-220 Hack Forum

Hi and thanks for all your work with auto and transmission KyleK!

Do you happen to know of a way to add torrents so they are "added as paused" using transmission-remote ?  (I realise there is an option to toggle new torrents as paused or not).  Just looking to do this to specific torrents.

cheers

@romanl, @zuluwalker:  Here is a nightly build that ought to fix the "tracker did not respond" issue. Please test and let me know how it works out.
Download: Transmission-1.83svn-test.tgz.

Others should stay away from this, it is untested and a very clean SVN version (e.g. it doesn't have external-done-command). Version 1.90 is expected for next week.

@KyleK
What is the implication of not having the "external-done-command"? Thanks for posting this, I will start testing it in a bit.

I still get "tracker did not respond" errors even with the 1.83 svn test build. I might as well go back to pre 1.8x since many private sites have already banned earlier 1.8x versions.

I'm hoping 1.90 will be more stable and have a lot of additional features too! :-)

Yes, I am running build 10157 and so far I am still experiencing the same thing. I have reinstalled it once more along with curl and restarted the machine to make sure I wasn't running the old one. If the problem reoccurs in the next few hours I will file a ticket with the devs to inform them of this issue.

Thanks for the help KyleK!

EDIT: Immediately upon restarting and running Transmission Remote GUI did I see that the same errors persisted. AFAIK this problem isn't manifested pre-1.83 so I'm sticking with an older version until the devs address the issue. I have no experience filing bug reports with SVN or any other versioning system but I will file a report on this.

Last edited by zuluwalker (2010-02-11 12:50:35)

KyleK wrote:

I'm not at home right now, so I can't look for the link, but it should be somewhere in this thread, a couple of posts above this one. It's still open, so just add that with the latest build you still see the problem.

The link you're referring to is: http://trac.transmissionbt.com/ticket/2854 - the same open ticket I reported to.

After 16 hours of seeding (130 torrents) on 1.83 svn test build there are no any red arrows.

Unfortunately, almost 24 hours after installation got a lot of red arrows.

All's okey) thanks!

Thanks for svn-test build. After 30 hours working all of 100 torrents are green and upload speed is maximum for tariff(~12Mbits). Big thanks, KyleK.

Last edited by Logrus (2010-02-13 10:17:01)

I am not having a an issue but I wanted to ask in case someone knows the answer....

I've noticed the settings.json file has a property "peer-port-random-low" with a value of 49152. 

However I noticed in my router logs that clients are connecting on ports below that number, for example a client would connect to my machine on port 4096 from 6881.  I would expect that wouldn't be any connections lower than 49152 or am I missing something?

I prefer to limit the ports because my router seems to manage the QOS better if I don't have the entire port range (0-65535) enabled which is what I am using now.  Previously I had the following port range and my router seemed to classify the torrent traffic lower than everything else but I would still see connections lower than port 49152 that would get the wrong priority.
49152-65535

To those of you who reported that the issue #2854 "Tracker did not respond" still persists with the test version I posted earlier this week, please read the latest comment on the Transmission tracker.

Try deleting your settings.json and set it up from scratch. It's a bit of work, but it might help.