Print

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

[Manul]

When I try to save my configuration settings via "System Management"->"System Settings"->"Configuration Settings"->"Save Configuration Settings" my browser downloads a file "backup" - which is, unfortunately, empty.

Is this a known issue? Is there an alternative way to download the settings? I have ssh access to the DNS320L via ffp - which is also why I don't want to upgrade to a newer firmware currently.

Any insight appreciated. Thanks in advance!

[ivan]

Have you tried using a different browser?  In the past there have been problems with browser versions and how they do things like page rendering, file save and other things.

[Manul]

Thank you for the suggestion, ivan! I have just tried a different browser on a different computer on a different OS with the same result.

Meanwhile, I've found a file /etc/NAS_CFG/config.xml on the DNS-320L. This file has 437 lines, starts with

Code: [Select]

<config>
<sw_ver_1>1.04b12</sw_ver_1>
<sw_ver_2>3.07.1226.2014</sw_ver_2>
<hw_ver>DNS-320L</hw_ver>
<network_mgr>
<web>
<ssl_enable></ssl_enable>
<ssl_port>443</ssl_port>
</web>
<lan0>

and ends with

Code: [Select]

<dest></dest>
<type>0</type>
</usb_backup>
<mtp_backup>
<enable>0</enable>
<dst></dst>
</mtp_backup>
</download_mgr>
<media></media>
</config>

Does this look like a valid config file that could be reuploaded via the web interface?

[FurryNutz]

I'm wondering if upgrading to v1.07 maybe an option...

[Manul]

As mentioned in my first post: Not really. I have ssh access and a script for incremental backup to an external disk nicely set up in ffp which, as I understand, is no longer supported in FW1.07. I would probably be able to get it working again on the new firmware, but frankly, I'm a bit shy of the effort involved.

I'd still appreciate if someone for whom the feature works could try it out and tell me what the resulting file is named and looks like and whether it bears any similarity to the config.xml file I found on the device.

[FurryNutz]

Ya, lets see if others see the same issue or not. So far you've been the first to post about this so not sure what others are seeing, if anything. 

[Manul]

I don't believe that there's actually nobody on these forums who owns a DNS-320L and is willing to help me out, so I'll assume my request somehow got overlooked and will take the liberty to repeat it:

Anybody out there with a working DNS-320L, any firmware: Could you please maneuver to "System Management"->"System Settings"->"Configuration Settings", click on "Save Configuration Settings" and answer the following short questions for me?

• Does your browser download a file?
• What is its name?
• What is its size?
• What do the first and last couple of lines look like? (Make sure they don't contain any sensitive information before posting!)

Thank you very much in advance for the effort involved in helping me out!

All the best,

Manuel

[FurryNutz]

You may want to phone contact your regional D-Link support office and ask for help and information regarding this while you wait for feedback here. You seem to be the only one currently posting about this. Hope others will give feedback.

[ivan]

Sorry if I'm a bit late looking back at this.

First is the file 'backup' that is saved as a 0kb file or does it have a size of about 5kb?
What are you using to view the contents of the file?

If it is 0kb then nothing was transferred.  If it is about 5kb then you have the backup of the config settings.
The file is a binary file and as such the contents will not appear in a text editor (using a text editor to view the file could well wipe it), you need a binary file reader.

I have just had a look at the saved backup files from the DNS-320L boxes that some of our clients have and I don't see anything wrong with them but then we haven't tested a restore for the simple reason we haven't needed to (we also have the config written down and filed).

Sorry I can't be of much help.

[Manul]

Thanks for your reply, ivan! The file is actually 0 bytes in length, so definitely nothing hidden in there. Interestingly, when the browser downloads it, it reports a MIME type of "text/plan" (sic!).

If you have a Linux box handy, could you do a "file <backupfile>"? Maybe it's some sort of compressed format (.zip,.gz,.tgz etc.) that just lacks the descriptive suffix. Is your customer's file called "backup" as well?

[Manul]

FWIW, if I create a .tgz of /etc/NAS_CFG (containing 4 files config.xml, ftp.xml, gui_admin.xml, p2psettings.xml) the resulting file comes out at 3311 bytes, so with the older FW version that seems at least on the same order as your config file.

[ivan]

OK, I have had a dig around while I watch the daily backups arriving.

The file 'backup' is a tar.gz without the suffix, and from what I can see they are all called 'backup'.

Opening the file I get:

drwxr-xr-x root/root           0 2015-08-17 16:26 backup/
-rw-r--r-- root/root              0 2015-08-17 16:26 backup/DNS-320L
drwxr-xr-x root/root           0 2015-08-17 16:26 backup/quota/
-rw-r--r-- root/root           133 2015-08-17 16:26 backup/quota/backup_quota_tab.a
-rw-r--r-- root/root         1524 2015-08-17 16:26 backup/smb.conf
-rw------- root/root          206 2015-08-17 16:26 backup/smbpasswd
-rwxr-xr-x root/root        194 2015-08-17 16:26 backup/shadow
-rwxr-xr-x root/root        303 2015-08-17 16:26 backup/passwd
-rwxr-xr-x root/root         82 2015-08-17 16:26 backup/hosts
-rwxr-xr-x root/root         35 2015-08-17 16:26 backup/group
-rwxr-xr-x root/root        601 2015-08-17 16:26 backup/mt-daapd.conf
-rwxr-xr-x root/root         50 2015-08-17 16:26 backup/resolv.conf
-rwxr-xr-x root/root       593 2015-08-17 16:26 backup/rc.init.sh
-rw-r--r-- root/root             0 2015-08-17 16:26 backup/blockip
-rw-r--r-- root/root        8070 2015-08-17 16:26 backup/config.xml
-rw-r--r-- root/root           96 2015-08-17 16:26 backup/gui.xml
-rwxr-xr-x root/root       285 2015-08-17 16:26 backup/sms_conf.xml
-rwxr-xr-x root/root        44 2015-08-17 16:26 backup/passwd.webdav
drwxr-xr-x root/root         0 2015-08-17 16:26 backup/a/
-rw-r--r-- root/root        545 2015-08-17 16:26 backup/a/.smb.xml
-rw-r--r-- root/root        273 2015-08-17 16:26 backup/a/ftp.xml
drwxr-xr-x root/root         0 2015-08-17 16:26 backup/a/schedcfgs/
-rw-r--r-- root/root        684 2015-08-17 16:26 backup/a/schedcfgs/00000013052169920197.xml
-rw-r--r-- root/root        100 2015-08-17 16:26 backup/a/.timeMachine.xml
drwxr-xr-x root/root         0 2015-08-17 16:26 backup/b/
-rw-r--r-- root/root        545 2015-08-17 16:26 backup/b/.smb.xml
-rw-r--r-- root/root        273 2015-08-17 16:26 backup/b/ftp.xml
-rw-r--r-- root/root        100 2015-08-17 16:26 backup/b/.timeMachine.xml

the numbers before the 2015 are the file size.
there are two sub directories 'a' and 'b' with 'a' having another sub directory in it.

I assume the zero length file is because the browser is using MIME 'text/plain' which is wrong it should be MIME 'binary'.

Hope this is of help.

[Manul]

Thank you, ivan. I will have a closer look at this tomorrow.

As for the MIME type: It's actually "text/plan" without the 'i', reported by two different browsers on two different OS's, so I suspect it's not a browser problem but some misconfiguration on the DNS-320L's side.

[Manul]

Thanks once more, I figured it out, at least to some extent. The strange MIME type put me on the track:

First, I tried to find its origin:

Code: [Select]

root@platte:~# find /usr/local/modules/ -xdev -type f -print0 | xargs -0 grep "text/plan"
Binary file /usr/local/modules/cgi/app_mgr/app_mgr.cgi matches
Binary file /usr/local/modules/cgi/mydlink.cgi matches
Binary file /usr/local/modules/cgi/system_mgr.cgi matches
Binary file /usr/local/modules/cgi/webfile_mgr.cgi matches

(searching in other mounts yielded no results)

Next, I looked at the most likely candidate:

Code: [Select]

strings /usr/local/modules/cgi/system_mgr.cgi|less
and found, amongst lots of other stuff

Code: [Select]

config_set -b >/dev/null
Content-Disposition: attachment;filename="backup";
Connection: Keep-Alive
Content-Type: text/plan
rm -rf /tmp/backup
rm -r /tmp/backup.tgz

This looked like it could be related to the config file saving, so I did a

Code: [Select]

root@platte:~# config_set --help
config_set: invalid option -- '-'
Usage:
    -b bakcup config to /tmp/config.tgz
    -r restore config from /tmp/config.tgz
    -s save restore config
    -t [compress type]: zip/tgz    -d enable debug

and tried a

Code: [Select]

config_set -b
which led to a "no space left on device" error.

A df showed that my root file system was indeed full and some further searching via du found a file "/mnt/HD_b4/.systemfile/.upnpav-db/upnpav.db" with a size of 11 MB dating back to January 2013. After I moved that out of the way, saving of the configuration settings worked again, yielding a gzipped tar file called backup weighing in at around 8kb. The contents of that file look very similar to what ivan posted, with some differences which are probably due to either different configuration settings or the different firmware version.

I had briefly toyed with using the DNS-320L as a UPNP server in the past but have long since disabled that feature. I guess the large DB file was a remnant of these attempts.

Thanks again to ivan and FurryNutz for taking an interest and putting me on the right track!

All the best,

Manuel

[ivan]

It's a little wonder that you got a zero length file when there was no place to create it.

The actual length and content of the file depends on what is activated, number of users and if they are in groups and so on.  The example I gave is for a box that only does backups for a specific piece of equipment hence it is rather minimal.

A nice bit of detective work.