NSLU2-Linux
view · edit · print · history

Unslung.Transmission History

Hide minor edits - Show changes to markup

April 02, 2014, at 11:19 PM by SRS -- GUI sort selection fixes
Changed lines 85-88 from:

04/01/2014 A very good update to the remote GUI is ready:

http:// transmissionbt.net/Win_GUI-040114.zip (Windows ONLY) 04/01/2014

to:

04/02/2014 A very good update to the remote GUI is ready:

http:// transmissionbt.net/Win_GUI-040214.zip (Windows ONLY) 04/02/2014

April 01, 2014, at 04:08 AM by SRS -- GUI bug fix
Changed lines 85-88 from:

03/26/2014 A very good update to the remote GUI is ready:

http:// transmissionbt.net/Win_GUI-032614.zip (Windows ONLY) 03/26/2014

to:

04/01/2014 A very good update to the remote GUI is ready:

http:// transmissionbt.net/Win_GUI-040114.zip (Windows ONLY) 04/01/2014

March 26, 2014, at 03:15 PM by SRS -- New remote GUI
Changed lines 85-86 from:
to:

03/26/2014 A very good update to the remote GUI is ready:

http:// transmissionbt.net/Win_GUI-032614.zip (Windows ONLY) 03/26/2014

This newer one has enhancements and fixes over the older one. Recommend.

.

February 01, 2014, at 03:20 AM by SRS -- minor security and bug fixes
Changed line 27 from:

January 15, 2014

to:

February 1, 2014

Changed lines 48-49 from:

January 15, 2014

to:

February 1, 2014

January 15, 2014, at 07:42 PM by SRS -- bug fixes and new download link
Changed line 27 from:

December 2, 2013

to:

January 15, 2014

Changed lines 29-32 from:

http:// computerfixpro.com/transmission273p.zip

Enhancements to daemon and web client

to:

http:// transmissionbt.net/transmission273p.zip

For changes see:

Changed line 49 from:

December 2, 2013

to:

January 15, 2014

Changed lines 51-52 from:

http:// computerfixpro.com/transmission273p.zip

to:

http:// transmissionbt.net/transmission273p.zip

December 02, 2013, at 11:20 PM by SRS -- daemon and web client enhancements
Changed lines 27-30 from:

September 16, 2013 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.77+ (core) and 2.82+ (except rename)

to:

December 2, 2013 Download the pre-built .ipk from here: http:// computerfixpro.com/transmission273p.zip

Enhancements to daemon and web client

Changed lines 34-38 from:
to:

http:// github.com/cfpp2p/transmission/commits/master

all bug fixes and enhancements through current version 2.77+ (core) and 2.82+ (except rename)

Changed lines 49-50 from:

09/16/2013

to:

December 2, 2013

September 17, 2013, at 02:38 AM by SRS -- update 2.77+ core and 2.82+ bug fixes & enhancements
Changed lines 27-30 from:

July 12, 2013 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.77+

to:

September 16, 2013 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.77+ (core) and 2.82+ (except rename)

Changed line 44 from:

07/12/2013 v2.73+ r14074

to:

09/16/2013

Changed lines 71-72 from:

dont forget:

to:

don't forget:

Changed lines 85-86 from:

http:// computerfixpro.com/WIN_GUI.zip (Windows ONLY) 07/12/2013

to:

http:// computerfixpro.com/WIN_GUI.zip (Windows ONLY) 09/16/2013

July 13, 2013, at 05:18 AM by SRS -- Transmission 2.77+
Added line 44:

07/12/2013 v2.73+ r14074

Changed lines 46-47 from:

http:// computerfixpro.com/transmission273p.zip 07/12/2012 v2.73+ r14074

to:

http:// computerfixpro.com/transmission273p.zip

July 12, 2013, at 08:02 PM by SRS -- Transmission 2.77+
Changed lines 27-30 from:

12/27/2012 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.75

to:

July 12, 2013 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.77+

http:// github.com/cfpp2p/transmission/commits/svn/trunk

Changed lines 41-43 from:

reference: http:// trac.transmissionbt.com/ticket/532#comment:148

to:

reference: http:// trac.transmissionbt.com/ticket/532#comment:148

Changed lines 45-46 from:

http:// computerfixpro.com/transmission273p.zip 12/27/2012 v2.73+ r13646

to:

http:// computerfixpro.com/transmission273p.zip 07/12/2012 v2.73+ r14074

Changed lines 74-75 from:

Version: 2.42+-1

to:

Version: 2.77+-1

Deleted line 77:
Changed lines 81-84 from:

Here is a very very nice Graphical User Interface for transmission 2.42+

http:// computerfixpro.com/WIN_GUI.zip (Windows ONLY)

to:

Here is a very very nice Graphical User Interface for transmission 2.77+

http:// computerfixpro.com/WIN_GUI.zip (Windows ONLY) 07/12/2013

Deleted line 95:
December 31, 2012, at 07:39 PM by SRS -- Transmission 2.73+ optimized for NSLU2
Added line 42:

Download the pre-built .ipk from here:

Changed lines 45-48 from:
to:

you can review and/or compile the source code for the above at: http:// github.com/cfpp2p/transmission/wiki

December 27, 2012, at 08:34 AM by SRS -- Transmission 2.73+ optimized for NSLU2
Changed lines 25-30 from:

Transmission 2.42+

06/05/2012 NOW below is download for v2.52+

security patches and assorted bug fixes included

to:

Transmission 2.73+

12/27/2012 NOW below is download for v2.73+

all bug fixes and enhancements through current version 2.75

and optimized for NSLU2.

Changed lines 35-36 from:

both working very nicely, very stable.

to:

Working very nicely, extremely stable.

Changed lines 42-46 from:

http:// computerfixpro.com/transmission242p.zip 06/05/2012 v2.52 r13304

to:

http:// computerfixpro.com/transmission273p.zip 12/27/2012 v2.73+ r13646

Changed lines 48-49 from:

ipkg install transmission_2.42+-1_armeb.ipk

to:

ipkg install transmission_2.73+-1_armeb.ipk

or

ipkg install transmission_2.73+-1_armeb-pcTMP.ipk

June 06, 2012, at 02:36 PM by SRS -- v2.52+ with security patches included
Changed lines 27-44 from:

01/06/2012

below is fix for:

optware feed for Transmission 2.42 is NOT compiled with µTP enabled

(plus several other v2.42 bugs)

due to compile problems as evidenced by:

trac.transmissionbt.com/ticket/4560

trac.transmissionbt.com/ticket/4604

...take care of using the non-buggy version of autoconf to generate the official

tarball - the bug would affect all users cross-compiling transmission.

to:

06/05/2012 NOW below is download for v2.52+

security patches and assorted bug fixes included

also version for temporary pieces included

both working very nicely, very stable.

use the regular or the piece-temp, whatever you prefer

reference: http:// trac.transmissionbt.com/ticket/532#comment:148

http:// computerfixpro.com/transmission242p.zip 06/05/2012 v2.52 r13304

to install:

ipkg install transmission_2.42+-1_armeb.ipk

be SURE to include the .ipk else ipkg install will try to download it

you may need to:

ipkg remove transmission if there is a version conflict

Changed lines 59-91 from:

trac.transmissionbt.com/changeset/12954/trunk/configure.ac

also note:

https://trac.transmissionbt.com/ticket/4528

difficulties with compile fixed so here is transmission_2.42+-1_armeb.ipk

http:// computerfixpro.com/transmission242p.zip 01/06/2012 v2.42+(r13123) plus #4687

to install:

ipkg install transmission_2.42+-1_armeb.ipk

be SURE to include the .ipk else ipkg install will try to download it

you may need to:

ipkg remove transmission if there is a version conflict

.

to:
January 07, 2012, at 01:12 AM by SRS -- v2.42+(r13123) plus #4687
Changed lines 27-28 from:

01/06/2011

to:

01/06/2012

January 07, 2012, at 01:08 AM by SRS -- v2.42+(r13123) plus #4687
Changed lines 27-28 from:

11/19/2011

to:

01/06/2011

Changed lines 59-64 from:

http:// computerfixpro.com/transmission242p.zip 12/23/2011 v2.42+(r13113) bug fixes and some nice enhancements!

to:

http:// computerfixpro.com/transmission242p.zip 01/06/2012 v2.42+(r13123) plus #4687

December 24, 2011, at 02:10 AM by SRS -- v2.42+(r13113) bug fixes and some nice enhancements!
Changed lines 59-64 from:

http:// computerfixpro.com/transmission242p.zip 12/14/2011 v2.42+(r13112) bug fixes and some nice enhancements!

to:

http:// computerfixpro.com/transmission242p.zip 12/23/2011 v2.42+(r13113) bug fixes and some nice enhancements!

December 14, 2011, at 10:46 PM by SRS -- v2.42+(r13112) bug fixes and some nice enhancements!
Changed lines 59-64 from:

http:// computerfixpro.com/transmission242p.zip

http:// computerfixpro.com/trs42pwebclientfx.zip -- minor Web UI fixes 11/11/2011

to:

http:// computerfixpro.com/transmission242p.zip 12/14/2011 v2.42+(r13112) bug fixes and some nice enhancements!

November 21, 2011, at 07:30 PM by SRS -- fix for: optware feed for Transmission 2.42 is NOT compiled with µTP enabled
Changed lines 27-35 from:

optware feed for Transmission 2.42+ not occurring perhaps compile problems:

https://trac.transmissionbt.com/changeset/12954/trunk/configure.ac

and

to:

11/19/2011

below is fix for:

optware feed for Transmission 2.42 is NOT compiled with µTP enabled

(plus several other v2.42 bugs)

due to compile problems as evidenced by:

trac.transmissionbt.com/ticket/4560

trac.transmissionbt.com/ticket/4604

...take care of using the non-buggy version of autoconf to generate the official

tarball - the bug would affect all users cross-compiling transmission.

.

trac.transmissionbt.com/changeset/12954/trunk/configure.ac

also note:

November 11, 2011, at 06:31 PM by SRS -- ipkg install Transmission 2.42+ & GUI & minor web ui fixes
Added lines 44-47:

http:// computerfixpro.com/trs42pwebclientfx.zip -- minor Web UI fixes 11/11/2011

November 02, 2011, at 06:51 PM by SRS -- ipkg install Transmission 2.42+ & GUI
Added line 67:
Added lines 71-85:

Here is a very very nice Graphical User Interface for transmission 2.42+

http:// computerfixpro.com/WIN_GUI.zip (Windows ONLY)

that supports the download queue and status, filter torrents with errors,

graphing, etc. many nice things. Give credit to Ivanal:

http:// code.google.com/p/transmisson-remote-gui/issues/detail?id=463

who worked hard to produce a fantastic update to:

http:// code.google.com/p/transmisson-remote-gui/ (MAC, LINUX, WIN)

October 31, 2011, at 08:46 PM by SRS -- ipkg install Transmission 2.42+
Changed lines 47-48 from:

ipkg install transmission-2.42-1_armeb.ipk

to:

ipkg install transmission_2.42+-1_armeb.ipk

October 31, 2011, at 07:29 PM by SRS -- ipkg install Transmission 2.42+
Added line 22:
Changed lines 25-28 from:

Native compile/build Transmission

http://www.nslu2-linux.org/wiki/HowTo/TransmissionCompileBuild

to:

Transmission 2.42+

optware feed for Transmission 2.42+ not occurring perhaps compile problems:

https://trac.transmissionbt.com/changeset/12954/trunk/configure.ac

and

https://trac.transmissionbt.com/ticket/4528

difficulties with compile fixed so here is transmission_2.42+-1_armeb.ipk

http:// computerfixpro.com/transmission242p.zip

to install:

ipkg install transmission-2.42-1_armeb.ipk

be SURE to include the .ipk else ipkg install will try to download it

you may need to:

ipkg remove transmission if there is a version conflict

Changed lines 59-60 from:
to:

dont forget:

Package: transmission

Version: 2.42+-1

Depends: openssl, libcurl, libevent, zlib

.

.

Native compile/build Transmission

http://www.nslu2-linux.org/wiki/HowTo/TransmissionCompileBuild

.

Changed lines 92-93 from:

Although http://trac.transmissionbt.com/ticket/2858

to:

Although http:// trac.transmissionbt.com/ticket/2858

Changed lines 102-105 from:

http://trac.transmissionbt.com/ticket/3826

https://trac.transmissionbt.com/ticket/3826

to:

http:// trac.transmissionbt.com/ticket/3826

https:// trac.transmissionbt.com/ticket/3826

Changed lines 116-117 from:
    http://computerfixpro.com/Transmission-176-NSLU2.zip 
to:
    http:// computerfixpro.com/Transmission-176-NSLU2.zip 
Changed line 199 from:
  • ( See http://trac.transmissionbt.com/ticket/1583 )
to:
  • ( See http:// trac.transmissionbt.com/ticket/1583 )
Changed line 230 from:

8) connect to web UI http://YOUR-NAS-IP-ADDRESS:9091/

to:

8) connect to web UI http:// YOUR-NAS-IP-ADDRESS:9091/

Changed line 251 from:

wget -q http://www.bluetack.co.uk/config/level1.gz

to:

wget -q http:// www.bluetack.co.uk/config/level1.gz

Changed lines 265-266 from:

Clutch interface can be found at: http://<YOUR_NAS_IP>:9091/transmission/web/index.html

to:

Clutch interface can be found at: http:// <YOUR_NAS_IP>:9091/transmission/web/index.html

Changed lines 269-270 from:

See also http://trac.transmissionbt.com/wiki/Headless%20Transmisison

to:

See also http:// trac.transmissionbt.com/wiki/Headless%20Transmisison

Changed lines 328-330 from:

Wiki: http://wiki.openwrt.org/SambaHowto?highlight=%28samba%29

to:

Wiki: http:// wiki.openwrt.org/SambaHowto??highlight=%28samba%29

October 29, 2011, at 02:35 AM by SRS -- Native compile/build Transmission
Changed lines 22-26 from:
to:

.

Native compile/build Transmission

http://www.nslu2-linux.org/wiki/HowTo/TransmissionCompileBuild

.

April 30, 2011, at 12:09 AM by SRS -- Version 2.22-2 is fully functional
Added lines 29-37:

Version 2.22-2 is fully functional

Due to the hard work of a couple of people. They deserve a hard earned THANKS from everyone...

_______________________________________________________________________ _______________________________________________________________________ _______________________________________________________________________

April 18, 2011, at 10:56 PM by SRS -- Version 2.x and above NOT fixed
Added lines 65-66:
April 18, 2011, at 10:28 PM by SRS --
April 18, 2011, at 09:28 PM by SRS -- Version 2.x and above NOT fixed
Added lines 39-40:

http://trac.transmissionbt.com/ticket/3826

April 18, 2011, at 09:08 PM by SRS -- Version 2.x and above NOT fixed
Changed lines 31-32 from:

said that the issue is fixed when tried, version 2.22 from the

to:

said that the issue is fixed, when tried, version 2.22 from the

Changed lines 35-36 from:

SO... it does NOT appeared solved for the NSLU2.

to:

SO... it does NOT appear solved for the NSLU2.

April 18, 2011, at 09:05 PM by SRS -- Version 2.x and above NOT fixed
Added lines 23-26:
Added lines 37-48:

The problem may be related to:

https://trac.transmissionbt.com/ticket/3826

and the platform of the NSLU2:

http://www.nslu2-linux.org/wiki/Optware/Platforms

and the glibc or uclibc version. Maybe someone will

have time to sort this out and post it here.

Changed lines 60-76 from:

Version 1.8x

Versions 1.8x seems to be broken for many.

See http://trac.transmissionbt.com/ticket/2858

as well as other major problems reported for ARM and .ipk

Revert back to version 1.76 which works excellent.

Get version 1.76 for NSLU2 here:

http://computerfixpro.com/Transmission-176-NSLU2.zip

to:
April 18, 2011, at 07:39 PM by SRS -- Version 2.x and above NOT fixed
Changed lines 37-39 from:

If anyone has got it functioning maybe they'll post how to do it here!

to:

Version 1.76 woks great!

If anyone has got a version above 1.76 functioning maybe

they'll post how to do it here!

April 18, 2011, at 07:33 PM by SRS -- Version 2.x and above NOT fixed
Changed lines 27-30 from:

said that the issue is fixed when I tried version 2.22 from the

optware feeds it STILL produces many many hash check fails.

to:

said that the issue is fixed when tried, version 2.22 from the

optware feeds STILL produces many many hash check fails.

April 18, 2011, at 07:30 PM by SRS -- Version 2.x and above NOT fixed
Changed lines 33-37 from:

Reverted back to v1.76 http://computerfixpro.com/Transmission-176-NSLU2.zip

If anyone has got it functioning maybe they'll post it here!

to:

Reverted back to v1.76 :

    http://computerfixpro.com/Transmission-176-NSLU2.zip 

If anyone has got it functioning maybe they'll post how to do it here!

April 18, 2011, at 07:28 PM by SRS -- Version 2.x and above NOT fixed
Added lines 22-37:

Version 2.x and above

Although http://trac.transmissionbt.com/ticket/2858

said that the issue is fixed when I tried version 2.22 from the

optware feeds it STILL produces many many hash check fails.

SO... it does NOT appeared solved for the NSLU2.

Reverted back to v1.76 http://computerfixpro.com/Transmission-176-NSLU2.zip

If anyone has got it functioning maybe they'll post it here!

February 09, 2010, at 12:30 AM by SRS -- Version 1.8x broken, revert to 1.76
Added line 25:
Added line 27:
Added line 29:
Added line 31:
Changed lines 34-38 from:

http://computerfixpro.com/Transmission-176-NSLU2.zip

to:

http://computerfixpro.com/Transmission-176-NSLU2.zip

February 09, 2010, at 12:29 AM by SRS -- Version 1.8x broken, revert to 1.76
Changed lines 24-25 from:

Versions 1.8x seems to be broken for many. See http://trac.transmissionbt.com/ticket/2858 as well as other major problems reported for ARM and .ipk Revert back to version 1.76 which works excellent. Get version 1.76 for NSLU2 here:

to:

Versions 1.8x seems to be broken for many. See http://trac.transmissionbt.com/ticket/2858 as well as other major problems reported for ARM and .ipk Revert back to version 1.76 which works excellent. Get version 1.76 for NSLU2 here:

February 09, 2010, at 12:26 AM by SRS -- Version 1.8x broken, revert to 1.76
Changed lines 22-30 from:
to:

Version 1.8x

Versions 1.8x seems to be broken for many. See http://trac.transmissionbt.com/ticket/2858 as well as other major problems reported for ARM and .ipk Revert back to version 1.76 which works excellent. Get version 1.76 for NSLU2 here:

http://computerfixpro.com/Transmission-176-NSLU2.zip

August 02, 2009, at 05:29 PM by SRS -- Version 1.73-1 NOTES
Added lines 22-64:

Version 1.73-1 NOTES

August 2, 2009 SRS

umask support was added in v1.73. You may change its value in the

/root/.config/transmission-daemon/settings.json file:

it is set as "umask": 18, this is decimal 18 or octal 022, which is

the most commonly used value. From the documentation:

' umask: Number (default = 022) Set transmission's file mode creation mask.

See { the umask(2) manpage} for more information. Users who want their

saved torrents to be world-writable may want to set this value to 0. '

Note: The client must be closed before making changes to settings.json,

otherwise settings will be reverted to it's previous state.

__________

A lot of people are asking why Transmisson "freezes" when it starts

downloading a torrent.

This is usually because "preallocation": 2, is the value in settings.json.

From the documentation:

' * preallocation: Number (0 = Off, 1 = Fast, 2 = Full (slower but reduces disk fragmentation), default = 1) '

I keep the default setting of 2 which is very slow, but sometimes

use a value of 1 which is fast and seems to work fine.

June 07, 2009, at 05:16 PM by SRS -- Version 1.70 notes
Changed lines 29-30 from:

and can only be disabled by editing the settings.json file.

to:

This can only be disabled by editing the settings.json file.

June 07, 2009, at 05:14 PM by SRS -- version 1.70 notes
Changed lines 22-43 from:
to:

Version 1.70-2 NOTES

June, 7, 2009 SRS

For private trackers you should disable the new Distributed hash table (DHT) support.

When Using transmission-daemon Web GUI this is ENABLED by default! and can only be disabled by editing the settings.json file.

Use 'vi' to edit:

vi /root/.config/transmission-daemon/settings.json

change line to: "dht-enabled": false,

You may want to disable this for public trackers in many cases also.

Version 1.70 seems to work very nicely and fixes several irritations/bugs of version 1.61.

January 11, 2009, at 01:32 AM by rfinch --
Changed lines 1-3 from:

CGI interface to daemon is for managing and preview of the daemon state. There
is also torrent_watchdog script for automatic torrent queue processing and mail notification.

to:

CGI interface to daemon is for managing and preview of the daemon state. There is also torrent_watchdog script for automatic torrent queue processing and mail notification.

January 11, 2009, at 01:29 AM by rfinch --
Changed lines 1-2 from:

CGI interface to daemon is for managing and preview of the daemon state. There is also torrent_watchdog script for automatic torrent queue processing and mail notification.

to:

CGI interface to daemon is for managing and preview of the daemon state. There
is also torrent_watchdog script for automatic torrent queue processing and mail notification.

January 11, 2009, at 01:28 AM by rfinch --
Changed lines 1-4 from:

CGI interface to daemon is for managing and preview of the daemon state. There is also torrent_watchdog script for automatic torrent queue processing and mail notification.

to:

CGI interface to daemon is for managing and preview of the daemon state. There is also torrent_watchdog script for automatic torrent queue processing and mail notification.

January 11, 2009, at 01:11 AM by rfinch --
Changed line 48 from:

New version of Transmission based on the 1.3 branch is now available via ipkg install. Most of the instructions below the dividing line are now invalid. Transmission 1.3x comes with Clutch Web UI.

to:

New version of Transmission based on the 1.3 branch is now available via ipkg install. Most of the instructions below the dividing line are now invalid. Transmission 1.3x comes with Clutch Web UI.

Changed lines 109-120 from:

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly supervised with transmission_watchdog. The only way for moving finished active torrent into target dir is with Watchdog and not with Push.

CGI interface to daemon after each command lists all torrents in database. This time consuming can be interrupted at any time by giving next command or pressing stop button in WWW browser. This can be done for all commands except URL, Note and Rename as the action on torrent is taken during listing. This means that listing should not be interrupted until torrent is listed. In general there is no problem of interrupting listing at any

to:

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly supervised with transmission_watchdog. The only way for moving finished active torrent into target dir is with Watchdog and not with Push.

CGI interface to daemon after each command lists all torrents in database. This time consuming can be interrupted at any time by giving next command or pressing stop button in WWW browser. This can be done for all commands except URL, Note and Rename as the action on torrent is taken during listing. This means that listing should not be interrupted until torrent is listed. In general there is no problem of interrupting listing at any

Changed lines 123-125 from:

Fetch command is useful only for fetching torrent files without passkey as there is no possibility to pass cookies to server. Use with care. Proper fetch would be "download in browser and then upload to server".

to:

Fetch command is useful only for fetching torrent files without passkey as there is no possibility to pass cookies to server. Use with care. Proper fetch would be "download in browser and then upload to server".

Changed lines 128-129 from:

Troubles with tracker communication can be seen in syslog file. There is no association of active thread and reported problem from tracker. User should

to:

Troubles with tracker communication can be seen in syslog file. There is no association of active thread and reported problem from tracker. User should

Changed lines 133-138 from:

Before running transmission user should carefully inspect variables in transmission.conf and create SOURCE, WORK, and TARGET directories

transmission_watchdog cares for queue processing and should be run every 30 minutes with cron. /opt/etc/crontab entry should look like:

to:

Before running transmission user should carefully inspect variables in transmission.conf and create SOURCE, WORK, and TARGET directories.

transmission_watchdog cares for queue processing and should be run every 30 minutes with cron. /opt/etc/crontab entry should look like:

Changed lines 142-145 from:

For graphing to work properly, gnuplot and syslog is required. As log can accumulate it is recommended that logrotate is used for flushing old logs.

to:

For graphing to work properly, gnuplot and syslog is required. As log can accumulate it is recommended that logrotate is used for flushing old logs.

Changed lines 148-150 from:

You can do this either via fetch method that's available while viewing transmission.cgi (no cookie support!) and also with ftp and samba.

I prefer the ftp way since its locked with pass and very easy to start you only need to install vsftpd: \\

to:

You can do this either via fetch method that's available while viewing transmission.cgi (no cookie support!) and also with ftp and samba.

I prefer the ftp way since its locked with pass and very easy to start you only need to install vsftpd: \\

Changed lines 155-157 from:

Login details are set to your root login and pass by default.

For samba you need to try it yourself.

to:

Login details are set to your root login and pass by default.

For samba you need to try it yourself.

Changed lines 164-165 from:

A lot of people, myself included, are probably having some trouble when they first run into Oleo web interface for torrent download (transmission.cgi). That's because it's a little different from the torrent programs they're used to. So I'm going to describe what's going on under the hood.

to:

A lot of people, myself included, are probably having some trouble when they first run into Oleo web interface for torrent download (transmission.cgi). That's because it's a little different from the torrent programs they're used to. So I'm going to describe what's going on under the hood.

Changed lines 170-173 from:
  1. transmissiond. This is the actual workhorse that's downloading and uploading a torrent. If you run "ps" in a console you will see several of them working (if you have torrents running). Every time a torrent starts, one of these comes along and takes charge of it.
  2. transmission_watchdog. This one runs periodically, usually every 30 minutes, and is in charge of moving torrents around the queues (from "queued" to "active" to "done").
  3. transmission.cgi this is the actual web interface and is the thing you use to see your torrents and control them.
to:
  1. transmissiond. This is the actual workhorse that's downloading and uploading

a torrent. If you run "ps" in a console you will see several of them working (if you have torrents running). Every time a torrent starts, one of these comes along and takes charge of it.

  1. transmission_watchdog. This one runs periodically, usually every 30 minutes,

and is in charge of moving torrents around the queues (from "queued" to "active" to "done").

  1. transmission.cgi this is the actual web interface and is the thing you use to

see your torrents and control them.

Changed lines 182-191 from:

You start by putting a torrent file under the source/ directory. You can do this in many ways: you can download it on a desktop computer and FTP or SCP it to the router; you can SSH to the router, go into that directory and wget it from a website; you can use the "Fetch" button in the web interface to give the URL and the cgi will wget it and put it under source/.

All torrents found under source/ are automatically seen as part of the "Queued" set of torrents. If there are no torrents in the "Active" set, the watchdog will fetch the first one in the Queued set the next time it runs and make it Active. Or, you can manually make as many torrents as you want Active by selecting them and using the Push button in the interface.

Everytime the watchdog runs it will also check for completed Active torrents (the ones seeding) and will move them to the Completed set, where they stop moving and wait for you to come get the files.

You can manually pause an Active torrent by selecting it and using the Push button. This will stop the torrent and put it in the Suspended set. It will not leave this set anymore unless you select it and use the Push button again. (That's right, Push does two different things; when the torrent is first Queued it moves it to Active, and then it moves it between Active and Suspended; there's no way to move it back to Queued anymore).

Active torrents (and their files) are found under the work/ dir. Queued torrents are under source/. Completed torrents are under target/. Suspended torrents are under work/, but are temporarily renamed to ".torrent.suspended".

to:

You start by putting a torrent file under the source/ directory. You can do this in many ways: you can download it on a desktop computer and FTP or SCP it to the router; you can SSH to the router, go into that directory and wget it from a website; you can use the "Fetch" button in the web interface to give the URL and the cgi will wget it and put it under source/.

All torrents found under source/ are automatically seen as part of the "Queued" set of torrents. If there are no torrents in the "Active" set, the watchdog will fetch the first one in the Queued set the next time it runs and make it Active. Or, you can manually make as many torrents as you want Active by selecting them and using the Push button in the interface.

Everytime the watchdog runs it will also check for completed Active torrents (the ones seeding) and will move them to the Completed set, where they stop moving and wait for you to come get the files.

You can manually pause an Active torrent by selecting it and using the Push button. This will stop the torrent and put it in the Suspended set. It will not leave this set anymore unless you select it and use the Push button again. (That's right, Push does two different things; when the torrent is first Queued it moves it to Active, and then it moves it between Active and Suspended; there's no way to move it back to Queued anymore).

Active torrents (and their files) are found under the work/ dir. Queued torrents are under source/. Completed torrents are under target/. Suspended torrents are under work/, but are temporarily renamed to ".torrent.suspended".

Changed lines 207-210 from:
  • Update: this one updates the Active information with actual data. Since this update is an expensive operation for the router, it is usually cached and you need to press Update to refresh it. Otherwise, using List will only show the same old info.
  • Bypass: this will mark active torrent to be bypasswd by watchdow when it tries to enqueue new torrents from source. Use this for big and slow torrents that will be bypasswd by others.
to:
  • Update: this one updates the Active information with actual data. Since this

update is an expensive operation for the router, it is usually cached and you need to press Update to refresh it. Otherwise, using List will only show the same old info.

  • Bypass: this will mark active torrent to be bypasswd by watchdow when it

tries to enqueue new torrents from source. Use this for big and slow torrents that will be bypasswd by others.

January 11, 2009, at 01:05 AM by rfinch --
Changed lines 109-111 from:

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly

to:

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly

Changed lines 115-120 from:

CGI interface to daemon after each command lists all torrents in database. This time consuming can be interrupted at any time by giving next command or pressing stop button in WWW browser. This can be done for all commands except URL, Note and Rename as the action on torrent is taken during listing. This means that listing should not be interrupted until torrent is listed. In general there is no problem of interrupting listing at any

to:

CGI interface to daemon after each command lists all torrents in database. This time consuming can be interrupted at any time by giving next command or pressing stop button in WWW browser. This can be done for all commands except URL, Note and Rename as the action on torrent is taken during listing. This means that listing should not be interrupted until torrent is listed. In general there is no problem of interrupting listing at any

Changed line 123 from:

Fetch command is useful only for fetching torrent files without passkey as

to:

Fetch command is useful only for fetching torrent files without passkey as

Changed line 129 from:

no association of active thread and reported problem from tracker. User should

to:

no association of active thread and reported problem from tracker. User should

Changed lines 133-138 from:

Before running transmission user should carefully inspect variables in transmission.conf and create SOURCE, WORK, and TARGET directories

transmission_watchdog cares for queue processing and should be run every 30 minutes with cron. /opt/etc/crontab entry should look like:

to:

Before running transmission user should carefully inspect variables in transmission.conf and create SOURCE, WORK, and TARGET directories

transmission_watchdog cares for queue processing and should be run every 30 minutes with cron. /opt/etc/crontab entry should look like:

Changed lines 142-145 from:

For graphing to work properly, gnuplot and syslog is required. As log can accumulate it is recommended that logrotate is used for flushing old logs.

to:

For graphing to work properly, gnuplot and syslog is required. As log can accumulate it is recommended that logrotate is used for flushing old logs.

Changed lines 148-149 from:

You can do this either via fetch method that's available while viewing transmission.cgi (no cookie support!) and also with ftp and samba.

to:

You can do this either via fetch method that's available while viewing transmission.cgi (no cookie support!) and also with ftp and samba.

Changed lines 153-154 from:

Login details are set to your root login and pass by default.

to:

Login details are set to your root login and pass by default.

January 03, 2009, at 04:45 PM by SRS -- version 1.42-1 settings notes
Changed lines 44-46 from:
to:
  • Also note the rpc-whitelist-enabled key is NON functional
  • for the clutch WebGUI?
January 03, 2009, at 04:35 PM by SRS -- version 1.42-1 notes
Changed lines 27-44 from:

With version 1.42 functionality for an IP address whitelist

( See http://trac.transmissionbt.com/ticket/1583 ) So you MUST specify the "rpc-whitelist" setting in the settings.json file. You can do so by editing settings.json directly or using the -a option when starting transmission-daemon:

-a --allowed x.x.x.x,...

             Allow RPC accecss to a comma-delimited whitelist

of IP addresses. Wildcards can be specified in an address by using '*'. Default: "127.0.0.1" Example: "127.0.0.*,192.168.1.*"

The option sticks in future starts of transmission-daemon. A value of *.*.*.* allows all IP addresses.

to:
  • With version 1.42 functionality for an IP address
  • whitelist became active for the WebGUI?.
  • ( See http://trac.transmissionbt.com/ticket/1583 )
  • So you MUST specify the "rpc-whitelist" setting in the
  • settings.json file. You can do so by editing settings.json
  • directly or using the -a option when starting
  • transmission-daemon:
  • -a --allowed x.x.x.x,...
  • Allow RPC accecss to a comma-delimited whitelist
  • of IP addresses. Wildcards can be specified
  • in an address by using '*'.
  • Default: "127.0.0.1" Example: "127.0.0.*,192.168.1.*"
  • The option sticks in future starts of transmission-daemon.
  • A value of *.*.*.* allows all IP addresses.
January 03, 2009, at 04:31 PM by SRS -- format
Changed line 28 from:

became active for the WebGUI?.

to:
January 03, 2009, at 04:27 PM by SRS -- format
Changed lines 27-28 from:

With version 1.42 functionality for an IP address whitelist became active for the WebGUI?.

to:

With version 1.42 functionality for an IP address whitelist became active for the WebGUI?.

Changed lines 30-31 from:

So you MUST specify the "rpc-whitelist" setting in the settings.json file. You can do so by editing settings.json directly or using the -a option when starting transmission-daemon:

to:

So you MUST specify the "rpc-whitelist" setting in the settings.json file. You can do so by editing settings.json directly or using the -a option when starting transmission-daemon:

Changed lines 36-40 from:
             Allow RPC accecss to a comma-delimited whitelist of IP addresses. Wildcards can be specified in an address by using '*'.  Default: "127.0.0.1" Example: "127.0.0.*,192.168.1.*"

The option sticks in future starts of transmission-daemon. a value of *.*.*.* allows all IP addresses.

to:
             Allow RPC accecss to a comma-delimited whitelist

of IP addresses. Wildcards can be specified in an address by using '*'. Default: "127.0.0.1" Example: "127.0.0.*,192.168.1.*"

The option sticks in future starts of transmission-daemon. A value of *.*.*.* allows all IP addresses.

January 03, 2009, at 04:25 PM by SRS -- version 1.42-1 notes
Added lines 24-36:

Version 1.42-1 NOTES

With version 1.42 functionality for an IP address whitelist became active for the WebGUI?. ( See http://trac.transmissionbt.com/ticket/1583 ) So you MUST specify the "rpc-whitelist" setting in the settings.json file. You can do so by editing settings.json directly or using the -a option when starting transmission-daemon:

-a --allowed x.x.x.x,...

             Allow RPC accecss to a comma-delimited whitelist of IP addresses. Wildcards can be specified in an address by using '*'.  Default: "127.0.0.1" Example: "127.0.0.*,192.168.1.*"

The option sticks in future starts of transmission-daemon. a value of *.*.*.* allows all IP addresses.

November 22, 2008, at 03:10 PM by SRS -- clarify
Changed line 37 from:

8) connect to web UI http://NAS:9091/

to:

8) connect to web UI http://YOUR-NAS-IP-ADDRESS:9091/

November 22, 2008, at 03:00 PM by SRS -- clarify
Changed lines 46-47 from:

NOTE: With UnSlung? 6.x and Transmission 1.4 it was ...transmission-da (NOT transmission-daemon). Using 'ps -A' or 'ps' command you will see this.

to:

NOTE: With UnSlung? 6.x and Transmission 1.4 it was 'killall transmission-da' (NOT 'killall transmission-daemon'). Using 'ps -A' or 'ps' command you will see this.

November 22, 2008, at 02:56 PM by SRS -- install notes
Added lines 45-47:

NOTE: With UnSlung? 6.x and Transmission 1.4 it was ...transmission-da (NOT transmission-daemon). Using 'ps -A' or 'ps' command you will see this.

October 02, 2008, at 02:58 AM by Arthur92710 --
Changed lines 1-175 from:

Transmission

to:

CGI interface to daemon is for managing and preview of the daemon state. There is also torrent_watchdog script for automatic torrent queue processing and mail notification.

Features

  • multithreading (eg. 10 torrents simultaneously with nice priority)
  • Multitracker, PEX support, UPNP support, Encryption support, Bandwith limiting
  • automatic seeding when torrent finishes (configurable)
  • configurable port
  • WWW interface transmission.cgi can be public (no password) as there is no delete provided. (old versions)
  • Clutch WWW Interface with username and password. (for versions > 1.31)
  • Accelerator keys (ALT-key) for CGI interface. See help for underlined keys.
  • Per torrent and cumulative status
  • start/stop/push/bypass and other commands available in WWW interface
  • lightweight - low memory footprint
  • tracker scrape info. Suggest best seed torrent from target dir.
  • watchdog for auto restart/queue processing with cron
  • syslog watchdog events
  • mail notify when torrent finishes
  • no state database required. Directory tree is database (slow, but fail-safe)
  • stable and portable. Developed on Asus WL-500g Deluxe with Oleg firmware

Version 1.3x

New version of Transmission based on the 1.3 branch is now available via ipkg install. Most of the instructions below the dividing line are now invalid. Transmission 1.3x comes with Clutch Web UI.

1) setup optware ipkg
2) # ipkg update
3) # ipkg install transmission

4) forward port 51413 to NAS

5) (recommend to create and login as a non-root user, root user might work too)
6) $ mkdir -p $HOME/Downloads
7) $ /opt/bin/transmission-daemon -w $HOME/Downloads
   $ pidof transmission-daemon  # should return 3 process ID's
8) connect to web UI http://NAS:9091/

The above should get you started, usage of the web UI should be straight-forward. If you have any problem starting transmission-daemon on step 7

7.1) # killall transmission-daemon
7.2) # /opt/bin/transmission-daemon -h
7.3) # /opt/bin/transmission-daemon -f

Autostart

avgjoe - Upon successfully installing 1.3x under ipkg you must start the transmission daemon. I have created a basic start script which will fetch the new version of the blocklist from bluetack and start the transmission-daemon:

#!/bin/sh

# update blocklist
cd /root/.config/transmission-daemon/blocklists
wget -q http://www.bluetack.co.uk/config/level1.gz
if test -f level1.gz; then
   rm level1
   gunzip level1.gz
   chmod go+r level1
fi

if [ -n "`pidof transmission-daemon`" ]; then
   kill -9 `pidof transmission-daemon`
fi

/opt/bin/transmission-daemon -b

Clutch interface can be found at: http://<YOUR_NAS_IP>:9091/transmission/web/index.html

You can modify config either using web UI, or by editing /root/.config/transmission-daemon/settings.json

See also http://trac.transmissionbt.com/wiki/Headless%20Transmisison


Workflow

For queue torrent file processing there should exist tree directories:

  • source - User should copy .torrent files here
  • work - Used for torrent processing
  • target - Place where finished torrents are put

Typical file flow is source -> work -> target For every torrent file from source, directory with the same name is created. Then torrent file is moved into this directory and transmissiond is run in background and constantly supervised with transmission_watchdog. The only way for moving finished active torrent into target dir is with Watchdog and not with Push.

CGI interface to daemon after each command lists all torrents in database. This time consuming can be interrupted at any time by giving next command or pressing stop button in WWW browser. This can be done for all commands except URL, Note and Rename as the action on torrent is taken during listing. This means that listing should not be interrupted until torrent is listed. In general there is no problem of interrupting listing at any point. This will not invalidate database which is file system alone.

Fetch command is useful only for fetching torrent files without passkey as there is no possibility to pass cookies to server. Use with care. Proper fetch would be "download in browser and then upload to server". This can only be done by browser plugin.

Troubles with tracker communication can be seen in syslog file. There is no association of active thread and reported problem from tracker. User should resolve this alone.

Install notes

Before running transmission user should carefully inspect variables in transmission.conf and create SOURCE, WORK, and TARGET directories

transmission_watchdog cares for queue processing and should be run every 30 minutes with cron. /opt/etc/crontab entry should look like:

 # m  h dom mon dow user command
 */30 *    * * *   admin nice transmission_watchdog 

For graphing to work properly, gnuplot and syslog is required. As log can accumulate it is recommended that logrotate is used for flushing old logs.

Accessing/Uploading .torrent files

You can do this either via fetch method that's available while viewing transmission.cgi (no cookie support!) and also with ftp and samba.

I prefer the ftp way since its locked with pass and very easy to start you only need to install vsftpd:
ipkg install vsftpd

Login details are set to your root login and pass by default.

For samba you need to try it yourself. Wiki: http://wiki.openwrt.org/SambaHowto?highlight=%28samba%29

Using Transmission

by wirespot

A lot of people, myself included, are probably having some trouble when they first run into Oleo web interface for torrent download (transmission.cgi). That's because it's a little different from the torrent programs they're used to. So I'm going to describe what's going on under the hood.

There are 3 pieces of software working on the torrents:

  1. transmissiond. This is the actual workhorse that's downloading and uploading a torrent. If you run "ps" in a console you will see several of them working (if you have torrents running). Every time a torrent starts, one of these comes along and takes charge of it.
  2. transmission_watchdog. This one runs periodically, usually every 30 minutes, and is in charge of moving torrents around the queues (from "queued" to "active" to "done").
  3. transmission.cgi this is the actual web interface and is the thing you use to see your torrents and control them.

How to use the torrents

You start by putting a torrent file under the source/ directory. You can do this in many ways: you can download it on a desktop computer and FTP or SCP it to the router; you can SSH to the router, go into that directory and wget it from a website; you can use the "Fetch" button in the web interface to give the URL and the cgi will wget it and put it under source/.

All torrents found under source/ are automatically seen as part of the "Queued" set of torrents. If there are no torrents in the "Active" set, the watchdog will fetch the first one in the Queued set the next time it runs and make it Active. Or, you can manually make as many torrents as you want Active by selecting them and using the Push button in the interface.

Everytime the watchdog runs it will also check for completed Active torrents (the ones seeding) and will move them to the Completed set, where they stop moving and wait for you to come get the files.

You can manually pause an Active torrent by selecting it and using the Push button. This will stop the torrent and put it in the Suspended set. It will not leave this set anymore unless you select it and use the Push button again. (That's right, Push does two different things; when the torrent is first Queued it moves it to Active, and then it moves it between Active and Suspended; there's no way to move it back to Queued anymore).

Active torrents (and their files) are found under the work/ dir. Queued torrents are under source/. Completed torrents are under target/. Suspended torrents are under work/, but are temporarily renamed to ".torrent.suspended".

What other buttons do:

  • List: this one gives the complete list of all the torrents in all the queues.
  • Update: this one updates the Active information with actual data. Since this update is an expensive operation for the router, it is usually cached and you need to press Update to refresh it. Otherwise, using List will only show the same old info.
  • Bypass: this will mark active torrent to be bypasswd by watchdow when it tries to enqueue new torrents from source. Use this for big and slow torrents that will be bypasswd by others.
  • Watchdog: this will force the watchdog to run now instead of waiting for the next normal time. This is useful if you see that a torrent has finished downloading and is seeding, but you don't want to wait for it to be moved to Completed the next time the watchdog would normally run. (Please note that you should let torrents seed so other people can benefit too. Instead of stopping that torrent, consider Push-ing a Queued one instead.)
  • Pause: this will stop all torrents temporarily. It does this by telling all transmissiond programs to die. It doesn't move torrents around the queues at all, there simply aren't downloads or uploads going. This will be marked clearly in big bold letters saying "torrent processing paused". Use Pause again to resume the Active torrents.
  • Info will show some information about the torrent (tracker, what files are in it and so on).
  • Log will try to create a graph showing the state of the downloads. Depends on whether you have gnuplot installed. (I personally prefer rrdtool, look around the forum for the rrdtool tutorial.)
  • Remove will mark a torrent for removal, and Purge will actually DELETE BOTH THE TORRENT AND THE FILES FOR IT. So be careful with it. Note that removal can be used for unfinished (suspended) torrents only. For removing torrents from target use other commands like rm -rf torrent-dir
  • Scrape will attempt to ask the tracker for the scrape info, and Best will attempt to suggest the best seed torrent from the completed ones.
  • Note will add your personal note to the torrent, in case you want to jot down something about it.
October 02, 2008, at 02:56 AM by Arthur92710 --
Added line 1:

Transmission

view · edit · print · history · Last edited by SRS.
Based on work by SRS, rfinch, and Arthur92710.
Originally by Arthur92710.
Page last modified on April 02, 2014, at 11:19 PM