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!

Quick update, it works perfectly, thank you so much for this f/w its a real shame the standard f/w has the android/wifi issue, i'm not entirely sure what you have tweaked in this but its worked ! Instant updates on wifi :).
 
New Asus Firmware

07.11.2012
* Black UI

http://www.asus.ru/ftp/NW_TO_TEST/RT-N56U_3.0.0.4_260.trx

I havent test it yet so if anyone will test this please let us know about it...

Not beta firmware, but official 3.0 firmware for the RT-N56u is available on our support site.

FW version 3.0.0.4.260
http://support.asus.com/Download.as...FW_RT_N56U_3004260.zip#FW_RT_N56U_3004260.zip


Im using the one in the first quote, I can't turn the 5ghz radio off though :/, infact can't turn off any radio at all.

Also do you know if there is a web ui user login timeout, I accidently left the 192.168.1.1 address open on my PC upstairs and it stayed logged in until I closed the window, couldn't login to the UI on any other PC until i had closed the window off upstairs.
 
Last edited:
I think transfer speeds over wired have dropped compared to stock f/w, It could just be me or another factor though. I don't see why they would of dropped, the physical hardware is the same.

Yes definitely dropped, used to hit 65mb/s and stick there, now its more like 45mb/s
 
Last edited:
I think transfer speeds over wired have dropped compared to stock f/w, It could just be me or another factor though. I don't see why they would of dropped, the physical hardware is the same.

Yes definitely dropped, used to hit 65mb/s and stick there, now its more like 45mb/s

my speeds are same all the time @ fttb 100/100 Mb/s, in windows task manager about 99/99 Mb/s
2297024490.png
 
Not beta firmware, but official 3.0 firmware for the RT-N56u is available on our support site.

FW version 3.0.0.4.260
http://support.asus.com/Download.as...FW_RT_N56U_3004260.zip#FW_RT_N56U_3004260.zip

Seems like the IPv6 is working now with this firmware. Although I didn't keep it in use very long, just wanted to upgrade the firmware and see if IPv6 would work. So not going to have weeks of testing unless my rt-n66u goes up in smoke *smile*. Or someone borrows it.
 
NUTS! You STILL can't just install the "Media Server" and access the configuration pages without having to install the "Download Master" first.
:mad::mad::mad:

That's odd that you have to do that....I don't use download master at all and have media server installed by itself....
 
I am not sure why, but it's always been the case with my router. I install "Media Server", then I go to it's configuration page and it's not there (I don't like sharing my entire drive, just one directory).

Uninstall "Media Server", then install "Download Master", then install "Media Server" (again), then I can go to the configuration page of "Media Server".

I ran some quick tests, and the transfer rate to a NTFS formatted USB drive is slow.

Also, for some reason after an hour or so, my internet download speed was cut in half. Reboot, it's back to normal. Hour or so later, back to half speed.

I went back to Pavadan's Custom firmware for now.
 
problems on new GA 3.0 firmware

Mostly good. Some problems already:
1. Logged in from client "a" (wireless). Now, I can no longer log in elsewhere -- neither "logout" nor even sleeping client "a" helps.
2. Router hung completely - had to reboot. Not sure why, yet, though I suspect it's related to having USB storage servers set up.

Questions:
1. Will the guest networks ever work? The (hidden) page is still there, but the access to the tables is still wrong, so it's pretty much unusable.
2. Will there be a WOL tab? This is really crucial for me when using VPN.
 
Mostly good. Some problems already:
1. Logged in from client "a" (wireless). Now, I can no longer log in elsewhere -- neither "logout" nor even sleeping client "a" helps.
2. Router hung completely - had to reboot. Not sure why, yet, though I suspect it's related to having USB storage servers set up.

Questions:
1. Will the guest networks ever work? The (hidden) page is still there, but the access to the tables is still wrong, so it's pretty much unusable.
2. Will there be a WOL tab? This is really crucial for me when using VPN.

There's no WOL tab in Asuswrt itself. Asus' WOL functionality is provided by AiCloud, which isn't available (yet?) on the RT-N56U.

One manual workaround is to telnet into your router, and run the ether-wake command through the command line.
 
Issues with firmware 3.0.0.260

Having been using it since the date it was released. Parent Controls doesn't work properly on Saturday and Sunday. Also I have been switching back and forth to Google version 3.0.2.6-018. Not sure if only to mine, the wifi with 0.260 has the following issues:
1. hard to get connected, taking loger time or multiple tries
2. tend to drop a connection, but get reconnected afterwards
3. erratic and fluctuating throughput

Tried with static channel and so do on to no avail. Switching back to 6-18, it works perfectly.
 
Having been using it since the date it was released. Parent Controls doesn't work properly on Saturday and Sunday. Also I have been switching back and forth to Google version 3.0.2.6-018. Not sure if only to mine, the wifi with 0.260 has the following issues:
1. hard to get connected, taking loger time or multiple tries
2. tend to drop a connection, but get reconnected afterwards
3. erratic and fluctuating throughput

Tried with static channel and so do on to no avail. Switching back to 6-18, it works perfectly.


I don't have any Wi-Fi issues, Did you restart your router back to default after the upgrade? Connecting is fluent no issues. My only issue is the wireless log does not display the correct Mac address. Is this the same for you?

--
Chris
 
chris,
yes. did reset and multiple reboots. getting the same wifi issues with all my wifi devices, not sure if one affects the rest. Lan works fine. Just loaded google 3.0.3.0-025. yes it is definitely more resilient (consistent). It is sort of optimizing itself. Even my kid won't complain anymore.
 
Last edited:
3.0.0.4.260: ping spikes with WPA2

I'm getting ping spikes with the new firmware that makes gaming unbearable. After much trial and error, I figured that it's related to WPA2 implementation in the new firmware. Firmware 1.0.1.8l w/ WPA2+AES works well, but not 3.0.0.4.260 w/ WPA2+AES. However, if you switch to WPA+TKIP for 3.0.0.4.260, it works well again which sucks because WPA+TKIP limits you to 54 Mbits wifi.

Selective logs are below. I've confirmed this many times, with multiple tests. No problems when I revert back to the old firmware.
PS: I tried Padavan's firmware, but couldn't get wifi to work. =( Only my Nexus 7 detected the network out of 8 devices.

Version 1.0.1.8l w/ WPA2+AES
Pinging google.com [74.125.224.162] with 32 bytes
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=30ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=73ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=35ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=25ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=27ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=44ms TTL=
Reply from 74.125.224.162: bytes=32 time=33ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=25ms TTL=
Reply from 74.125.224.162: bytes=32 time=28ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=25ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=34ms TTL=
Reply from 74.125.224.162: bytes=32 time=25ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=
Reply from 74.125.224.162: bytes=32 time=26ms TTL=

Ping statistics for 74.125.224.162:
Packets: Sent = 30, Received = 30, Lost = 0 (0
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 73ms, Average = 29ms

Version 3.0.0.4.260 - w/ WPA2+AES
Pinging google.com [74.125.224.162] with 32 bytes of d
Reply from 74.125.224.162: bytes=32 time=27ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=28ms TTL=51
Reply from 74.125.224.162: bytes=32 time=27ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=111ms TTL=51
Reply from 74.125.224.162: bytes=32 time=28ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=27ms TTL=51
Reply from 74.125.224.162: bytes=32 time=27ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=1166ms TTL=51
Reply from 74.125.224.162: bytes=32 time=304ms TTL=51
Reply from 74.125.224.162: bytes=32 time=322ms TTL=51
Reply from 74.125.224.162: bytes=32 time=550ms TTL=51
Reply from 74.125.224.162: bytes=32 time=467ms TTL=51
Reply from 74.125.224.162: bytes=32 time=332ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=27ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=31ms TTL=51
Reply from 74.125.224.162: bytes=32 time=26ms TTL=51
Reply from 74.125.224.162: bytes=32 time=385ms TTL=51
Reply from 74.125.224.162: bytes=32 time=198ms TTL=51

Ping statistics for 74.125.224.162:
Packets: Sent = 30, Received = 30, Lost = 0 (0% lo
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 1166ms, Average = 146ms


Version 3.0.0.4.260 w/ WPA+TKIP
Pinging google.com [74.125.224.160] with 32 bytes of
Reply from 74.125.224.160: bytes=32 time=25ms TTL=51
Reply from 74.125.224.160: bytes=32 time=25ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=25ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=33ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=25ms TTL=51
Reply from 74.125.224.160: bytes=32 time=25ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=30ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=28ms TTL=51
Reply from 74.125.224.160: bytes=32 time=27ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=31ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51
Reply from 74.125.224.160: bytes=32 time=26ms TTL=51

Ping statistics for 74.125.224.160:
Packets: Sent = 30, Received = 30, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 33ms, Average = 26ms
 
Last edited:
I'm getting ping spikes with the new firmware that makes gaming unbearable. After much trial and error, I figured that it's related to WPA2 implementation in the new firmware. Firmware 1.0.1.8l w/ WPA2+AES works well, but not 3.0.0.4.260 w/ WPA2+AES. However, if you switch to WPA+TKIP for 3.0.0.4.260, it works well again which sucks because WPA+TKIP limits you to 54 Mbits wifi.

Selective logs are below. I've confirmed this many times, with multiple tests. No problems when I revert back to the old firmware.
PS: I tried Padavan's firmware, but couldn't get wifi to work. =( Only my Nexus 7 detected the network out of 8 devices.

I see your problem..

You're gaming on wifi :/.

All joking aside, I hope it gets sorted.
 
I'm running latest fw, with WPA2 AES, just tested my laptop, pinged google.com and had about 30ms ping overall average. So no wifi problems for me.

Have you done a proper reset like advised ? I had GUI issues, did the proper reset as I was supposed to do and the router has been perfect every since. So happy with my n56u now with this firmware on.
 
Last edited:
Have you done a proper reset like advised ? I had GUI issues, did the proper reset as I was supposed to do and the router has been perfect every since. So happy with my n56u now with this firmware on.

Even with a factory reset, I'm still able to replicate the issue. Also, I get ping spikes using WPA2 with firmware 1.0.1.8n. Again, firmware 1.0.1.8l has no issues.

Moreover, I found that other users are having ping issues with 1.0.1.8n and 3.0.0.4.260.
http://vip.asus.com/forum/view.aspx...rd_id=11&model=RT-N56U&page=1&SLanguage=en-us
http://vip.asus.com/forum/view.aspx...rd_id=11&model=RT-N56U&page=1&SLanguage=en-us
 
Last edited:

Similar 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