After narrowing down the replacement router that I wanted to either a Netgear WNDR 4500 or an Asus RT-N66U, I bought an RT-N66R from Best Buy last Saturday. It really wasn"t until I got it home that I noticed it wasn"t a "U". Since I couldn"t find a reference to that model on the Asus website, I called Asus tech spt/product information and was told by an Asus rep (who didn"t hesitate in his answer) that the only difference between the "R" and the "U" models is that the "R" is sold by retailers such as Best Buy. That sounded great. However, the firmware version that the R came with is 3.0.0.4.176, and doing an update check with the router"s web administration GUI states that "The router"s current firmware is the latest version." Yet, we know that the latest U firmware is version 3.0.0.4.220. When I went to the Asus download website today, I found that both the R and U were listed. For the RT-N66R, no firmware updates are listed as available, and the utility software is shown as: ASUS RT-N66R Utility version 4.2.6.4, The first version of utility for ASUS RT-N66R. (For the RT-N66U (VER.B1), the utility software is ASUS RT-N66U B1 Utility version 4.2.3.9, The first version of utility for ASUS RT-N66U B1.)Issues that I"ve found so far with the R are:1. The HTTPS SSL admin web page freezes.2. The Save Setting selection goes and HTTP 404 Not Found page for http://192.168.1.1/Settings_RT-N66R.CFGSince it"s evident that I need to upgrade the firmware to fix these issues, I might as well try the Merlin ASUS RT-N66U 3.0.0.4.220.18b while I"ve still got store return privileges. I"ll let you know the results.If it"s fully compatible, I think that the R should maybe be rolled up into the U subforum. I suspect the R could outrun the U in sales from big box stores.

You are watching: Rt-n66u vs rt-n66r


*

I have a feeling they are the exact same hardware, but it"s indeed a marketing difference (either in bundling or packaging). In fact that model does not even exist in the firmware source code, so I suspect it"s the exact same firmware.Could you do me a favor and post the output from the "dmesg" command (run it over telnet)? That will allow me to at least see if most of the hardware is the same.Normally I would suggest trying to flash my firmware just to see what happens (those routers are near impossible to brick), however the lack of an official RT-N66R firmware to flash it back in case of trouble could be a problem.EDIT: If we"re lucky, Asus might have also taken the occasion to fix the CFE to properly handle 64K NVRAM, which would open the door to full DD-WRT support. But that would require someone with such a router and a serial cable to validate whether Asus did change the CFE or not.
Asuswrt-Merlin: Customized firmware for Asus routersGithub: github.com/RMerl - Twitter: RMerlinDev - Libera: #asuswrtSee the sticky post for more info.
Attachments
S
shantanugoelOccasional Visitor
That is most certainly N66U firmware. It says so right at the beginning of the dmesg log. I also compared it against my N66U log and they are same..
*

The RT-N66U needs more nvram because it"s a true dual band router, and it also has USB ports, DownloadMaster, optware, etc... All those features require additional space to store both settings and temporary values.A brand new RT-N66U with only a basic configuration would have less than 3 KB of free nvram with its original 32 KB nvram.
Asuswrt-Merlin: Customized firmware for Asus routersGithub:
github.com/RMerl - Twitter: RMerlinDev - Libera: #asuswrtSee the sticky post for more info.
*

Interesting - I just noticed that the firmware has AiCloud enabled, while being based on a much older version (176). AiCloud was only officially launched with build 220, and went through a lot of code changes between these two versions.
Asuswrt-Merlin: Customized firmware for Asus routersGithub:
github.com/RMerl - Twitter: RMerlinDev - Libera: #asuswrtSee the sticky post for more info.
Hello, new here. Thought I would chime in on this since I just got my shiny new Black Knight in the mail from Amazon today. Pretty much same thing as the OP, but didn"t get from a BB (obviously). Grepped the dmesg output for nvram and it"s showing the updated 64k as well as AiCloud even though I have the .176 FW.Box said U, web interface shows U, and even the hostname is RT-N66U.
M
Mick MickleRegular Contributor
RMerlin said:
The RT-N66U needs more nvram because it"s a true dual band router, and it also has USB ports, DownloadMaster, optware, etc... All those features require additional space to store both settings and temporary values.A brand new RT-N66U with only a basic configuration would have less than 3 KB of free nvram with its original 32 KB nvram.

See more: Convert G To Pg Converter, Chart, Convert Gram To Pg


Interesting - I just noticed that the firmware has AiCloud enabled, while being based on a much older version (176). AiCloud was only officially launched with build 220, and went through a lot of code changes between these two versions.
Yes, the AiCloud tab has the Google Play logo link, but AiCloud isn"t working right. I suppose it"s been fixed for build 220? I"ve been able to set up the AiDisk USB HDD and access the media server, network share, FTP server, and Download Manager. But the Cloud Disk can"t be connected through either the Google app or the URL with a browser. (The Google app recognizes the existence of the router"s AiCloud, because it starts with the nickname prefilled with the host name, and that changes if I change the DDNS service. And for IE connection, Windows Network Diagnostics says that the remote device or resource won"t accept the connection.)The AiCloud hard-coded 443 port conflicts with the standard SSL port that many users will want forwarded to a server, so I had to remove that port forward for WHS 2011 to test. I think that routers should be able to have any of their administrative ports changeable -- and that includes added functions like FTP server and AiCloud -- so that the router can be transparent to applications and roles that one wants to assign to connected computers. The only port I can find that"s selectable is the HTTPS LAN port for the web GUI. I reckon I"ve been spoiled by DD-WRT.I noticed that the FTP security (for Share with Account) seems weak: FTP access on the LAN goes directly to a log-on screen, but Internet FTP access through DDNS doesn"t trigger a log-on screen until you drill down into the folders. (Although the folders appeared to be empty in the latter case, it"s not a warm and fuzzy feeling that anyone is allowed to be connected and see the folder structure.)