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
great news, thanks a lot, finallyNot beta firmware, but official 3.0 firmware for the RT-N56u is available on our support site.
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
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
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
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
NUTS! You STILL can't just install the "Media Server" and access the configuration pages without having to install the "Download Master" first.
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.
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.
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
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.
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.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!