New Asus firmware version: 3.0.0.4.360

[mrjackson]

Looks like Asus released a new firmware version today:

http://usa.asus.com/Networks/Wireless_Routers/RTN56U/#download


ASUS RT-N56U Firmware Version 3.0.0.4.360
1. AiCloud
For iOS user, please upgrade app to 1.02.78 or above
(for more information, please refer to http://event.asus.com/2012/nw/aicloud/index.htm)
2. Network tools in Advanced setting
3. WOL user interface
4. H.323 and SIP passthrough can be disabled in Advanced Settings --> WAN -->NAT Passthrough
5. Click the device name and lookup the manufacturer information
6. Change the DHCP query frequency in Advanced settings-->WAN-->Internet connection to resolve the ISP compatibility issue.

Fix
1. Wireless time control related bugs.
2. Media server related issues when lan subnet change or USB hotplug
3. IPv6 over PPPoE interoperability issues.
4. PPPoE password setting error in Advanced wan setting.

Modify
1. Support Huawai E353 3G/4G USB dongle.
2. The router setting URL is changed to http://router.asus.com, use the original URL http://www.asusnetwork.net can also go to the setting page.

 

[RogerSC]

Curious about the MgmtRing messages with this one, since they're not explicitly mentioned in the list of fixes.

 

[BoscoWg]

Looks like Asus released a new firmware version today:

http://usa.asus.com/Networks/Wireless_Routers/RTN56U/#download


ASUS RT-N56U Firmware Version 3.0.0.4.360
1. AiCloud
For iOS user, please upgrade app to 1.02.78 or above
(for more information, please refer to http://event.asus.com/2012/nw/aicloud/index.htm)
2. Network tools in Advanced setting
3. WOL user interface
4. H.323 and SIP passthrough can be disabled in Advanced Settings --> WAN -->NAT Passthrough
5. Click the device name and lookup the manufacturer information
6. Change the DHCP query frequency in Advanced settings-->WAN-->Internet connection to resolve the ISP compatibility issue.

Fix
1. Wireless time control related bugs.
2. Media server related issues when lan subnet change or USB hotplug
3. IPv6 over PPPoE interoperability issues.
4. PPPoE password setting error in Advanced wan setting.

Modify
1. Support Huawai E353 3G/4G USB dongle.
2. The router setting URL is changed to http://router.asus.com, use the original URL http://www.asusnetwork.net can also go to the setting page.

I just flashed my router with this firmware. Everything seems so far so good at all, but there is always a constant problem with these recent firmwares. My xbox 360 always cannot to my 5Ghz wifi and says my password is wrong. However, it connects well to my 2.4Ghz wifi.

I wish they could implement those xbox fixes for rt-n56u just like what they have done with rt-n66u and rt-ac66u.

 

[BoscoWg]

I also found a spelling error in the log

Jan 1 08:00:13 kernel: The CPU feqenuce set to 500 MHz

frequency is spelled wrong

 

[RogerSC]

I also found a spelling error in the log

Jan 1 08:00:13 kernel: The CPU feqenuce set to 500 MHz

frequency is spelled wrong

Thanks, they've never been very good with spelling and grammar. Sounds like this new version is worth a try.

They have been adding in the features that they've added for the rt-n66u one by one, but this is a different chip set so it will apparently take longer for some things *smile*.

 

[jolu]

With the new firmware I lost internet connection every now and then. My connection speed was also inconsistent and did stay at 144mbps most of the time.
Now im back at the 342-firmware, no drops with the connection and the connection speed is between 240-300mbps again.

Have anyone else noticed this as well?

 

[RogerSC]

Also upgraded to .360, and didn't even see my 5GHz. network on my Roku, even though it was on and working. Even after rebooting the router, still no 5GHz. network in the living room. Went back to .342 and my 5GHz. network was again available on the Roku in my living room.

The 2.4GHz. network was fine for both firmware versions.

So I guess I'll stay with .342 for the moment.

 

[arul]

Anybody know why recent fw wont work with fixed dns server? I tried to use any dns server on the fw, it wont connect to dns at all, it will only work if i set it up to auto mode and use my isp dns instead.

 

[CL-Jeremy]

Hi All!

Please try checking your settings for the issues you have been experiencing. They may have changed during the update which would require you to alter them to best fit your environment. Also, there have been some changes to the wireless drivers so your previous settings may not be optimal in the latest version of firmware.

My xbox 360 always cannot to my 5Ghz wifi and says my password is wrong. However, it connects well to my 2.4Ghz wifi.

Check the security settings for 5ghz: Authentication method (WPA, WPA2, etc.), WPA Encryption (AES or TKIP), and enter in your password again on the router just in case anything changed.

With the new firmware I lost internet connection every now and then. My connection speed was also inconsistent and did stay at 144mbps most of the time.

Which band are you using 2.4 or 5ghz? It sounds like the signal to your client isn't as strong anymore. Have you tried changing the settings?

Also upgraded to .360, and didn't even see my 5GHz. network on my Roku, even though it was on and working. Even after rebooting the router, still no 5GHz. network in the living room.

Can you try moving your client closer to the router? It may be a signal issue and you need to change your settings to fit your environment. If you are within the same room as the router and it doesn't show up, please let me know. The 5ghz band shows up in my testing, but I am fairly close to the router.

Anybody know why recent fw wont work with fixed dns server? I tried to use any dns server on the fw, it wont connect to dns at all, it will only work if i set it up to auto mode and use my isp dns instead.

Can you tell me which ones you are trying? I have tested Google servers: 8.8.8.8 and 8.8.4.4 without any problems. Do you have problems with just this new firmware (.360)?


If anybody is still having problems, please email me at cl-jeremy@asus.com so that I may try to help.

 

[arul]

It was opendns.

 

[RMerlin]

It was opendns.

I've seen some oddities with OpenDNS, where it won't work properly with Asuswrt. This is caused by how the router handles DNS requests - it tends to send a first query with your local domain appended. Unfortunately, OpenDNS ignores the RFCs, and instead of returning a NXDOMAIN error (which would make the router resend the request again but without the local domain), it returns a catch-all IP, which causes your connection to fail as you end up with the wrong IP.

I'm not sure if it's a bug in either Asuswrt or the dnsmasq service itself, but in the end it's pretty much OpenDNS's fault for not handling DNS queries the way they are expected to be handled. If you have a professional account with them look for an option to disable that catch-all error page feature, so it will once again return a proper NXDOMAIN error.

If I recall, this is also documented in OpenDNS's FAQ.

 

[geko53]

Issue with USB printer

Seems that Asus didn't test build 360 all too thoroughly before releasing it...

After flashing 3.0.0.4.360 my USB printer (Kyocera 1300D) driven on the router's USB port couldn't be brought to print by no means (new installation, checking all the settings, reset, reset to factory default etc.).

Going back to 3.0.0.4.342 the printer immediately started working as expected again...

Hope that CL-Jeremy will deliver that flaw to the development crew...

Ciao
Gerald

PS: Austria still seems to be part of Australia as far as 3G modem settings are concerned But now we are prepared: we have kangaroos in the game park of Rosegg right now...

 

[RogerSC]

Also upgraded to .360, and didn't even see my 5GHz. network on my Roku, even though it was on and working. Even after rebooting the router, still no 5GHz. network in the living room.

Can you try moving your client closer to the router? It may be a signal issue and you need to change your settings to fit your environment. If you are within the same room as the router and it doesn't show up, please let me know. The 5ghz band shows up in my testing, but I am fairly close to the router.

Hi Jeremy...I did verify that 5GHz. was working for both .342 and .360 firmware versions. I have a laptop on the same desk as the router *smile*, and it connected on 5GHz. with both .342 and .360. However, for .360, the 5GHz. network didn't show up in the living room on my Roku, and it did show up for .342 with the same router settings and physical placement and orientation.

My comment was directed at relative signal strength of the 5GHz. networks, not at their functionality *smile*.

 

[RMerlin]

Hi Jeremy...I did verify that 5GHz. was working for both .342 and .360 firmware versions. I have a laptop on the same desk as the router *smile*, and it connected on 5GHz. with both .342 and .360. However, for .360, the 5GHz. network didn't show up in the living room on my Roku, and it did show up for .342 with the same router settings and physical placement and orientation.

My comment was directed at relative signal strength of the 5GHz. networks, not at their functionality *smile*.

Try setting a fixed channel in the low-numbered channels then in the higher-numbered channels, and see if you get better results with one or the other. It's possible that the automatic channel selection works differently in the newer firmware (or that the default power output was changed on one of the two channel bands).

 

[baadnewz]

360 vs 342 or Padavan's latest. Values reported by inssider, router position didn't change between versions nor the laptop on which i ran inssider.


5ghz channels 36+40 signal -48 to -50db on version .342 and padavan's latest
5ghz channels 36+40 signal -54 to -58db on .360 so yes the signal is weaker.

on top of that with the latest version im getting a lot of I/O errors on the attached usb hdd and unmounts (hdd is fine, tested on laptop ). ntfs driver update?

 

[RogerSC]

Try setting a fixed channel in the low-numbered channels then in the higher-numbered channels, and see if you get better results with one or the other. It's possible that the automatic channel selection works differently in the newer firmware (or that the default power output was changed on one of the two channel bands).

I don't use automatic channel selection. Usually use the higher numbered channels on 5GHz., and the same channel on both .342 and .360. It is true I didn't try a lower numbered channel for both firmware versions, or even for either version *smile*. When I get a chance, I'll try both firmware versions with a lower-numbered channel and see what the results are.

 

[antdes45]

Anybody know why recent fw wont work with fixed dns server? I tried to use any dns server on the fw, it wont connect to dns at all, it will only work if i set it up to auto mode and use my isp dns instead.

Well I had the same problem with the RT-N66U and 3.0.0.4.3xx beta until I erased the NVRAM.

 

[kayakj]

Has anyone gotten the "Mgmtringfullcount error" with this firmware version? Or did they find a way to fix the issue?

 

[slimypizza]

Client Status won't update

Beginning with the last FW update, I noticed that Client Status (from Network Map -> Clients) will not update properly when logging in to my N56U remotely. I had hoped .360 would fix this but that was not the case. Anyone else notice this?
This worked properly a couple of FW's ago. I used to be able to login remotely and tell who was at the house by which iPhone was logged in. Not anymore.

 

[AshCation]

Hello after updating the firmware my router is working fine , but something is annoying me on the logs:

Apr 20 14:19:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:20:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:21:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:22:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:23:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:24:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:25:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:26:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:27:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:28:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:29:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:30:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:31:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:32:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:33:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:34:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:35:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:36:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:37:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:38:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:39:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:40:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:41:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:42:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:43:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:44:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:45:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:46:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:47:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:48:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:49:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:50:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:51:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:52:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:53:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:54:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:55:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:56:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:57:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:58:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 14:59:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:00:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:01:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:02:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:03:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:04:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:05:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:06:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:07:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:08:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:08:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:09:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:10:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:11:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:12:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:13:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:14:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:15:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:15:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:16:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:17:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:18:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:19:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:20:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:20:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:21:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:22:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:23:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:24:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:25:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:25:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:26:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:27:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:28:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:28:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:29:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:30:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:30:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:31:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:32:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:32:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:33:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:34:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:35:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:35:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:36:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:37:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:38:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:39:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:40:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:40:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:41:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:42:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:44:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:45:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:45:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:46:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:47:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:48:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:49:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:50:10 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )  
Apr 20 15:50:23 kernel: ACT - SendBSS2040CoexistMgmtAction( BSSCoexist2040 = 0x6 )

What is that ? How do I remove it?

Also , Im using the same settings of the previous version and my wireless speed droped from 150Mbps to 72Mbps , its on 2.4Ghz 20/40Mhz , now I only get 150Mbps when I change to 40Mhz only.
Thanks.