I'm happy to announce the release of Tranmission 2.71 for the 100, 200, 300 and 400 series in a CSI package.

This is a continuation (with his blessing) of Ger Teunis packages. Many thanks to him for the years of good work.

Many thanks also to Padavan for his LTU package. The fixes he discovered for the the socket read buffer size causing crashes with large transfers have been included in this package. Also some ideas for the startup scripts are his.

Installation instructions

---

Download the CSI package.

This package will work on the 100, 200, 300 and 400 series. You can install using CSI. Inside CSI click File -> Install from file and follow the instructions.

Upgrading from CSI versions from before version 2.42
You need to uninstall the old version first. Quite a few things changed. If you want to keep your torrents and stats copy these files from /share/Apps/Transmission/.transmission:
- resume/*
- torrents/*
- stats.json
Place them back to /share/Apps/Transmission/config after the installation.

How to use Transmission

---

Gaya interface (100 and 200 series only)
A webservice link will be automatically added on your NMT's webservices menu, called Transmission. Note that the webservice called Torrent is the old one and will not function.

Web interface
You can access transmission through your browser via:

Desktop
An excellent standalone program with a uTorrent like interface is transmission-remote-gui. Versions for all OSes.

How to report issues

---

If you have trouble installing or running Transmission please give me the content of these files in /share/Apps/Transmission (or Apps/Transmission on the network share, depending on how you reach those files). You can open the files with any text editor, when in doubt try in Wordpad (on Windows).
- .daemonresult
- .installed
- .setupresult
- daemon.log
Also report if they don't exist or are empty. These files might be hidden on your system. Make sure you've enabled to show hidden files.

Note that I do not develop transmission. I just assemble this package. Transmission issues should be reported directly to them. When in doubt whether it's a Transmission or package issue post here first.

FAQ

---

Q: How do I configure Transmission?
A: Many settings can be set using one of the interfaces that have been explained above. For the more advanced settings you can edit settings.json which is explained below.

Q: My download / upload speeds are slow or non existing
A: Please follow this checklist. Also don't be too quick to judge, give it a few days of experience.

Q: Where do I find the config file (settings.json)?
A: In Apps/Transmission/config/. Use an editor that can handle unix line endings (like Notepad++). Be sure to stop Transmission (from CSI) first before editing. Your changes will be overwritten otherwise.

Q: Why can't I edit the settings.json file? It is giving me a permission error.
A: Please make sure the daemon is stopped first (through CSI). This makes the config file editable again. If not, execute this through telnet:

Q: Where do I find an explanation of all config variables?
A: Here.

Q: How do I automatically unrar completed downloads?
A: After stopping the daemon edit these two settings in settings.json:
An example script has been made. This one is specifically made for Oversight but you can edit that to your liking.

Q: Why can't I download more than 5 torrents at the same time?
A: This is the new queue feature of 2.40+. Take a look a the download-queue-size in settings.json to change that.

Q: Does this package work for the [insert any player]?
A: I don't know. I don't own those machines, I work with the A-210 myself. If you have telnet and ftp access and some basic linux experience we can see if we can make it work. Please contact me by PM.

Q:Where can I find transmission-{create,show,remote,edit}?
A: Here. Select your release, then extras, then correct series. The 300 and 400 series is binary compatible with the 200 series.

Known issues

---

On the A-400 it has been reported twice that settings are not being saved. This could be related to either CSI or the NMT itself. See this thread.

There have been quite a few reports about freezes and crashes with large (100GB+) torrents. They do not seem to be related to Transmission directly as similar reports have be given when transferring large files over FTP. Lowering the nice value of the daemon might improve the situation.

There have also been reports with crashes and freezes with high speed transfers (over 12Mbit (1MB/s)) for the 100 and 200 series. This is a kernel/firmware bug. Try limiting the speed to see if this is the cause of your crash.

Possible issue: Padavan has uTP disabled in his LTU package. This might be because he has experience with high speed transfers causing issues with the UDP stack of the NMT. If you experience slow speeds, try disabling uTP and see if it improves. Report your experiences.

Changelog

---

Version 2.71-dath1 (21 October 2012):
- Upgraded to Transmission 2.71 (Changelog)

Version 2.50-dath1 (24 February 2012):
- Upgraded to Transmission 2.50 (Changelog)

Version 2.42-dath2 (12 December 2011):
- Start the daemon as the "nmt" user. Fixes permission issues
- Use NMT's tar to build package. Makes A110 tar happy.

Version 2.42-dath1 (17 November 2011):
- Upgrade to transmission 2.42
- Fixes for gayaui (rpc update, sort on ratio, harddisk free space)
- Include fixes for TCP receive window kernel crash
- Enabled uTP (uTorrent transport protocol)
- Make watch directory work
- Fixes to install and startup scripts
- One package for both 100 series and 200 series

MANY THANKS FOR THIS PACKAGE !!!

All 200 and 100 series users will much appreciate that.

Thanks!!!

I succesfully installed 2.42 on my a-110.
For now it is only seeding, i'll try to give some feedback in a few days.

I updated to this version and now cannot connect remotely

downgraded to 2.21 and it works perfect/

btw I have c200

Connecting remotely works fine with me.
are you sure you have set up portforwarding for port 9091 correct?


btw, my 2.42 has been running for 24+ hours now and it didn't hang.
i should say that i haven't been downloading, only uploading.

Update: I just started a few linux distros for testing purposes.
They can stay uploading untill they have a ratio of about 10

(11-18-2011 06:02 PM)Slevin Wrote:  Connecting remotely works fine with me.
are you sure you have set up portforwarding for port 9091 correct?


btw, my 2.42 has been running for 24+ hours now and it didn't hang.
i should say that i haven't been downloading, only uploading.

Update: I just started a few linux distros for testing purposes.
They can stay uploading untill they have a ratio of about 10

I never did portforwarding for any torrent clients, and it always worked for me

well
in my case (c200) its connecting properly, but download is very slow comparing to 2.21 and all is running slower on transmission remote via desktop

According to my experience with 2.30+ from LTU enabling uTP does slow downloads. Those who experience speed issues might try to disable this.

I'm haven't checked for download speeds (as it downloads my stuff by night anyway it doesn't matter that much).

I have µTP enabled on my A-110 and it works. It might not be the highest speed.
Transfers over µTP are working as i checked the flags and they have the T https://trac.transmissionbt.com/wiki/PeerStatusText

here some screenshots (not sure if the speed is my fault or on the other side)
my max upload speed is around 40-45kBps
http://slevin.no-ip.org/stuff/uTP.png
http://slevin.no-ip.org/stuff/uTP2.png

@ Roman_V_M

I think this is not issue in this release as 1st post clearly says:

Quote:Possible issues: Padavan has uTP disabled in his package. This might be because he has experience with high speed transfers causing issues with the UDP stack of the NMT. I'm interested in your experiences. Related to this might be the UDP buffer size error messages in daemon.log.

Hi!

Thanks for your work. It working fine
But i coudn't edit my password for the web ui.
How should i edit the daemon.sh to i can edit the setting.json?

(11-20-2011 02:17 AM)Blazs Wrote:  Hi!

Thanks for your work. It working fine
But i coudn't edit my password for the web ui.
How should i edit the daemon.sh to i can edit the setting.json?

stop transmission via CSI, connect to popcorn via telnet,
change file properties by chmod 777 settings.json, edit it on notepad++ or notepad2 to preserve linux line endings. After edit change back file properties by chmod 600 settings.json and restart transmission by CSI.

(11-20-2011 11:20 AM)lukjod Wrote:  

(11-20-2011 02:17 AM)Blazs Wrote:  Hi!

Thanks for your work. It working fine
But i coudn't edit my password for the web ui.
How should i edit the daemon.sh to i can edit the setting.json?

stop transmission via CSI, connect to popcorn via telnet,
change file properties by chmod 777 settings.json, edit it on notepad++ or notepad2 to preserve linux line endings. After edit change back file properties by chmod 600 settings.json and restart transmission by CSI.

It's not working after i start transmission and check the settings.json again with the text editor the user name ok but the passwork reset to original...


Thanks for your help!

Another question
All files downloaded but new transmission seems to have read only parameter and I cannot remove it or rename after download easily by network share without command chmod
Can this be changed by some option in settings ?