Dual Band (Concurrent).
There are two versions:
WD has discontinued the whole My Net product line in early 2014; the original MSRP of N900 is around 149 USD, but as of late 2013 and early-to-mid 2014, N900 w/ 8x GigE can occasionally be had at a firesale price of as little as 39,99 USD (at Staples and some other retailers), going back and forth to a non-firesale price.
WD Downloads (GPL Source Code):
No OpenWrt support
|Ubicom IP8K@600MHz||256MB||16MB||-||7x 1GigE||1x 1GigE WAN||2x 2.0||1x TTL||-||-|
|Ubicom IP8K@600MHz||256MB||-||1TB/2TB||4x 1GigE||1x 1GigE WAN||1x 2.0||-||-||-|
# cat /proc/cpuinfo Vendor : Ubicom CPU : IP8K MMU : enabled FPU : enabled Arch : 4 Rev : 1 Clock Freq : 600.0 MHz DDR Freq : 533.0 MHz BogoMips : 589.82 Calibration : 294912000 loops Hardware : UbicomIP8K cpu : thread id - 6 cpu : thread id - 2 cpu : thread id - 3 cpu : thread id - 4 cpu : thread id - 5
# cat /proc/meminfo MemTotal: 253376 kB MemFree: 21664 kB Buffers: 84368 kB Cached: 66384 kB SwapCached: 0 kB Active: 110064 kB Inactive: 72448 kB Active(anon): 30480 kB Inactive(anon): 3808 kB Active(file): 79584 kB Inactive(file): 68640 kB Unevictable: 320 kB Mlocked: 0 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 32080 kB Mapped: 15328 kB Shmem: 2208 kB Slab: 34224 kB SReclaimable: 4816 kB SUnreclaim: 29408 kB KernelStack: 2480 kB PageTables: 2880 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 228032 kB Committed_AS: 145024 kB VmallocTotal: 262144 kB VmallocUsed: 3248 kB VmallocChunk: 116464 kB
This section explain some of the things you can do with the router firmware. It is not directly related to OpenWRT however, it is a necessary section as not much is known about this chip and some further research would be needed before OpenWRT comes true for this platform.
DISCLAIMER: Performing some of these procedures and what you can do with them may void your device's warranty. Furthermore, any of the following procedures and any of the activities you perform through this access may brick or damage your device as well as cause data loss or corruption. Please, use this guide at your own risk as neither the author nor this site can be held responsible.
This gives you user level access to your router as a non-privileged user. It is useful to wonder around with command line with certain safety as most of your system files will be protected against non-privileged users. However, it may be possible that certain data stored in the router, specially user data, may be still at risk of your actions. To achieve Telnet access you need to perform the following steps:
|My Net N900||Alphanetworks||wrgnd15_wd_pro|
|My Net N900 Central 1TB||Alphanetworks||wrgnd14_wd_storage|
|My Net N900 Central 2TB||Alphanetworks||wrgnd14_wd_storage|
This gives you user level access to your router as root user. It is useful as provides you with full access to all commands and files in your router, however it is highly risky if you do not know what you are doing. If you do not know what root access means and the risk it may bring for your device, you should probably stay away from it. To achieve root access you need to perform the following steps:
Western Digital has a recovery procedure in their website, however I do not know how effective it is and if it will work in a bricked device as it seems too dependent on the system working fairly ok. They advise to use this procedure when My Net Dashboard(web interface) is unable to be accessed which from my point of view does not imply the router is bricked. The procedure can be found in: http://wdc.custhelp.com/app/answers/detail/a_id/9618/~/how-to-recover-a-my-net-router-from-a-failed-firmware-update This is a summary of the procedure:
Given that support for the ubicom32 architecture has been removed from OpenWrt for being unmaintainable, it is unlikely that we will ever see OpenWrt for this router. But it may still be possible to improve it by tweaking.
There are three issues with this router: it does reset every once in a while, the NAS performance is mediocre at best and terribly in certain situations, and it also throws errors during demanding operations such as running Google Picasa on the network share.
Investigating the system gives some hints as to why that may be. The hard drive is connected via USB, and formatted as NTFS. The file server is a heavily customised version of samba called KC_SMB. And the system is running a number of crawler processes that all seem to scanning for images and generating thumb nails: miocrawler, mediacrawler, and dms_smm. None of this is ideal.
So what can be done about it? The crawler processes can be stopped, but that requires turning off the DLNA function. The first two can be disabled from the command line, too. Without the crawlers, the system seems much more stable and more responsive. Formatting the hard drive as ext3 seems like another interesting option, but it may also require changing the mount logic.