What's new

ASUS RT-N56U beta firmware

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Hey,
it´s seems, that i got also these dropbs in the wlan

C:\Users\Hexo>ping 192.168.178.7 -n 20

Ping wird ausgeführt für 192.168.178.7 mit 32 Bytes Daten:
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.178.7: Bytes=32 Zeit<1ms TTL=64


C:\Users\Hexo>ping www.google.com -n 20

Ping wird ausgeführt für www.google.com [173.194.35.145] mit 32 Bytes Daten:
Antwort von 173.194.35.145: Bytes=32 Zeit=139ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=127ms TTL=57

Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57

Ping-Statistik für 173.194.35.145:
Pakete: Gesendet = 20, Empfangen = 20, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 50ms, Maximum = 139ms, Mittelwert = 58ms

C:\Users\Hexo>ping www.google.com -n 40

Ping wird ausgeführt für www.google.com [173.194.35.145] mit 32 Bytes Daten:
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=183ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=53ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=52ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=56ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=51ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=50ms TTL=57
Antwort von 173.194.35.145: Bytes=32 Zeit=53ms TTL=57

Ping-Statistik für 173.194.35.145:
Pakete: Gesendet = 40, Empfangen = 40, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 50ms, Maximum = 183ms, Mittelwert = 54ms

The first ping was to my NAS System. Normaly i got a ping about <1 and since this fw i got some higher pings.
Also if i ping other server, you can see some very high ping.
I was using the latest beta without any problems.
After i made the update to the final version, i realise these drops.
I think the wlan isn´t running as good as it was as i use the beta.
I tried a hard rest but i still got the lags.

Can i switch without any problem back to the beta?
Edit: Some got a link to the beta? The links in the first post of this topic are dead

Greetz
 
Last edited:
Hey,
it´s seems, that i got also these dropbs in the wlan



The first ping was to my NAS System. Normaly i got a ping about <1 and since this fw i got some higher pings.
Also if i ping other server, you can see some very high ping.
I was using the latest beta without any problems.
After i made the update to the final version, i realise these drops.
I think the wlan isn´t running as good as it was as i use the beta.
I tried a hard rest but i still got the lags.

Can i switch without any problem back to the beta?
Edit: Some got a link to the beta? The links in the first post of this topic are dead

Greetz

here it is 253 beta.

http://d-h.st/VcB
 
Hi all.

Using the 3.0.0.4.260 firmware and it is incredible! It has all the features that the "homebrew" versions did...but all the features I need (VPN, WoL, miniDLNA) all actually work with my equipment (PS3)!

Thank you!

Quick question though, typically in the miniDLNA "Media Server" controls there is an option to set how miniDLNA should scan the database. The options typically let you set how often (in seconds) it monitors files on your attached disk or manual options for scanning or rebuilding the entire database.

The ver. 1.0.0.20 of the media server's control panel page seems to me missing the option to set a duration.

I added files and they didn't show up even after about 10 mins. I typically had it set to 90 seconds!

I had to rescan my entire database (by turning the media server "off" and then "on" to get newly added files to show up.

Is this option somewhere and I'm missing it... or will it be added later?

Thanks again for a truly great firmware for this amazing router!
 
I recently installed v. 3.0.0.4.260 but it hasn't been a good experience so far.
The new interface hangs any time I try navigating to a different section other than the initial screen.
It also hangs when trying to even log into the admin interface.
Has anyone else experienced this? And if so, how did you resolve it?

Thank you for any help you can provide.
 
I recently installed v. 3.0.0.4.260 but it hasn't been a good experience so far.
The new interface hangs any time I try navigating to a different section other than the initial screen.
It also hangs when trying to even log into the admin interface.
Has anyone else experienced this? And if so, how did you resolve it?

Thank you for any help you can provide.

Mine did this...press and hold the reset button on the router, once the router has restarted it should all work perfectly...atleast mine has, loving the firmware so far even better now the interface isnt buggy after the reset.
 
Mine did this...press and hold the reset button on the router, once the router has restarted it should all work perfectly...atleast mine has, loving the firmware so far even better now the interface isnt buggy after the reset.

Phew, thank you! That worked a treat!
 
I recently installed v. 3.0.0.4.260 but it hasn't been a good experience so far.
The new interface hangs any time I try navigating to a different section other than the initial screen.
It also hangs when trying to even log into the admin interface.
Has anyone else experienced this? And if so, how did you resolve it?

Thank you for any help you can provide.

Well after having a super stable Padavan 1.1.2.1-004 for months, it started cutting on the WAN intermittently on this setup: ISP Modem (Transparent Bridge (DHCP auto off but NAT on) --> RT-N56U PPPoE and DHCP. This setup has been flawless so have no idea why the WAN problem started, no new devices too. After days restoring different firmwares, starting the settings from scratch, restoring settings and using Padavan 3.0.3.0-026 for awhile, the issue exists. Haven't done anything to my setup. So I installed Official ASUS 3.0.0.4_260 and it seems to hold on well. Some random wifi chokes but not disconnects. Though I have the tendency to return to latest Padavan and see what the hell, lol. Also, how does IPv6 work? Is it just filling in the 6RD data as instructed by the ISP help pages and not deal with anything under WAN? Thanks.
 
Removed latest 260 firmware

I was getting disconnects on the VPN using the final 260 build. Also pings were erratic or receiving timeouts when pinging google.com -n 40.

This also showed up while playing Call of Duty BlackOps 2 where the game would lag or freeze.

I installed 1.0.1.8n instead of going back to black beta versions. I am no longer getting VPN disconnects and seemingly better internet and gaming performance than previous betas.
 
Looking to refer back to Beta Version 3.0.0.4_206

I have major wifi issues with the latest firmware (260)

I am looking to revert back to 206 but the links in the OP are dead.


Anyone can upload the Beta Version 3.0.0.4_206 to the forum and/or provide a working link?

Thanks so much!

Mickey
 
I have major wifi issues with the latest firmware (260)

I am looking to revert back to 206 but the links in the OP are dead.


Anyone can upload the Beta Version 3.0.0.4_206 to the forum and/or provide a working link?

Thanks so much!

Mickey

You are lucky I kept a back up of this :), this has been the most stable firmware for me. I kept it in case I need it in the future, but so far I have been using padavan's firmware and my router doesn't slow down at all, its amazing fast. but I rather have stock firmware :( I feel safer using it.

https://www.dropbox.com/s/gb858i7r6kmd4nn/RT-N56U_3.0.0.4_206.trx
 
You are lucky I kept a back up of this :), this has been the most stable firmware for me. I kept it in case I need it in the future, but so far I have been using padavan's firmware and my router doesn't slow down at all, its amazing fast. but I rather have stock firmware :( I feel safer using it.

https://www.dropbox.com/s/gb858i7r6kmd4nn/RT-N56U_3.0.0.4_206.trx

Thanks so much! You saved me. I am also using padavan's firmware but it has no QOS. I have VOIP so will see hoe pavadan is working...

Thanks again!
 
Im also having major problems with some wifi devices when running the 260 firmware. I get random wifi disconnects(2.4 GHz/WPA2/AES) on two devices, HTC Flyer and an ASUS laptop(Intel WiFi Link 1000 network card - 15.2 drivers).
Tried different wifi settings, factory resetting a couple of times, reflashed .260 etc. Also after about 4 days of uptime most wifi devices suffer from packetloss, for ex. I cant stream a movie from the wired network to the wireless network without packetloss. Going back to the .206 firmware solved all my issues.
 
3.0.0.4.260 wasn't stable for me at all with Wi-Fi. Devices get disconnected or connection dies even though it seems connected. This was also happening with 1.0.1.8n firmware.

Log is being flooded with the following messages when Wi-Fi problems occur:

Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=250!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=251!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=252!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=253!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=254!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=255!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=256!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=257!
Sep 29 22:46:22 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=258!

I'm not sure whats happening but this issue was posted on ASUS forums (sadly without a solution):

http://vip.asus.com/forum/view.aspx...759&board_id=11&model=RT-N56U&page=1&count=22

However the 3.0.0.4.206 beta works perfectly with no Wi-Fi issues and no MgmtRing space warnings in the log. Been up and running for 10 days now without any problems.

Got 2 iPads, 2 iPhones, 1 Android phone, 1 notebook on the 2.4GHz Wi-Fi network. No serious network activity though, max active is 3 at the same time.
 
problems with .260

I was having the same problems with .260 and i contacted Jeremy. He recommended reapplying the firmware and configuration. I did that and it seems to have solved my problem. I originally did the upgrade for the beta by checking for the updates in the gui. This time i uploaded the files to the router after downloading it myself from the asus site.

may be worth a try if you are having trouble with yours.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top