SmallNetBuilder Forums
Go Back   SmallNetBuilder Forums > Wireless Networking > ASUS Wireless > ASUS N Routers & Adapters

Reply
 
Thread Tools Search this Thread Display Modes
  #11  
Old 10-06-2012, 06:30 AM
Mick Mickle Mick Mickle is offline
Member
 
Join Date: Sep 2012
Posts: 47
Thanks: 17
Thanked 3 Times in 3 Posts
Mick Mickle is just starting out
Default

Overall, Build 220 (and also the Merlin build) is a definite improvement for the RT-N66R. Build 220 fixes these problems that I found in build 176 which was on the router out of the box:

1. The Save Setting selection no longer goes to an HTTP 404 Not Found page.

2. AiCloud works great and does a good job of streaming video to Android from LAN shares. (Be sure your phone or tablet has good security because the AiCloud app caches the username and password for immediate connection. So anyone who has access to your lost phone can be in your LAN.)

3. FTP access is more secure by starting with a log-on screen before showing the file structure.

However, I have these issues, although they may also exist in the "U" version (or maybe it's just my router or cockpit error):

1. Download Master goes to a blank page at port 8081.

2. HTTPS access to the web GUI works on the LAN IP address and from Android, but IE9 results in res://ieframe.dll/invalidcert.htm?SSLError=50331648 when using a DDNS address after clicking continue on the problem-with-security-certificate screen.

3. After logging on to FTP and clicking on the root folder, IE cannot display the webpage.

If these issues aren't unique to the "R" model, then indeed "R" = "U".
Reply With Quote
  #12  
Old 10-06-2012, 07:52 AM
Pierino Pierino is online now
Very Senior Member
 
Join Date: Jul 2012
Location: Ohio
Posts: 369
Thanks: 56
Thanked 42 Times in 32 Posts
Pierino is just starting out
Default

If the 66r does use the 66u firmware, would it be possible to flash it to a firmware version that does not have the 64k nvram fixed in the kernel, then telnet and run the nvram show command to see if it still is 64k?
That way it wouldn't need to be opened up? Or am I off base?
__________________
Rt-ac68u on Asuswrt-Merlin fw
Reply With Quote
  #13  
Old 10-06-2012, 01:22 PM
RMerlin's Avatar
RMerlin RMerlin is offline
Very Senior Member
 
Join Date: Apr 2012
Location: Canada
Posts: 10,010
Thanks: 54
Thanked 5,516 Times in 2,268 Posts
RMerlin is just starting out
Default

Quote:
Originally Posted by Mick Mickle View Post
2. HTTPS access to the web GUI works on the LAN IP address and from Android, but IE9 results in res://ieframe.dll/invalidcert.htm?SSLError=50331648 when using a DDNS address after clicking continue on the problem-with-security-certificate screen.
Accessing the router using the DDNS from inside your network can cause the router to crash and reboot itself if you are running Asus's firmware. I have fixed that issue in my builds (it's related to the GRO setting). Asus are aware of the issue and will have a solution in a future firmware update.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers
Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
Reply With Quote
  #14  
Old 10-06-2012, 02:34 PM
TonyH TonyH is offline
Very Senior Member
 
Join Date: Feb 2012
Location: Calgary AB Canada
Posts: 716
Thanks: 5
Thanked 49 Times in 46 Posts
TonyH is just starting out
Send a message via Skype™ to TonyH
Default

R often stands for Refurbished.bished. So My guess is it is RT-66N refurgished.
Reply With Quote
  #15  
Old 10-06-2012, 02:56 PM
RMerlin's Avatar
RMerlin RMerlin is offline
Very Senior Member
 
Join Date: Apr 2012
Location: Canada
Posts: 10,010
Thanks: 54
Thanked 5,516 Times in 2,268 Posts
RMerlin is just starting out
Default

Quote:
Originally Posted by TonyH View Post
R often stands for Refurbished.bished. So My guess is it is RT-66N refurgished.
No, Asus already confirmed it was a SKU aimed at large retailers like Best Buy. It's definitely brand new.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers
Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
Reply With Quote
  #16  
Old 10-07-2012, 03:38 AM
Mick Mickle Mick Mickle is offline
Member
 
Join Date: Sep 2012
Posts: 47
Thanks: 17
Thanked 3 Times in 3 Posts
Mick Mickle is just starting out
Default

Quote:
Originally Posted by RMerlin View Post
Accessing the router using the DDNS from inside your network can cause the router to crash and reboot itself if you are running Asus's firmware. I have fixed that issue in my builds (it's related to the GRO setting). Asus are aware of the issue and will have a solution in a future firmware update.
I'm sorry to say that IE9 chokes in HTTPS access using DDNS within the LAN even with your 220.18 build. While I can get past the log-in window to see the GUI, the screen freezes either right away or after a few clicks. Although the router doesn't crash, that HTTPS access isn't reliable on my system. However, Google Chrome does successfully access the GUI under the same HTTPS scenario. In fact, it's very speedy operation of the GUI. Plain HTTP access using DDNS inside the network does work okay with IE9.
Reply With Quote
  #17  
Old 10-08-2012, 05:42 AM
Pierino Pierino is online now
Very Senior Member
 
Join Date: Jul 2012
Location: Ohio
Posts: 369
Thanks: 56
Thanked 42 Times in 32 Posts
Pierino is just starting out
Default

Quote:
Originally Posted by Pierino View Post
If the 66r does use the 66u firmware, would it be possible to flash it to a firmware version that does not have the 64k nvram fixed in the kernel, then telnet and run the nvram show command to see if it still is 64k?
That way it wouldn't need to be opened up? Or am I off base?
I guess not.
__________________
Rt-ac68u on Asuswrt-Merlin fw
Reply With Quote
  #18  
Old 10-09-2012, 06:18 PM
Mick Mickle Mick Mickle is offline
Member
 
Join Date: Sep 2012
Posts: 47
Thanks: 17
Thanked 3 Times in 3 Posts
Mick Mickle is just starting out
Default

Quote:
Originally Posted by RMerlin View Post
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.

Is what I provided below relevant to the CFE issue?

Quote:
Originally Posted by Pierino View Post
If the 66r does use the 66u firmware, would it be possible to flash it to a firmware version

that does not have the 64k nvram fixed in the kernel, then telnet and run the nvram show command to see if it still

is 64k?
That way it wouldn't need to be opened up? Or am I off base?
OK, I checked it out, since I had the confidence from already easily upgrading the firmware (see below) and having store return privileges. I put the RT-N66R back to an earlier firmware and got the readings by Telnet. I also discovered some significant problems that may be applicable to other than the "R" model.

UPDATE: I think I resolved the issues below. Please see the post at http://forums.smallnetbuilder.com/sh...7&postcount=25 for an explanation. In retrospect, any difficulties that I experienced were not show stoppers (more likely user errors) and shouldn't overshadow the impressive performance of this router.

Flashing and Backup Issues. Upfront, these are remaining issues for me, listed by importance (see Problems Experienced below):

a. Reliability of settings configuration file is questionable. (I don't like to think of having to manually re-enter all of the settings that make my network flow correctly.)

b. Reliability of Firmware Restoration utility operation is questionable. (Assuming the router is bullet proof -- here's hoping -- other flashing methods might work.)

c. Duplicate web GUI login-blocking enigma ("You cannot Login unless logout another user first") complicates and frustrates resolution of problems. (When router is fully functioning, I've been able to log in simultaneously from different computers, both HTTP and HTTPS -- maybe that's just the Merlin build? -- and I haven't had that problem with Linksys or DD-WRT GUIs. Duplicate login restrictions should be removed. Remote access might be needed but wouldn't be available if the web GUI was left open on the LAN.)

NVRAM Size. Here's the result of flashing the RT-N66R to the pre-64KB NVRAM firmware 3.0.0.3.178. If I correctly understand how to read the outputs of dmesg and "nvram show," I think it went back to 32KB like one would expect if it's just a clone of the "U" model, different in branding only. I've attached the Telnet logs for the output of both dmesg and "nvram show" (excerpt because of attachment size limit here) if anyone wants to glean further information or if I didn't provide the right summary:

dmesg --
dev_nvram_init: _nvram_init
_nvram_init: allocat header: 2280980480, size= 32768

nvram show --
size: 29689 bytes (3079 left)

Pre-64KB Firmware. I started with the out-of-the-box firmware of 4.176 (which is already 64KB NVRAM) and several days ago upgraded to Asus 4.220 then Merlin 4.220.18, all smoothly without a hitch. So, I thought it would be a piece of cake to go back to 3.178, and it was. While at the 3.178 firmware and having read a number of threads here on clearing NVRAM, resetting, and upgrading these Asus routers, I decided to try some of the methods: Holding the reset button, using "mtd-erase -d nvram" both with Telnet and at http://192.168.1.1/Main_AdmStatus_Content.asp, and even putting router into "rescue mode" and using Firmware Restoration utility to reload 3.178 (failed - see below). (I didn't try the method of holding the WPS button while powering the router back on to clear NVRAM, which I assume will work http://forums.smallnetbuilder.com/sh...7&postcount=19.) Of course, Telnet had to be re-enabled for any Telnet access after successful resets. At various times I was greeted with the "You cannot Login unless logout another user first" webpage while trying to access the web GUI. Generally, http://192.168.1.1/Main_AdmStatus_Content.asp was always available as long as the power LED wasn't blinking. And there were several times when the configuration did survive the "mtd-erase -d nvram." I ended these experiments with the router in a seemingly stable 3.178 state with minimum configuration.

Problems Experienced. Getting back to the 4.220.18 build and restoring my configuration settings was a saga lasting hours. (I didn't keep track of the times I reset the router and flashed the firmware.) Each time I restored the settings with the backup file, I could see that only the 2.4GHz SSID had been restored, but the 5GHZ SSID was still "ASUS_5" and I couldn't log in to the web GUI with my username and password after I closed the browser window. I also couldn't access the Administration page to enable Telnet. Apparently the .cfg settings file that I had backed up to was corrupted. Frustratingly, I was continually met with "You cannot Login unless logout another user first." I often ended Internet Explorer between NVRAM clearings and firmware flashing, including ending the iexplorer processes in Task Manager to hopefully eliminate any caching that may have been contributing to these problems. But I was always able to get to http://192.168.1.1/Main_AdmStatus_Content.asp. That webpage also presented a login window that, curiously, would accept my username and password when the main web GUI page would not. I tried the Firmware Recovery utility at least five times and found that if I tried to upload the firmware and was unsuccessful, I would later only get the response of "not in rescue mode" unless I exited and restarted the program. When the program did start to upload the firmware, the power LED stopped its slow blinking, which indicated it was in the rescue mode, and I had these errors (never successfully completing the recovery process): Either the program aborted the upload part way through, resulting in the status that the router is not in rescue mode, or after completing the upload and after a fairly lengthy recovery process, I received a warning that the recovery was unsuccessful.

Resolution. To finally restore workability, I cleared NVRAM via the Main_AdmStatus_Content webpage referenced above. I then closed all IE processes, restarted the browser, and accessed 192.168.1.1 after waiting out the "You cannot Login unless logout another user first" error (it seemed to go away on it's own after 5-10 minutes, but I was never really sure of what was going on there -- apparent restricted simultaneous logins seem to persist beyond complete router resets), sprinted through the Quick Setup, did the firmware upgrade again to be sure there wasn't any corrupted code in the router (maybe that wasn't necessary), and re-entered all of my "production" configuration information. (Fortunately, with this being a brand new router, I haven't gotten around to entering all the MAC address filters, static IP addresses, and port forwards that I normally use.) I saved the settings into a backup file that has the same size (36,872 bytes) as the one that wouldn't restore correctly, so I still don't know if it's any good or how to test it -- not the best comfort level.

Last edited by Mick Mickle; 10-11-2012 at 05:59 AM. Reason: Ref CFE
Reply With Quote
  #19  
Old 10-09-2012, 06:45 PM
RMerlin's Avatar
RMerlin RMerlin is offline
Very Senior Member
 
Join Date: Apr 2012
Location: Canada
Posts: 10,010
Thanks: 54
Thanked 5,516 Times in 2,268 Posts
RMerlin is just starting out
Default

Flashing an older firmware won't help you determine if the CFE addresses 32 KB or 64 KB. The RT-AC66U requires the NVRAM_64K switch to be enabled when the firmware is compiled. The only way to truly determine if the CFE can access the whole 64 KB is through a serial cable.

Restoring settings meant for a different nvram size is not supported. You HAVE to clear your settings and manually reconfigure when switching nvram size, otherwise you will run into issues.

The multiple login issue usually occurs if you log from one IP, change your PC's IP without logging out - the router will still think you are logged in on the first IP.
__________________
Asuswrt-Merlin: Customized firmware for Asus routers
Github: github.com/RMerl - Twitter: RMerlinDev
See the sticky post for more info.
Reply With Quote
  #20  
Old 10-09-2012, 07:44 PM
Mick Mickle Mick Mickle is offline
Member
 
Join Date: Sep 2012
Posts: 47
Thanks: 17
Thanked 3 Times in 3 Posts
Mick Mickle is just starting out
Default

To be clear, I followed cautions about using settings from mismatched firmware. I never tried to restore any settings to the earlier 32KB firmware. I tried to restore the backup from the 220.18 back to the 220.18 after flashing back to that current version. That's when I had the problems. Shouldn't the 220.18 have set the NVRAM back up to 64KB after experimentation with 32KB firmware and accepted the settings without error? Now that I have it working right but with minimum custom configuration settings, I guess I'd better bite the bullet and clear brNVRAM and test the settings restore so I can rely on the backup and restore function.

Why do you suppose there's still a multiple login problem when only one computer is being used after the router's memory is erased and the browser is restarted? That's the issue I had.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


All times are GMT -4. The time now is 05:50 AM.


Top 10 Stats
Top Posters* Top Thanked
RMerlin  491
azazel1024  153
stevech  133
KGB7  129
sinshiva  113
hggomes  92
Kel-L  88
microchip  86
sm00thpapa  83
fistv  81
RMerlin  5515
stevech  322
ryzhov_al  264
TeHashX  214
L&LD  188
RogerSC  187
sinshiva  140
joegreat  123
jlake  122
sfx2000  118
Most Viewed Threads* Hottest Threads*
Old Asuswrt-Merli...  73756
Old Asuswrt-Merli...  58540
Old Asuswrt-Merli...  21586
Old Asus locking...  8975
Old [Fork]...  7679
Old ASUS...  6741
Old Incoming...  5912
Old Asus...  5224
Old Share What...  2948
Old Download...  2838
Old Asuswrt-Merli...  392
Old Asuswrt-Merli...  389
Old Asuswrt-Merli...  130
Old Asus locking...  125
Old [Fork]...  84
Old Asus...  52
Old ASUS...  48
Old Inherited PC...  45
Old 376.44 -...  40
Old What's...  39


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
© 2006-2014 Pudai LLC All Rights Reserved.