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

brasilcaps wrote:

Anyhow, does anybody know why my internet is still slow even after I paused all my downloads? When I turn off the Transmission, it all goes back to speedy self.

All the routers I've owned --Netgear MR814v2, Linksys WRT54Gv2, D-Link DGL-4300, and D-Link DLG-4500-- spread across three ISPs --RCN, Roadrunner, and Cox-- all have required reboots after heavy torrent usage.  OpenWRT on the WRT54G resolved some the issue for most people, but I have never found a good resolution for other routers.

Hello! I have a question. Four days ago i update transmission on DNS-323 to 1.51. And yesterday i was banned for cheat on tracker. My standart upload traffic increased six time. It`s impossible! Please advise me something. Thank you!

KyleK wrote:

Wrong place, go to www.transmissionbt.com, they write the app.

Thanks!

LeChuck wrote:

The TransmissionBT site has a bash script to limit bandwidth for the transmission-daemon.

It has? Where? If it's a normal bash script, you can use it on the DNS-323.

Any other suggestions to schedulke bandwidth for the torrent client? My ISP uses peak and off-peak.

It looks like bandwidth scheduling is coming with the next release. No promises though.

OK Kylek I tried your advice but it ended up in two problems first I got the
"401: Unauthorized

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.

If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details."

and what is worse is that I get the message "Failed to retrieve share list from server" from nautilus if I try to get to the share so something seems to went terrible wrong during the operation.

Ok I found a solution. First of all after all my messing around I realized that that NAS had a yellow lamp at the right activated. I then restarted the NAS by unplugging the device. After that the network shares was back Yippey. Then when I looked inte folders on the NAS I now had two folders at the toplevel. (volume-1 and volume-1-1) The content in these two folders seemes to be pretty much the same with transmission daemon and everything. After that I tried your advice from the beginning with a new whitelist credentials and the chown for a nobody user. And all of a sudden everything seem to work. Now I have a last question What should I do with the extra folder volume-1-1? Is it safe to remove it?

Last edited by axelsvag (2009-03-28 10:34:37)

Interesting but I have just put one hard drive in the NAS?

After delaying it for a while, I finally upgraded my firmware to 1.06 last night. The upgrade went smoothly but I had to turn off D-Link's iTunes server and UPnP servers - they were somehow interfering with transmission (e.g. causing the transmission web UI and tranmission-remote operations to time out) when they update themselves.

KyleK wrote:

lamski wrote:

I have some questions for you guys: I'm still using the 1.05 firmware version for my DNS-323. I'm thinking of upgrading to 1.06 but I'm wondering if there are any drawbacks.
If I upgrade to 1.06, do I need to reinstall ffp? I simply use the JBOD configuration for 2x 1TB disks and I have around a few hundred GBs of data (mostly downloaded media). Is it safe to simply install firmware 1.06? I read in the release notes that disks will now sleep "properly" - will this affect transmission operation?

Any input on this will be greatly appreciated.

A firmware update should not impact the functionality of funplug in any way. You won't have to reinstall ffp after upgrading.
The info in the release notes about disks sleeping properly doesn't affect Transmission in any way (the disk won't be spinning down anyway if Transmission is running - it has to read and/or write data from it).


But, in any case it would be wise to backup critical data before the firmware update.

KyleK wrote:

Dont' change the settings.json by hand. Use the tools transmission-daemon and transmission-remote for that.

If you want a completely fresh start, do this:

Code:

$ /ffp/start/transmission.sh stop
$ rm -r /mnt/HD_a2/.transmission-daemon   (this deletes all your current settings as well as progress info about currently downloading torrents!)

$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <login> -v <password> -a "*.*.*.* -w /mnt/HD_a2/Downloads
[Press Ctrl-C after a maybe 20 seconds].
$ chown -R nobody /mnt/HD_a2/.transmission-daemon /mnt/HD_a2/Downloads

From here on out, only use /ffp/start/transmission.sh to start and stop the application.

Hi ! I performed these instructions , set  "-w /mnt/HD_a2/Downloads" option , but still receiving the message "parent folder "/home/nobody/Downloads" does not exist "


from settings.json:
"download-dir": "\/mnt\/HD_a2\/Downloads", 

Why it always tries to download to "/home/nobody/Downloads" although another download folder was specified ?

How it could be fixed?

Last edited by asm (2009-04-05 14:20:57)

asm wrote:

Hi ! I performed these instructions , set  "-w /mnt/HD_a2/Downloads" option , but still receiving the message "parent folder "/home/nobody/Downloads" does not exist "


from settings.json:
"download-dir": "\/mnt\/HD_a2\/Downloads", 

Why it always tries to download to "/home/nobody/Downloads" although another download folder was specified ?

How it could be fixed?

If you start Transmission directly, using its binary (/ffp/bin/transmission-daemon) without the -g option, then it will store its settings in /home/nobody/.transmission-daemon/settings.json. When you reboot the NAS, that file will be gone. So the next time you start up Transmission, it won't find the old settings, and create new, default ones. The default folder for saving torrents is ~/Downloads.

So the correct procedure is this:

//When starting for the first time, use this command:
$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_a2/Downloads
//When Transmission stops showing any messages, press Ctrl-C. It'll then save the settings in /mnt/HD_a2/.transmission-daemon/settings.json
//From now on, use the script in /ffp/start to start and/or stop transmission:
$ sh /ffp/start/transmission.sh start

Important: If you decide to store the Transmission settings somewhere else, you have to modify /ffp/start/transmission.sh as well!

No problems with large torrents here. Maybe your disks are full?
What does the logfile say?

How did you add your PC's IP to the whitelist?
When you quit Transmission (/ffp/start/transmission.sh stop) and then look at /mnt/HD_a2/.tranmsission-daemon/settings.json, are your IPs listed there?

ive followed everything here and i cannot download a torrent.

ive pulled everything apart and used every command but i still get the "folder doesnt exist" error.

chown hasent helped and neither does the GUI.  what can i be doing wrong?  i just boot to ubuntu for torrents, id like to use my 321

here is ls -l     /mnt/HD_a2/

drwxrwxrwx    2 nobody   501          4096 Apr  9 21:15 Downloads

Last edited by roth140 (2009-04-11 08:00:19)

Depends on where you put the Transmission-1.51.tgz
The root folder of ffp is /ffp (cd /ffp)
The root of drive one is /mnt/HD_a2
The root of drive two is /mnt/HD_b2