Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

NAS Reviews

Under the covers

I recently picked up one of those little devices that measures electricity usage of a plugged-in device. Using this little box, I measured the usage of the NetCenter at 12 W while in use and 4W when the drive spun down after 10 minutes. So think of it as using about the same amount of electricity as a night light.

In terms of the hardware used on the box, I usually like to open up the case to photograph the main board, but the NetCenter's case was tightly sealed with plastic compression clips. I didn't want to risk breaking or marring this loaner unit, so I used software techniques to get some hints about the hardware.

Like nearly all consumer NASes, it was clear that the NetCenter runs Linux internally. A port-scan of the box told me the OS used is based on a Linux 2.4 kernel. But for more detailed information about the software running on the box, Western Digital provides a download link where I grabbed the GPL components used in the product. Those brave enough to build their own custom firmware will also find a full compilation tool-chain at this site.

Digging through the provided source tree turns up the usual components found in these products. For basic utilities, busybox is used and CIFS support comes courtesy of Samba. The tree also contains utilities for managing a Reiser filesystem, so that's a strong hint regarding the internal filesystem. I was also interested to see an FTP server and number of utilities related to the use of VPNs, but I found no evidence that these features used internally.

The presence of these unused packages may just indicate that this source tree is used in other products, or it could also give some indication of future direction for Western Digital with this product. It was fairly clear that the internal processor used on the box was from Broadcom. A number of Broadcom directories were present along with references to a 4710 chip which provides the main CPU as well as network connectivity. In another Broadcom directory, I found an IDE driver for an Acard ATP864 chip.

More NAS

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I had hopes that using an RT-AX88U (router on one side of my house) and RT-AX86U (node in the middle of the house) together in an AiMesh configuration...
Author's Note: The original review can be found at my blog - Asus RT-AX86U vs RT-AC86U @ RT-AX86U is an excellent Wi-Fi 6 router. Pe...
Is there a practical limit to how many clients it can handle (in AP mode if it matters)? Atm I have around 20 clients connected, most to 2.4GHz, some ...
HiI'm looking for switch that can handle 2.5G. It can be 10G overall but has to be able to properly handle 2.5G because that's what my home network wi...
This thread is for the discussion topic : unbound_manager script. As per the GitHub Hints/Tips: Differences between the operational modes​ E...

Don't Miss These

  • 1
  • 2
  • 3