Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[albert]

What is the reason why add-on are not available for DNS-320? Can any of the existing add-on, for example those meant for DNS-320L be use for DNS-320?

[albert]

Anyone?

[vtverdohleb]

DNS-320 does not support Addons. ONLY supports the following models: DNS-320L / DNS-325 / DNS-327L / DNS-340L / DNS-345.

[albert]

But what's the reason for the lack of support?

[FurryNutz]

Maybe due to the direction and target market for the 320 was for a budget and simplistic buyers. also the 320 is getting to be about 3 years old so maybe headed towards being phased out as far and FW development and support life. 

[masterxilef]

Yeah, main reason is that addons are not compatible with the firmware. Although hardware could maybe run most of them, as ther run fine on ffp.

[albert]

Maybe due to the direction and target market for the 320 was for a budget and simplistic buyers. also the 320 is getting to be about 3 years old so maybe headed towards being phased out as far and FW development and support life. 

Actually this model should be around 5yrs old, I brought mine back in 2010. Its product status is already classified as "Phased Out" since Sep 1, 2012 but continue to receive support from D-Link.

Anyway, perhaps it's my own wishful thinking to expect any kind of support for an EOL product. 

[albert]

Yeah, main reason is that addons are not compatible with the firmware. Although hardware could maybe run most of them, as ther run fine on ffp.

I doubt there is an issue with firmware compatibility, just the lack of option to configure these addons. If one would to check the NAS webUI coding, there is still some remnant code related to these but was commented off.

[FurryNutz]

Once a product hits EOL, unless there is a security issue found, no other features would be fixed or added at this point. And again, early design and target market of this model DNS, may not have included any add-ons or was meant to have them. 

Maybe due to the direction and target market for the 320 was for a budget and simplistic buyers. also the 320 is getting to be about 3 years old so maybe headed towards being phased out as far and FW development and support life. 

Actually this model should be around 5yrs old, I brought mine back in 2010. Its product status is already classified as "Phased Out" since Sep 1, 2012 but continue to receive support from D-Link.

Anyway, perhaps it's my own wishful thinking to expect any kind of support for an EOL product. 

[masterxilef]

Yeah, main reason is that addons are not compatible with the firmware. Although hardware could maybe run most of them, as ther run fine on ffp.

I doubt there is an issue with firmware compatibility, just the lack of option to configure these addons. If one would to check the NAS webUI coding, there is still some remnant code related to these but was commented off.

Yeah, that's what I meant, sorry, english not my native language, as I said, most software would run fine under the native os, as they run in ffp, but because is not enabled by the firmware there not much to do about it other than using ffp.

[albert]

Doesn't matter, I try to figure it out by myself, actually all I wanted to know is how the addon is being packaged.

[masterxilef]

If you are really interested have a look here: http://ftp.dlink.ru/pub/NAS/DNS-327L/Add-on/
Basically, you need the files that are name SDK.

Building an addon it's relatively simple if you know a little about linux. What the addons for this nases does is symlink the files for the program to the core os of the nas (linux), and using a set of files that tell the nas to autostart the program, stop it or delete it, etc.

About packaging, inside the file is a 32bit binary that packages the addon to a compatible format for the nas. And as far as I know, you can´t extract it in linux or windows.

If you say there are some remnants of the addons code in the 320 firmware, maybe you can look on how to enable it.

Hope this helps you.

[albert]

I am well aware of this information but all it has is on creation of addon, I need info on how to extract it,I assumed it must be in some kind of archive format.

[vtverdohleb]

I am well aware of this information but all it has is on creation of addon, I need info on how to extract it,I assumed it must be in some kind of archive format.

What Addons are you interested in? Can you give the archive .TAR.GZ

[ACME_Corp]

Using the SDK I've managed to convert DNS-320L addons to DNS-320B.

HOWTO:
Download the package you want to convert (DNS-320L Twonky Package v2.06_07212015_UA)
Extract the files with binwalk :
binwalk -v -e "Twonky Package v2.06_07212015_UA"
Untar the generated C8 file "tar -xvf C8"
Enter the newly  created directory "cd Twonky"
Generate  the package for DNS - 320B "mkapkg -m DNS-320B"

Now you can upload the package to your NAS using "/web/app_mgr/module.html" wich is inside it but somehow disabled.
Navigate to Administration / Application Management / Right click on Multimedia Services / Inspect Element
and change /web/app_mgr/media_share.html to /web/app_mgr/module.html now click on Multimedia Services and then you just got to select the file previously created "DNS-320B Twonky Package v2.06_07212015(BETA)" and Apply. Once it's been uploaded and installed you can enable it.