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

I'd like to try compiling this myself, however I am getting some errors:
Any help?


/mnt/HD_a2/build/transmission-1.42 # ./configure -q && make -s
appending configuration tag "CXX" to libtool
appending configuration tag "F77" to libtool
gnome-config: No such file or directory
gnome-config: No such file or directory
gnome-config: No such file or directory
gnome-config: No such file or directory
./configure: line 24442: intltool-update: command not found
configure: error: Your intltool is too old.  You need intltool 0.23 or later.
/mnt/HD_a2/build/transmission-1.42 #

I'am having the exact same error message as zxsix when compiling on the NAS with the FFP packages.

I'm have tried using the --disabled-nls parameter, but it does keep looking for the intltool-update binary.

checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking whether NLS is requested... no
checking for intltool >= 0.23... ./configure: line 24442: intltool-update: command not found
found
configure: error: Your intltool is too old.  You need intltool 0.23 or later.


For the debian installation it had to do with some dependencies being unavailable for etch:

checking for LIBCURL... configure: error: Package requirements (libcurl >= 7.16.3) were not met:
Requested 'libcurl >= 7.16.3' but version of libcurl is 7.15.5

For debian etch, there is no libcurl3 package available higher than 7.15.5

Last edited by Maartenvdv (2008-12-25 10:06:15)

I have upgraded my debian installation to lenny instead of etch. Now I have the right libcurl library and it builds.

A normal funplug package would still be great though, haven't been able to build this.

Transmission 1.42 is out. Check the first page for the changelog and the updated download link.

Please note that the format for the RPC whitelist has changed (it used to be an ACL). I've also updated the info on this in the first post.

heema wrote:

KyleK wrote:

Transmission 1.42 is out. Check the first page for the changelog and the updated download link.

will some one make a funplug package out of it ?

ummm.....first post in this thread.

KyleK wrote:

dansu wrote:

Hi All!

I noticed there is some restriction of upload speed for any torrents - 256.2 kB per sec.
It's the max upload speed which I have ever seen in Transmission.
Download speed is fine - it can reach 1 or 2 MB per sec for some torrent.
Total upload speed can be more in case if few torrents are in work but for each of them upload speed is 256.2 kB/sec maximum...
Of course there are no any restriction set in the system.
Is there this problem only with my device or is it well known bug?
Is it possible to fix it?
Thanks in advance!

Denis

My line doesn't upload faster than 115kB/s, so I can't test this. This is the wrong forum for this kind of question. I only provide the binaries of Transmission for the NAS, I'm not an active developer.

Please ask your question again at http://forum.transmissionbt.com.

I have just installed new version - 1.42
And I can see my problem is resolved!
Now upload speed per torrent can reach 1.5 MB/sec and even more...
I'm happy!
Thanks KyleK!

i changed one line in the settings.json to

    "rpc-whitelist": "127.0.0.1,192.168.178.*",

(where 192.168.178.* is the internal ip range)

btw. with 1.42 have now dissapearing torrents on trackers that are still seeded by transmission, who knows

Last edited by NASewise (2008-12-26 18:52:40)

At attempt to begin loading Transmission gives out the following message: Connection failed. Could not connect to the server. You may need to reload the page to reconnect. In a broad log-file the following is written down:

Transmission 1.42 (7500) started
RPC Server: Adding address to whitelist: 127.0.0.1
RPC Server: Adding address to whitelist: 192.168.220.231
RPC Server: Serving RPC and Web requests on port 9091
RPC Server: Whitelist enabled
Loaded 1 torrents
Port Forwarding: Opened port 32929 to listen for incoming peer connections
Searching for web interface file "/home/nobody/.local/share/transmission/web/javascript/transmission.js"
Searching for web interface file "/ffp/share/transmission/web/javascript/transmission.js"
moydomdinaz.BD.AVC.chopper887.mkv: Couldn't read resume file
moydomdinaz.BD.AVC.chopper887.mkv: Queued for verification
moydomdinaz.BD.AVC.chopper887.mkv: Verifying torrent
moydomdinaz.BD.AVC.chopper887.mkv: Got 26 peers from tracker
/ffp/bin/transmission-daemon: bandwidth.c: 428: tr_bandwidthUsed: Assertion `tr_isBandwidth( b )' failed.


In what there can be a problem.
Browser Оpera 9.61.

Thanks

I followed the instructions for adding the whitelist through the command prompt (and also tried manually editing the settings.json file) but both were unable to add any additional whitelist IP's to Transmission.  I ended up downgrading to 1.40 as one of my private tracker sites hasn't allowed 1.42 yet. 

Anyone else having the same problem?

PS - I uninstalled Transmission first (-r) before installing 1.42.

bearxor wrote:

I reinstalled back down to 1.40 and it worked fine.  I then uninstalled it and reinstalled it to 1.42 and got a 401 access error again.  Uninstalling 1.42 and reinstalling 1.40 fixed it up again.

I had the same problem.
Solution was to change rpc-whitelist value from network address and netmask notation (it was 127.0.0.1/32,10.64.119.216/29 for me) to only host address notation (now I have 127.0.0.1,10.64.119.221,10.64.119.222).
After I have changed it - it became worked.
Also you need to rememver the following. When you plan to change your settings.json file it's necessary to stop transmission daemon first.
So, give the command:

root@nas:~# /ffp/start/transmission.sh stop

Then wait for transmission process is stopping:

root@nas:~# ps -ef|grep trans|grep -v grep
29398 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon
29399 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon
29400 nobody   /ffp/bin/transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon
root@nas:~# ps -ef|grep trans|grep -v grep
root@nas:~#

When you see there are no any process like these you can start to change your settings.json file.
After this start the Transmission and check settings.json it's correct JIC.
I did so and it helped.

Last edited by dansu (2008-12-27 10:42:47)

Hi, I am a complete newbie to linux. I have manged to install transmission 1.4.2. Everything works fine except for two things.

1.

After "transmission-daemon -f -t -u <user> -v <passwd> -a 127.0.0.*" transmission starts fine, without errors, but after pressing CTRL+"C" the settings.json file is not updated, so when I start again transmission with "sh transmission.sh start" the setting file loads with the default values...

2. I am not able to delete finished torrent from the transmission download directory in my windows XP after removing them from clutch.  Via telnet I can delete everything. 

Can you please help?

toolbox wrote:

Sickboi, I have the same results. I ended up just edit settings.json in .transmission-daemon before start transmissionsh.sh. It seems when transmission is running in the console, it updates the settings in .transmission. I am new to this also and not sure if there is something I did to cause this to happen.

Meanwhile I read the last few threads once again and I find the solution.  (Thank you dansu!)

So after "transmission-daemon -f -t -u <username> -v <password> -a 127.0.0.*, runs fine, press CTRL+C and then wait till all the processes have been stopped.

You can check it with "ps -ef|grep trans|grep -v grep"

After that "vi settings.json" edit the config file --> save and close.
Now after "sh transmission.sh start" it works fine with the new settings!