First and foremost, NAS4Free is a storage system. In order to be a storage system that is useful (what good is storage if you can't get it to store or retrieve things?), it must include file transfer protocols (some of which are referred to as “streaming”, which is a fairly useless designation, in general). This carves out a giant area that NAS4Free does. And it does those things expertly. ZFS creates a very stable storage platform. UFS can be used if you don't care about the integrity of your data, because it doesn't checksum the data, and it will gleefully return corrupted data to you as if it were 100% healthy. Then the list of available protocols for reading, writing, and moving files is quite comprehensive. NFS, SSH/SSHFS/rsync, SMB and HTTP make up a very comprehensive and useful block. Bittorrent, as a long-running, random availability protocol adds some very useful flexibility. AFP and novelty protocols like UPnP or iTunes add some misguided but commonly requested stuff and round out the protocol set pretty completely.
That being said, there are a good number of things that NAS4Free is not. Further, the list of things that NAS4Free is not are things that are unlikely to ever be supported. So pestering anyone about adding them, or how to install them will fall on deaf ears and only cause annoyance to others by asking. Worse, asking how to install ANYTHING will likely red-flag you as someone that is probably beyond help.
Among the things that NAS4Free is not, and should not ever be are the following items, which make up a non-complete list.
Just for the sake of completion, here's the following:
NAS4Free is not windows. Where windows has some things supported out of the box, and then has boatloads of things that require you to install drivers because MS is lazy, FreeBSD (like Linux) builds support for most hardware into the kernel or as kernel modules that are loaded automatically when/if the hardware is needed. What NAS4Free supports is what FreeBSD supports, and what FreeBSD doesn't support is just unsupported. Unlike the MS design, installing drivers (which are often binary blobs of black magic that nobody should trust in the first place) is not something any user should be doing. If the hardware is not supported, you should probably just swap it out for something that is supported and that works. Then wait for FreeBSD development to catch up to the hardware you want to use, and it is supported.
Yes, it may seem frustrating that your shiny new NIC or drive controller, or whatever won't work. But, installing drivers, especially closed-source-binary-blob-of-black-magic type drivers is entirely the wrong solution to the problem.
To address some grumbling I can already hear forming, here's some retorts to what I know people are probably about to ask: