D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-321 => Topic started by: alan3885 on February 20, 2009, 06:58:25 PM
-
D-Link please consider adding the following features D-Link for the DNS-321 in a future firmware update:
- 802.11p (QoS)
- Improved iTunes server
- Fix the fan cycle issue
- Advanced Encryption Standard (AES) file-based disk encryption
- FTPS (for secure FTP file sharing using SSL)
Any other suggestions? Please add onto the list. :D
-
Have unit stay up without crashing on long file transfers.
Allow temperature to be set without an email alert.
Add NFS access (faster than SMB/Samba).
-
Support xxx.xxx.0.xxx ip address or atleast tell me about the bug next time...geese...
Support for streaming files more than 2 folders deep
Increase file name and folder name character limit
-
EXT3 filesystem as a standard option. Why was EXT2 (non-journaling) chosen in the first place? (Or is this a legacy thing from the NDS-323?)
-
Make sure you read up on the Release notes for 1.02 in the beta forum. Some of your requests are already met.
-
Ah, thanks (it didn't even occur to me to click on that icon in the forum.) Nice work guys!
-
Shadow Copies/Drive Snapshots as an option. It would make this NAS device just awesome. I use it to back up my and my wife's laptops but I also use it as a file server. It need some sort of back-up.
-
UPnP AV: support for MKV, OGG, FLAC
-
1. Provide the capability to convert from single drive operation to RAID 1 mirror without backing everything up, formatting both drives, and writing it all back out again. When the user inserts a second disk, the firmware should allow the user to
2. Provide ability to "grow" mirrors by installing larger drives one at a time. For example, say that I have a pair of 320GB drives. I should be able to replace one with a 1GB drive and rebuild the mirror. Then I should be able to replace the remaining 320GB drive with a second 1GB drive and, again, rebuild the mirror. At that point, the DNS-321 should automatically increase the partition size to use the full disks. So I swap one out in the morning, swap the second one out when I get home from work, and then the next day I have a larger array.
3. Add ability to support passive mode FTP. This would require that the unit "know" what the public IP address was (if the router was port-forwarding) and that the PASV port range be able to be specified by the user.
4. Add a mail server. Now you have a complete presence for a small business: Web site, FTP site, and e-mail.
5. Add jumbo frame test. If someone selects jumbo frames, the DNS-321 should initiate a test to ascertain whether it can still communicate with the host system and also to help the user select the best jumbo frame size based on throughput. No communications should result in jumbo frames being automatically turned back off.
6. Ability to "daisy-chain" to achieve RAID 5. Imagine two DNS-321s with one taking the master role and the other the slave. The master would do a RAID 0 stripe across two drives while the slave would XOR each sector and write it to its internal drives. If any one of the two master drives went down, the secondary unit could provide the data necessary to reconstruct the missing drive's data until the drive was replaced. Would it be slower? Sure, but the user could buy three 1TB drives and get 2TB of RAID 5 space. And D-Link would sell more DNS-321 units.
P.S. I'll cast my vote against trying to support a bunch of different codecs for AV. Space is limited, both RAM and flash, and there are more useful features associated with NAS that should be implemented first. I am the moderator for the Exact Audio Copy forum on Yahoo! and I've seen too many issues related to codecs to think that it's a good idea to put a bunch of them into a small, inexpensive, slow NAS box.
-
Probably not going to happen, but for the OS X users out there (like me :)), AFP would be nice.
-
How about a manual "Clone HD" option that invokes the dd command directly on the unit.
That way you can clone one HD to the another without transferring all data across the network.
The idea came from wanting to clone before reformatting each drive to EXT3.
-
I don't know if this has already been discussed, but a web server (apache or lighttpd) would be really great. doesn't seem like too much work either.
Thanks