Print

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

[FurryNutz]

D-Link posted DNS-320L firmware version v1.09 B06, which can be downloaded here: DNS-320L.
04/05/2017

HW Versions Supported:
DNS-320L A1/A2/A3
DNS-320LW A1/A2

Problems Resolved:
1. Fix the photos modification date change while photos uploaded via My Photos or Mobile APP
2. Remove the share to Picasa function, according to Picasa service is terminated.

New Features:
None

Enhancements:
Several system security enhancements.
1) Support mydlink new UID design
2) Update OpenSSL to 1.0.2h
3) Fix the buffer overflow in the discovery protocol message handler
4) Fix the Command injection in CGI
5) Fix the exploitable stack overflow in the binary
6) Fix the security issue on Lighttpd configuration
7) Fix the command injection


Let us know how it works for you...

[tnk]

Same issue with ssh daemon as on 1.08 B08: http://forums.dlink.com/index.php?topic=66389.msg280978#msg280978 And any particular reason to use ssh-dss which is disabled by default as weak option in openssh 7.0+?

[FurryNutz]

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

[mpcr]

On the "Enhancements or New features" section... It brings  dropbox client api/app as default app...

In regarding the dropbox api...

There seem to exist some limitations/bugs (it does seem to repeatedly fail to sync 33GB file and some zip files), I set the api to sync with dropbox every hour and api doesn't seem able to sync a file over 9.9GB size. However copying the 33GB file from PC dropbox into the DNS320L network share, it just copied into the DNS320L with no file size issues... so I point at the DNS320L dropbox api as the having a problem/limitations with certain files (zips) and with dropbox files over certain size.

Also, the dropbox api/app information only appear on the DNS320L log, the api is quite basic with no settings other than set the dropbox home dir and how frequent to sync with dropbox plus account details... No options on what to sync neither network bandwith cap...

Comparing the full sync of a 268GB dropbox (DNS320L vs windows 7 PC with dropbox client) the PC beats the DNS320L dropbox sync by several days... DNS320L dropbox took near a week. To add that PC and DNS320L are connected directly to ISP fiber router. The download test rated between 44MB-57MB/second and upload 12MB-17MB/s.

As request for enhancement goes:

- It would be nice the DNS320L dropbox api allowed at least the selection of network bandwidth because present download rate seems extremely slow (unsure if this is a limitation hardcoded on the dropbox api or on DNS320L).
- With dropbox api minimal information logged onto DNS320L log, really does not help debuging why dropbox  files do fail to sync every hour when api attempts to sync them; so reason for failed sync would be helpful to have rather than simple "files/dirs sync Y and files/dirs failed X".

[FurryNutz]

Something you might want to phone connect with D-Link support about. Ask for escalated support.

On the "Enhancements or New features" section... It brings  dropbox client api/app as default app...

In regarding the dropbox api...

There seem to exist some limitations/bugs (it does seem to repeatedly fail to sync 33GB file and some zip files), I set the api to sync with dropbox every hour and api doesn't seem able to sync a file over 9.9GB size. However copying the 33GB file from PC dropbox into the DNS320L network share, it just copied into the DNS320L with no file size issues... so I point at the DNS320L dropbox api as the having a problem/limitations with certain files (zips) and with dropbox files over certain size.

Also, the dropbox api/app information only appear on the DNS320L log, the api is quite basic with no settings other than set the dropbox home dir and how frequent to sync with dropbox plus account details... No options on what to sync neither network bandwith cap...

Comparing the full sync of a 268GB dropbox (DNS320L vs windows 7 PC with dropbox client) the PC beats the DNS320L dropbox sync by several days... DNS320L dropbox took near a week. To add that PC and DNS320L are connected directly to ISP fiber router. The download test rated between 44MB-57MB/second and upload 12MB-17MB/s.

As request for enhancement goes:

- It would be nice the DNS320L dropbox api allowed at least the selection of network bandwidth because present download rate seems extremely slow (unsure if this is a limitation hardcoded on the dropbox api or on DNS320L).
- With dropbox api minimal information logged onto DNS320L log, really does not help debuging why dropbox  files do fail to sync every hour when api attempts to sync them; so reason for failed sync would be helpful to have rather than simple "files/dirs sync Y and files/dirs failed X".