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

Hi,

I must have done something wrong on either my DIR-655 router or DNS-323.  My Transmission 1.51 is NOT getting any respond from any tracker as of three days ago.  I need help/direction as to where I should look at.  I am ABLE to download/upload from uTorrent using the same PORT 7777 though.  Any assistance is appreciated.

[02:50:11.216] Couldn't create socket: Address family not supported by protocol
[02:50:11.218] RPC Server: Adding address to whitelist: *.*.*.*
[02:50:11.220] RPC Server: Serving RPC and Web requests on port 9091
[02:50:11.221] RPC Server: Whitelist enabled
[02:50:11.221] RPC Server: Password required
[02:50:11.222] Transmission 1.51 (7968) started
[02:50:11.322] transmission-daemon: requiring authentication
[02:50:11.334] Loaded 1 torrents
[02:50:12.219] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[02:50:12.219] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[02:50:15.000] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.10.7:4444/wipconn"
[02:50:15.000] Port Forwarding (UPnP): Local Address is "192.168.10.8"
[02:50:15.005] Port Forwarding (UPnP): Port forwarding through "http://192.168.10.7:4444/wipconn", service "urn:schemas-upnp-org:service:WANIPConnection:1".  (local address: 192.168.10.8:7777)
[02:50:15.005] Port Forwarding (UPnP): Port forwarding successful!
[02:50:15.006] Port Forwarding: State changed from "Not forwarded" to "Forwarded"
[02:50:15.006] Port Forwarding: Opened port 7777 on 0.0.0.0 to listen for incoming peer connections

Last edited by KiLrOy (2009-04-12 22:00:22)

Hey Kylek and community,

I'm trying to use cron to schedule Transmission to start at midnight and stop at 8am, to use my offpeak quota.
Quite simply, I thought adding jobs for "/ffp/start/transmission.sh start" and "/ffp/start/transmission.sh stop" (without quotes) would do the trick, but only the stop command seems to be working.

here is the list of items in my crontab - all stock bar the last two.

root@NAS:/# crontab -l
32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
*/10 * * * * /usr/sbin/offl_chk four
*/60 * * * * /usr/sbin/getdhcp&
0 0 * * * /ffp/start/transmission.sh start
0 8 * * * /ffp/start/transmission.sh stop

running the commands works fine from the command line, just not via the cron job.

It's not a date issue, as the stop works correctly at 8am locally - so fairly sure it's using /bin/date as opposed to /ffp/bin/date (see below)

root@NAS:/# date
Mon Apr 13 01:00:26 UTC 2009
root@NAS:/# /bin/date
Mon Apr 13 11:00:29 EST 2009
root@NAS:/# /ffp/bin/date
Mon Apr 13 01:00:33 UTC 2009
root@NAS:/#

strangely though, if I add a job

* * * * * echo "test"

nothing is printed out. The thing which is confusing me about the whole thing is that the stop command works, at whatever time I set it to.

cheers,
- Klaus

***EDIT***
oh, and on reboot cron jobs I added (ie, anything beyond the first 4 lines) are removed. I assume crontab <filename> is performed to reload default values into there, and has little to do with why the cron for starting transmission doesn't work

Last edited by cliaz (2009-04-13 17:07:18)

1.52 out

Hey LeChuck,

With that script, do I put it in a .sh file and run said .sh from crontab? if so, when do I schedule it to run, assuming that I want to un-limit it at midnight and limit it at 8am.

start_time=8
end_time=0

# Normal speed setting:
normal_speed="-d100 -u20"
# Speed limit setting:
limited_speed="-d0 -u0"

note sure if it will let me limit it to 0KB/s, here's hoping.

well, I've tried using transmission-remote to do stuff, and from the command line it works - eg, running transmission-remote -D -U works fine
but doing it via cron gives me issues, doesn't seem to work.

* * * * * transmission-remote -d100 -u20

is what I'm running, trying to get it working at all, but no go. appears to be a cron issue, yet it still runs

0 8 * * * /ffp/start/transmission.sh stop

as I said, it works from commandline...but not from cron

awesome, that's working. not sure what the "export TRANSMISSION_HOME=/mnt/HD_a2/.transmission-daemon;" does, but it made it work - for all commands from transmission-remote.

thanks KRH! now to figure why cron doesn't want to run transmission.sh start - not out of any real necessity, purely out of interest

- Klaus

Not sure if this has been posted or not before, however since I started using this client to download torrents on my DNS-321, I've noticed that whenever I download something off Transmission and try to transfer the files to the PC (I make sure to stop the torrent and remove it) my transfer speeds are somewhat slow (Goes from 1.91 MB/s to 4.9 MB/s at most), but whenever I move stuff to the NAS and transfer them back to my PC I get the usual normal speed (10-14 MB/s).

So my question is, does this happen to everyone that downloads stuff from their NAS or is this strange behavior just occurring to me? Is there any way around it?

(If not, I'll just have to see it as a necessary evil to save some electricity at night.)

dummhuman wrote:

I am having a problem similar to some other people here, in that the <transmission-daemon.log> file says that transmission could not create the download file because the parent folder does not exist, and the web interface says that there is 'No such file or directory' under the torrent's progress bar.  I have tried the 'chown' procedure to change file owner to nobody, with no results, and I am certain that the download folder does exist, because i have created it using command-line, and verified through windows explorer.  I apologize if this is a stupid question; I have just started using ffp today, and I've never interacted with Linux before, so I was hoping someone might have an idea of what was wrong.

Transmission needs the full linux path to the directory: /mnt/HD_a2/download/torrent or something similar.

When I try to download a torrent or directory, it always give me an error no such file or directory, i tried downloading the same file in utorrent in my computer, the file was able to download. I am using ESET Smart Security, I ran the port check test in utorrent, the test failed for both the ports I used for transmission and utorrent, but I am able to get good speed in utorrent. Anyone can advise?

Some people have already tried, but the new Transmission v1.52 package is now up for you to grab!

Nothing of importance has changed, really, so an upgrade might not really be necessary.

You can find the link in the first post of this thread.

hello,

I need some help setting up my nas 323 and transmission.
I followed the instructions here in the forum and wiki.

I have nas 323 with firmware 1.06 and transmission 1.52.

I installed funplug and transmission following the rules from here.

When I added some torrents to download (some of them um more than 10000 peers), transmission doesnt download anything and doesnt detect any peers.

in attach i send the configuration file and here is the logfile so you can try and help me out please.

----------- LOG -----------

[23:11:26.048] Couldn't create socket: Address family not supported by protocol
[23:11:26.049] RPC Server: Adding address to whitelist: *.*.*.*
[23:11:26.051] RPC Server: Serving RPC and Web requests on port 9091
[23:11:26.052] RPC Server: Whitelist enabled
[23:11:26.052] RPC Server: Password required
[23:11:26.053] Transmission 1.52 (8256) started
[23:11:26.153] transmission-daemon: requiring authentication
[23:11:27.050] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[23:11:27.051] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[23:11:37.070] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.3.2:50181/"
[23:11:37.070] Port Forwarding (UPnP): Local Address is "192.168.3.2"
[23:11:37.111] Port Forwarding (UPnP): Port forwarding through "http://192.168.3.2:50181/", service "".  (local address: 192.168.3.2:51413)
[23:11:37.111] Port Forwarding: State changed from "Not forwarded" to "Starting"
[23:11:37.112] Port Forwarding: Opened port 51413 on 0.0.0.0 to listen for incoming peer connections
[23:11:37.120] Searching for web interface file "/home/nobody/.local/share/transmission/web/javascript/transmission.js"
[23:11:37.120] Searching for web interface file "/ffp/share/transmission/web/javascript/transmission.js"
[23:12:07.750] Lost.S05E13.HDTV.XviD-NoTV.avi: Couldn't read resume file
[23:12:07.752] Lost.S05E13.HDTV.XviD-NoTV.avi: Queued for verification
[23:12:07.756] Lost.S05E13.HDTV.XviD-NoTV.avi: Verifying torrent
[23:13:35.743] Port Forwarding: State changed from "Starting" to "???"

Last edited by cybernauta (2009-04-24 01:25:14)

---

Attachments:
settings.json, Size: 1,052 bytes, Downloads: 357