ASUS RT-N56U beta firmware

[jhoffy22]

been running for 4 days, no hiccups at all

Okay, I'll give it a try.

 

[Slamb]

just installed latest stable version 3.0.0.4.342

 

[kayakj]

just installed latest stable version 3.0.0.4.342

Have you experienced any of the "kernel: idx(1), not enough space in MgmtRing, MgmtRingFullCount" errors in the logs/ wifi drop outs? ( I hope they finally fixed the issue)

 

[Slamb]

i did some cleaning after update and since then, there is no line in log...
wifi is ok, but i think, in v334 it was more stable (40/40 -> 50/15) on my phone...

 

[kayakj]

i did some cleaning after update and since then, there is no line in log...
wifi is ok, but i think, in v334 it was more stable (40/40 -> 50/15) on my phone...

So I tried the firmware (3.0.0.4.342).. and the kernel errors started appearing within the first 5 minutes and I also lost connection around that time. Guess I may just give up on the official firmware permanently

 

[baadnewz]

mediaserver / download master

i changed the hdd connected to the router and now i cant install mediaserver package and or download master, it says server not responding. any ideas an alternate download location or any recommendation for a optware mediaserver ?

i have the lastest firmware 3.0.0.4.342

 

[RogerSC]

Now trying out .342 *smile*, and have noticed that you can't get to the "System Log" tab using Chrome browser on Windows 8, have to use MS Internet Explorer 10, on Windows 8, anyways.

Anyone else notice that *smile*? I even tried to get there via the page's URL, no luck.

Other than that, seems functional to me. I'll use it for a while and see what happens.

 

[Rianata]

Installed .342 last night and today encountered the "kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!" again like in former firmware builds This causes a drop of connection to the internet. The lines with the dots were inserted while posting this because of the length of this reply. But overall it takes 1m2s before it seems to stop and the first log entry is when I add a manual assigned IP around the DHCP list at 23.48pm.

Feb 9 13:26:31 nmbd[2145]: Samba name server RT-N56U is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.1
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=452!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=453!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=454!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=455!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=456!
.............
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=700!
Feb 9 14:12:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=701!
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=702!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4095!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4096!
.............
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4559!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4560!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4561!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCoFullCount=4570!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4571!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4572!
.............
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4992!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4993!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4994!
Feb 9 23:48:00 rc_service: httpd 2127:notify_rc restart_net_and_phy

 

[BoscoWg]

Installed .342 last night and today encountered the "kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!" again like in former firmware builds This causes a drop of connection to the internet. The lines with the dots were inserted while posting this because of the length of this reply. But overall it takes 1m2s before it seems to stop and the first log entry is when I add a manual assigned IP around the DHCP list at 23.48pm.

Feb 9 13:26:31 nmbd[2145]: Samba name server RT-N56U is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.1
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=452!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=453!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=454!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=455!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=456!
.............
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=700!
Feb 9 14:12:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=701!
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=702!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4095!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4096!
.............
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4559!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4560!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4561!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCoFullCount=4570!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4571!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4572!
.............
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4992!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4993!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4994!
Feb 9 23:48:00 rc_service: httpd 2127:notify_rc restart_net_and_phy

You could use the restoration tool to flash again the newest firmware in the router's rescue mode.

 

[baadnewz]

you can always try:

http://192.168.1.1/Main_AdmStatus_Content.asp

type :

mtd-erase -d nvram

then

reboot

be aware, you settings will be lost

 

[YASUKAWA]

Flashed from 206 to 342 yesterday and so far I had no problems (been 18 hours). No slow downs or no drops or no "Qidx(0), not enough space in MgmtRing, MgmtRingFullCount" messages in log.

I had all kinds of weird problems with previous stable releases, but this one seems fine. I'll report back if anything happens.

 

[kayakj]

you can always try:

http://192.168.1.1/Main_AdmStatus_Content.asp

type :

mtd-erase -d nvram

then

reboot

be aware, you settings will be lost

I tried that when I initially installed 3.0.0.4.342 and still got the "Qidx(0), not enough space in MgmtRing, MgmtRingFullCount" Errors almost immediately

 

[RMerlin]

you can always try:

http://192.168.1.1/Main_AdmStatus_Content.asp

type :

mtd-erase -d nvram

then

reboot

be aware, you settings will be lost

Sometimes, the reboot command will write back the cached content of the nvram. It's best to boot the router with no USB disk plugged in (to avoid filesystem corruption), run the mtd-erase command, and then turn the router off and on rather than running the reboot command.

 

[RogerSC]

Flashed from 206 to 342 yesterday and so far I had no problems (been 18 hours). No slow downs or no drops or no "Qidx(0), not enough space in MgmtRing, MgmtRingFullCount" messages in log.

I had all kinds of weird problems with previous stable releases, but this one seems fine. I'll report back if anything happens.

Interesting, this is the first release where I've seen the MgmtRing messages in the router log, haven't seen them in previous Asus releases. Also, the "System Log" tab doesn't work on Chrome with .342, and I really don't like having to have IE up just so I can look at my router logs. I could put up with that, but the MgmtRing messages are the last straw.

I'm currently trying out the latest Padavan's firmware, but may go back to Asus .337 (Beta) since I'm having problems getting IPv6 working with Padavan's firmware. .337 worked well for me, but I didn't want to stay with it because it was a Beta.

 

[iamstillvince]

so far so good

i updated to the 342 and cross fingers, seem to be having no more issues. NAT open on xbox, streaming, server all seems to be good. No drops or anything, still a little issue with speed but i am not really sure its caused by router. getting upgrade to my internet next week so i will wait till after that.

 

[hiluke]

Interesting, this is the first release where I've seen the MgmtRing messages in the router log, haven't seen them in previous Asus releases. Also, the "System Log" tab doesn't work on Chrome with .342

System Log tab is working fine for me on .342 with Win XP, Win 7 and Win 8 (64bit) using chrome. (And I know because I am constantly checking for these MgmtRing issues when my network randomly stops working properly.

From a few of the comments above, I might try wiping and physically unplugging the router, before manually reconfiguring, to see if there's a buggy setting from one of the previous firmwares I have flashed. I don't have high hopes though. My MgmtRing count was up to 7000+ in under 12 hours yesterday.

 

[RogerSC]

System Log tab is working fine for me on .342 with Win XP, Win 7 and Win 8 (64bit) using chrome. (And I know because I am constantly checking for these MgmtRing issues when my network randomly stops working properly.

From a few of the comments above, I might try wiping and physically unplugging the router, before manually reconfiguring, to see if there's a buggy setting from one of the previous firmwares I have flashed. I don't have high hopes though. My MgmtRing count was up to 7000+ in under 12 hours yesterday.

I tried that, even flashed a couple of times, erased the nvram a couple of times, power-cycled it, tried the reset button, tried everything I could think of, recycled my browser after dumping the cache, rebooted my computer, and the "System Log" tab wouldn't work for me in Chrome. I did find it amazing, which is why I spent so much time trying to get it to work. And then I got the MgmtRing errors, and I decided that I'd spent enough time with that version of the firmware.

As a last resort, I just flashed .342 from "Recovery Mode", cleared the nvram, used the reset button, and power-cycled (belt and suspenders *smile*), and now the "System Log" tab is working with the Chrome browser. If I don't get the "MgmtRing" errors, then I'll be happy. IPv6 is also working fine.

 

[LHF]

I tried that, even flashed a couple of times, erased the nvram a couple of times, power-cycled it, tried the reset button, tried everything I could think of, recycled my browser after dumping the cache, rebooted my computer, and the "System Log" tab wouldn't work for me in Chrome. I did find it amazing, which is why I spent so much time trying to get it to work. And then I got the MgmtRing errors, and I decided that I'd spent enough time with that version of the firmware.

As a last resort, I just flashed .342 from "Recovery Mode", cleared the nvram, used the reset button, and power-cycled (belt and suspenders *smile*), and now the "System Log" tab is working with the Chrome browser. If I don't get the "MgmtRing" errors, then I'll be happy. IPv6 is also working fine.

Hi RogerSC !

Could you post here the telnet command line for clearing nvram ?

Thanks !

 

[taedan]

In the latest .342, when I click install media server, it proceeds up to 99% and just hangs. Tried deleting the asusware folder on the HDD as well as all other asus files on the disk but still hangs. Anyone get media server to install completely and work?

 

[RogerSC]

Hi RogerSC !

Could you post here the telnet command line for clearing nvram ?

Thanks !

Sure:

mtd-erase -d nvram

That's all there is to it. And you'll see the results when you reboot the router.