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

Like most other consumer-level NAS devices on the market, the StorCenter was clearly running Linux. A network port-scan of the device turned up no interesting open ports, but a fingerprint scan identified the TCP/IP stack as being from a Linux kernel. Connecting to the UPnP server port manually from a Telnet window gave me the following string:

SERVER: Linux/2.6 UPnP/1.0 Iomega TwoPeas UpnP/1.0.0.53

To verify my findings, I found that Iomega included Linux 2.6.12 and other GPL source code on the installation CD. The Linux configuration file included indicates that a Realtek 8169 provides the gigabit Ethernet support. Digging a bit into Iomega's documentation, it appears that the StorCenter has 64 MB of RAM, and is running on a Freescale MPC8241 processor. The internal drive runs at 7200 RPM and is formatted with the EXT2 file system. (This was changed over to XFS as of firmware version v1.27.) The 250GB model I tested had 8 MB of cache, while the 160 GB model has 2 MB.

While I was browsing the folder sharing options, I noticed the following parameter tacked on to the end of the URL: "list_dir=/nethdd". Thinking that perhaps changing it would allow me to get some more visibility into the operation of the system, I manually removed the "nethdd" portion and re-submitted. Bingo! I was rewarded with a display of the top-level directory structure of the operating system, shown in Figure 17. Using this menu, I was able to share the operating system directories as well as the normal data directories.

Directory listing via simple modified URL

Figure 17: Directory listing via simple modified URL

Browsing through the read-only directories showed me a standard Linux system with PowerPC binaries and fairly heavy use of busybox for utilities and Samba for file sharing; this is a pretty standard combination with this type of device.

To check out what optional capabilities were provided in the busybox toolkit, I copied it over to my Power PC based KuroBox and verified that it would run there. Running it showed me that it didn't have a Telnet daemon included, which might have given me the ability to get a command shell on the running box. I suspect that with more effort, a user willing to risk his warranty could figure out a way to add custom code for additional functionality.

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 am pleased to announce the release of CakeQOS-Merlin!Current Version: 1.0.5 (Changelog)CakeQOS-Merlin is a custom add-on for supported Asus routers ...
Update 2020/12/01(9.0.0.4.386.41157)https://drive.google.com/drive/folders/1D4X3k9GXxkiRQkaO1huQGnCAsQeIvokC?usp=sharingThis version inclouds ZenWiFi:...
I have four Etekcity/VeSync smart wall plugs that I use for various lights in the house, and for the most part they work as intended, but they go offl...
This is FlexQoS, a fork of the original, groundbreaking FreshJR_QOS script written by @FreshJR.FlexQoS provides a fully customizable Adaptive QoS expe...
Hello,I'm having an issue with remote accessing my RT-AX86U from a faraway location. By faraway I mean a location that introduces 80+ ms of latency to...

Don't Miss These

  • 1
  • 2
  • 3