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

KyleK wrote:

Nope, those messages unfortunately do not help to determine why your Transmission shuts down by itself.
How fast does it shut down?
How many torrents have you loaded/downloading/seeding?
At what speeds?

Make sure Transmission doesn't store anything on the NAS's flash (e.g. /tmp or so). There's not much free space available and once it's full all kinds of things can happen.

Hi Kylek...thanks for your help thus far!

Sorry I haven't been able to provide meaningful log info for you to help. 

Anyway, what I've also noticed that everytime transmission shuts down on its own, and when I restart it, it loses all its seed/leechers info and start off again @ 0/0 for seeders and leechers...

Perhaps it's a case of where a file never got saved properly and it's preventing transmission from working properly?

EDIT:

I got dmesg right after a shutdown...what can I glean from this?

TCP: drop open request from 123.110.152.93/1208
TCP: drop open request from 69.159.113.101/56196
TCP: drop open request from 124.14.30.105/39354
TCP: drop open request from 71.75.162.197/52456
TCP: drop open request from 109.205.253.243/43493
TCP: drop open request from 85.151.46.29/56693
TCP: drop open request from 72.226.125.36/55400
TCP: drop open request from 109.255.5.28/53657
TCP: drop open request from 95.103.172.177/18199
TCP: drop open request from 78.8.56.34/2872
TCP: drop open request from 75.152.222.122/60707
TCP: drop open request from 78.129.115.66/65095
TCP: drop open request from 78.154.133.50/64864
TCP: drop open request from 202.173.168.71/51308
printk: 2 messages suppressed.
TCP: drop open request from 186.18.188.164/64237
TCP: drop open request from 75.82.51.115/61262
TCP: drop open request from 68.146.135.142/58127
printk: 21 messages suppressed.
TCP: drop open request from 109.93.170.40/3043
printk: 1 messages suppressed.
TCP: drop open request from 81.182.93.33/56534
printk: 3 messages suppressed.
TCP: drop open request from 87.212.3.209/50247
printk: 12 messages suppressed.
TCP: drop open request from 46.151.132.87/50752
TCP: drop open request from 200.138.112.107/50345
TCP: drop open request from 66.110.158.117/51739
TCP: drop open request from 24.14.89.230/50938
TCP: drop open request from 79.4.164.21/59061
TCP: drop open request from 89.11.142.22/60732
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
egiga0: link down
egiga0: link up, full duplex, speed 1 Gbps
TCP: drop open request from 190.80.136.12/34878
TCP: drop open request from 221.235.50.53/60637
TCP: drop open request from 119.154.150.38/50563
TCP: drop open request from 88.23.183.168/49490
TCP: drop open request from 58.96.44.91/4087
TCP: drop open request from 129.97.246.50/53313
TCP: drop open request from 125.34.164.69/58074
TCP: drop open request from 117.240.70.1/53926
TCP: drop open request from 71.206.2.78/54893
TCP: drop open request from 69.114.137.187/53024
TCP: drop open request from 82.5.60.234/63139
printk: 6 messages suppressed.
TCP: drop open request from 77.31.5.194/62292
printk: 54 messages suppressed.
TCP: drop open request from 189.18.24.249/60012
printk: 45 messages suppressed.
TCP: drop open request from 50.33.165.72/51179
printk: 76 messages suppressed.
TCP: drop open request from 121.8.46.0/7507
printk: 129 messages suppressed.
TCP: drop open request from 82.33.96.96/55807
printk: 122 messages suppressed.
TCP: drop open request from 109.54.219.175/50831
printk: 144 messages suppressed.
TCP: drop open request from 186.42.222.33/13557
printk: 163 messages suppressed.
TCP: drop open request from 46.177.177.243/62507
printk: 113 messages suppressed.
TCP: drop open request from 78.245.1.74/56863
printk: 106 messages suppressed.
TCP: drop open request from 61.224.78.175/63772
printk: 80 messages suppressed.
TCP: drop open request from 186.105.93.131/51144
printk: 55 messages suppressed.
TCP: drop open request from 46.193.133.124/53793
printk: 133 messages suppressed.
TCP: drop open request from 81.23.165.223/55272
printk: 96 messages suppressed.
TCP: drop open request from 86.101.124.70/29898
printk: 48 messages suppressed.
TCP: drop open request from 109.225.78.164/63523
printk: 56 messages suppressed.
TCP: drop open request from 180.154.180.190/4171
printk: 53 messages suppressed.
TCP: drop open request from 76.92.215.119/65296
printk: 66 messages suppressed.
TCP: drop open request from 86.136.148.58/62968
printk: 23 messages suppressed.
TCP: drop open request from 108.83.120.83/2452
printk: 24 messages suppressed.
TCP: drop open request from 84.73.26.12/49882
printk: 54 messages suppressed.
TCP: drop open request from 1.64.121.6/42986
printk: 14 messages suppressed.
TCP: drop open request from 92.24.156.16/16429
printk: 16 messages suppressed.
TCP: drop open request from 84.52.163.208/61488
printk: 7 messages suppressed.
TCP: drop open request from 95.21.15.85/54478
printk: 13 messages suppressed.
TCP: drop open request from 114.34.119.127/1768
printk: 5 messages suppressed.
TCP: drop open request from 98.26.97.8/4160
printk: 22 messages suppressed.
TCP: drop open request from 85.138.111.245/65431
printk: 18 messages suppressed.
TCP: drop open request from 80.178.8.208/62573
printk: 62 messages suppressed.
TCP: drop open request from 82.33.96.96/56065
printk: 103 messages suppressed.
TCP: drop open request from 71.56.8.11/59898
printk: 99 messages suppressed.
TCP: drop open request from 61.83.75.179/6224
printk: 115 messages suppressed.
TCP: drop open request from 178.254.175.185/56132
printk: 81 messages suppressed.
TCP: drop open request from 207.6.236.247/60304
printk: 49 messages suppressed.
TCP: drop open request from 151.48.37.19/63808
printk: 31 messages suppressed.
TCP: drop open request from 24.147.240.181/59011
printk: 15 messages suppressed.
TCP: drop open request from 89.46.113.78/16387
printk: 5 messages suppressed.
TCP: drop open request from 83.101.13.52/63246
TCP: drop open request from 86.97.223.159/57446
printk: 1 messages suppressed.
TCP: drop open request from 87.231.7.164/54392
TCP: drop open request from 71.238.28.204/52640
TCP: drop open request from 39.54.215.183/62484
TCP: drop open request from 80.179.225.42/21673
TCP: drop open request from 207.6.238.22/37812
TCP: drop open request from 67.175.133.94/58844
TCP: drop open request from 84.3.112.85/53251
TCP: drop open request from 108.76.103.168/54524
printk: 2 messages suppressed.
TCP: drop open request from 69.254.227.114/50683
printk: 8 messages suppressed.
TCP: drop open request from 58.8.5.60/11997
printk: 1 messages suppressed.
TCP: drop open request from 219.74.15.248/3186
printk: 2 messages suppressed.
TCP: drop open request from 142.167.126.31/60010
TCP: drop open request from 199.192.234.85/58102
printk: 2 messages suppressed.
TCP: drop open request from 183.38.74.4/3182
printk: 3 messages suppressed.
TCP: drop open request from 85.240.120.226/54160
TCP: drop open request from 130.113.193.122/58978
TCP: drop open request from 75.71.211.75/63945
TCP: drop open request from 71.174.169.175/50934
TCP: drop open request from 71.68.238.24/59556
TCP: drop open request from 82.231.17.235/56641
printk: 1 messages suppressed.
TCP: drop open request from 221.194.183.5/17537
TCP: drop open request from 125.39.134.40/28201
printk: 14 messages suppressed.
TCP: drop open request from 187.113.60.74/25841
printk: 10 messages suppressed.
TCP: drop open request from 83.86.217.90/63380
printk: 13 messages suppressed.
TCP: drop open request from 93.164.224.178/3571
printk: 17 messages suppressed.
TCP: drop open request from 41.56.199.109/49832
printk: 38 messages suppressed.
TCP: drop open request from 201.78.108.253/42434
TCP: drop open request from 76.106.21.36/52387
TCP: drop open request from 46.61.22.210/65116
printk: 9 messages suppressed.
TCP: drop open request from 23.16.53.222/49344
TCP: drop open request from 124.244.142.231/59507
printk: 1 messages suppressed.
TCP: drop open request from 94.4.45.121/49764
printk: 8 messages suppressed.
TCP: drop open request from 212.108.204.4/62535
printk: 10 messages suppressed.
TCP: drop open request from 196.20.161.182/50198
printk: 1 messages suppressed.
TCP: drop open request from 88.156.157.240/56724
printk: 3 messages suppressed.
TCP: drop open request from 173.77.213.52/44575
TCP: drop open request from 78.86.79.80/58739
TCP: drop open request from 86.96.110.176/53871
TCP: drop open request from 222.138.28.144/50794
TCP: drop open request from 87.214.86.125/54479
TCP: drop open request from 196.210.197.195/61297
TCP: drop open request from 201.58.198.120/54064
printk: 2 messages suppressed.
TCP: drop open request from 85.75.83.29/11666
TCP: drop open request from 202.83.27.220/4721
TCP: drop open request from 108.27.201.31/53397
TCP: drop open request from 208.168.235.74/51342
TCP: drop open request from 84.251.60.158/51440
TCP: drop open request from 80.56.150.244/3322
TCP: drop open request from 70.138.65.223/58613
TCP: drop open request from 187.114.102.58/57368
TCP: drop open request from 60.30.249.66/2639
printk: 101 messages suppressed.
TCP: drop open request from 89.142.73.57/54830
printk: 24 messages suppressed.
TCP: drop open request from 182.55.133.29/58247
printk: 4 messages suppressed.
TCP: drop open request from 213.37.188.101/20994
TCP: drop open request from 119.129.254.32/49536
TCP: drop open request from 187.56.134.241/51910
TCP: drop open request from 86.179.133.49/51136
TCP: drop open request from 79.168.78.156/3042
printk: 2 messages suppressed.
TCP: drop open request from 109.209.209.44/63169
printk: 3 messages suppressed.
TCP: drop open request from 121.54.58.153/40970
TCP: drop open request from 186.212.100.134/3120
printk: 5 messages suppressed.
TCP: drop open request from 92.96.126.144/54143
TCP: drop open request from 46.102.0.234/61537
TCP: drop open request from 177.97.33.76/61357
TCP: drop open request from 176.14.17.209/54055
TCP: drop open request from 91.181.187.184/53520
TCP: drop open request from 41.205.14.189/7065

Last edited by Fobio (2012-02-12 21:13:11)

I need some help regarding Transmisson.

I have been running Transmission for the last 3 years, but after i did the firmware 1.10 update on the DNS-323 i'm not able to have peers or seeds anymore. Dosent matter if it's private or public trackers, all of them shows zero in seeds and peers, and every tracker is saying in status "Tracker did not respond"
My setup:
Netgear CG3000 Router, with port forward to my DNS-323, when I test the port on http://www.canyouseeme.org/ , everything it OK and working. On DNS-323 I have ffp 0.5, and SSH enabled, I have installed Transmission 2.42 and everthing used to work, but not now :-(
I have tryed to downgrade Transmission from 2.42 to 2.32 to 2.2 and back again, put it dosent help.
I have tryed to stop and restart Transmission, but didnt solve the problem. So do anyone have any idears of some usefull hints how to solve or where to look for a fault if any?

Fobio wrote:

Anyway, what I've also noticed that everytime transmission shuts down on its own, and when I restart it, it loses all its seed/leechers info and start off again @ 0/0 for seeders and leechers...

Perhaps it's a case of where a file never got saved properly and it's preventing transmission from working properly?

Do you use jumbo frames? If yes, try to decrease frame size. I had similiar behavior when switched on jumbo frames...

Last edited by Nuri (2012-02-13 19:17:51)

Does anyone have a download mirror for the transmission version from the topic start? Because I can't seem to be able to download it of Kylek's download location.
(I need the 0.5 version)

Last edited by Wilibrord (2012-02-13 22:10:51)

Thanks alot!

KyleK wrote:

You're right in that you need a Transmission version compiled for ffp-0.7-oarm. The version from the first post will not work.

Mijzelf has apparently a Transmission 2.42 for 0.7-oarm, but he reports that it does not really work for some reason (it runs, but doesn't connect to any peers).

Unfortunately, I haven't had the time yet to look into it, and that won't change for a while

I suggest that owners of the older NASes (DNS-323, CH3SNAS), stay with ffp-0.5 for now.

From what I've gathered, it seems that it may work if the following packages are installed.  I do not have time myself to upgrade to 0.7 right now, but if someone does, please let us know if the following works:

libevent-2.0.16-oarm-0.txz
transmission-2.42-oarm-1.txz
uClibc-0.9.33_git-oarm-1.txz
curl-7.21.4-oarm-1.txz

Thanks

Hey everyone. Transmission v2.50 is out and about.
You can grab packages for ffp-0.5 and ffp-0.7-arm from the first post.

As always, enjoy, and let me know how it goes

supertwister wrote:

Hey new guy here, although I've been reading these forums since a couple of weeks.

I installed ffp 0.7 on my DNS-323 and wanted to try transmission. All of the 4 packages you listed are installed and transmission does work (I can download) but it does not seem very stable. Some torrents do not work, sometimes it times out for no reason and it also crashes.

Note that I had to edit the transmission.sh start script. In the instructions on the first page, the first command you enter to specify the config folder location will indeed create the folder are the desired location, but the start script points to some default folder somewhere else. Make sure the two match.

One thing that I have not been able to make work are blocklists. I've tried putting them in the folder, it does see the file but then creates an empty bin file (tells me that all of the ips are invalid or something), and imputing them in the web interface does not seem to work.

Hope it helps.

Thanks for the great work.  Looks like we might need some pros on this one.  If anyone wants to help us legacy hardware users, it would be greatly appreciated (and hopefully rewarding to figure this out)!

hey everyone.

now i use http://downloads.zyxel.nas-central.org/ … oarm-1.txz


where can i find Transmission-2.50_oarm-1.txz?

thank.

Hello Gentelmans,

first I would like thanks to Kylek. I used to Transmission on DNS-323 very long time and I was very happy with it (your manuals are great for non-linux people like me:), this forum etc).

But I bought new storage DNS-345 and now I am trying to install transmission there. I know this thread is for DNS-323, but I do not know where Can I ask.
I installed on DNS-345 fun_plug 0.5 then I followed Kylek instructions ( http://www.shadowandy.net/2009/01/trans … ns-323.htm )

Installing uclibc was correctlly done, but step no. 4 is different. Correct path is in my case "cd /mnt/HD/HD_a2"
And this is the problem, I think.

Installing Transmission in next part, step 9 is not succesfull like with DNS-323, but I will get this error:

/mnt/HD/HD_a2 # chmod a+x /ffp/start/transmission.sh;sh /ffp/start/transmission.sh start mkdir: cannot create directory '/mnt/HD_a2/.transmission-daemon': No such file or directory
Starting transmission-daemon Couldn't open "/mnt/HD_a2/.transmission-daemon/transmission-daemon.log": No such file or directory/mnt/HD/HD_a2 # edit /ffp/start/transmission.sh/ffp/bin/sh: edit: not found

I am not Linux guy, so how can I change the path from  '/mnt/HD_a2/.transmission-daemon' to '/mnt/HD/HD_a2/.transmission-daemon' . Can I edit this path somewhere? Or is it different problem..?


Thanks for you help

BartCZ wrote:

Installing Transmission in next part, step 9 is not succesfull like with DNS-323, but I will get this error:

/mnt/HD/HD_a2 # chmod a+x /ffp/start/transmission.sh;sh /ffp/start/transmission.sh start mkdir: cannot create directory '/mnt/HD_a2/.transmission-daemon': No such file or directory
Starting transmission-daemon Couldn't open "/mnt/HD_a2/.transmission-daemon/transmission-daemon.log": No such file or directory/mnt/HD/HD_a2 # edit /ffp/start/transmission.sh/ffp/bin/sh: edit: not found

I am not Linux guy, so how can I change the path from  '/mnt/HD_a2/.transmission-daemon' to '/mnt/HD/HD_a2/.transmission-daemon' . Can I edit this path somewhere? Or is it different problem..?

There are some hardcoded paths in the startup script (/ffp/start/transmission.sh). You can just open this file with a text editor (vi or nano on the device) and change the paths.

Last edited by KyleK (2012-02-26 01:13:13)

Hi, what i need to do to install the libcurl?
Because i have downloaded the curl for the 0.7 posted in this page, and i have opened the txz and extracted in my ffp directory. But when i run the start script for transmission it say libcurl.so.4 is not an elf file.

EDIT: i have tried to copi curl-7.21.4-arm-1.tar into the root and give an funpkg -i curl-7.21.4-arm-1.tar but it say "invalid package name".

I have a DNS-320 (but this method should work even with it) and FFP 0.7

Last edited by dejawho (2012-03-02 00:31:29)

It's important to not mix packages for ffp-0.5 and ffp-0.7. Therefore I've updated the first post to make the difference a bit more clear.
Please note that I currently don't have packages for ffp-0.7-oarm/oabi!


@dejawho: Don't manually extract packages and copy them somewhere. Use funpkg instead:

$ funpkg -i curl-7.21.4-arm-1.txz