New FW - ASUS RT-N66U Firmware Version 3.0.0.4.374.720

[shooter40sw]

Cant wait for Merlin to get his hands on this FW, this one says it fixes the 5ghz issues with the SDK6, something Merlin has already done on the pixie dust, thats the one I´m using in this moment, hope this one fixes the lower range on the 5ghz.
Keep up the great job! Thanks for the great firmware

 

[Bad Teddy]

Cant wait for Merlin to get his hands on this FW, this one says it fixes the 5ghz issues with the SDK6, something Merlin has already done on the pixie dust, thats the one I´m using in this moment, hope this one fixes the lower range on the 5ghz.
Keep up the great job! Thanks for the great firmware

Fixes the 5GHz issues as in... the ones from the old SDK?

Or fixes the 5GHz issues as in... the ones from SDK6? Because Pixie Dust doesn't fix those.

I'd check the website, but it doesn't even work for me right now -_-

Edit: Nvm, Google caching wins again. Looks like they've switched to SDK6 officially now basically.

Description ASUS RT-N66U Firmware Version 3.0.0.4.374.720
Please note: This version add many new features, please press the reset button more than 5 seconds to reset the RT-N66U after firmware upgraded to prevent unexpected problem.

AiCloud 2.0 released
1.All new web interface
2. Support video subtitles (.srt format) For better video compatibility, windows user need to update VLC to v2.0.8 or later
3. File/ folder can be shared to Facebook(router must have public IP)
4. Supported mobile version web interface
5. Supported router to router sync
Please refer to video via:
http://www.youtube.com/watch?v=vG6BEjUrzfc&feature=share&list=UUlSsNTCjMEGj8Guo_NmiMWA
6. Fixed smartsync related issues.

Add:
1. Repeater mode( in Administration --> Operation mode)
2. Dual WAN (in WAN -> Dual WAN)
3. Unmount all disks with 1-click
4. Disk scan feature. It is in external USB disk status tab in network map.
5. Support Sandisk Cruzer flash drive with both CD-ROM and flash disk interface.
6. Auto adjust time zone in internet setup wizard process.
7. PPTP VPN server status GUI
8. Recognized .rmvb files as video format in media server.
9. Show more detail information in USB application install process.

Fixed:
1. Upgraded to SDK6 driver to fix 5GHz connection issue.
2. Fixed HK ISP DHCP connection issue.
3. Fixed USB application update related issues.
4. Reduced the redundant packets when used 3G/4G dongle as WAN and opened web browser.
5. Fixed the traffic monitor related issues when used 3G/4G dongle as WAN,
6. Fixed client duplicated issue in network map
7. removed modem setting button in AP mode
8. Fixed IE related parental control issue.
9. Disabled the Broadcom ACSD service to prevent buffer overflow vulnerabilities.
10. Fixed AiCloud vulnerability related bugs.
11. Underline "_" can now be acceptable in device name and computer name.
12. Hide Broadcast option in PPTP VPN server when it is disabled.
13. Fixed multicast IPTV related issues in PPPoE/PPTP/L2TP connection.
14 .Fixed parental control offset issue in IE.
15. Fixed 3G dongle related issue.
16. Hide ASUS DDNS description when selecting 3rd party service.
17. Fixed script error 'invalid argument on IE'
18. Fixed smart sync JS error
19. Fixed JST time zone issue.

IPv6
1. Fixed PPP IPv6 global address retrieval
2. added DHCP-PD option
3. Added LAN DHCPv6 server
4. Added network status GUI.
5. Added option domain name if available

3G/4G dongles
1. Support Yota LTE dongle LU150
2. Support ZTE LTE dongle MF821
3. Support 3G dongle Q110
4. Support Huawei EC306

update 2013.09.11

 

[GoNz0]

that is one hell of an update, let us hope Merlin can get the source code as this is a good update.

 

[RMerlin]

that is one hell of an update, let us hope Merlin can get the source code as this is a good update.

The vast majority of the changes listed are from the previous release. Still a major release nonetheless as it includes Dual WAN and Repeater mode (already present in my experimental builds tho), AiCloud 2.0 (available in my latest test release, tho based on older code).

Asus has indeed switched to the SDK6 version of the wireless driver. The SDK6 driver resolves the vast majority of connection issues on the 5 GHz band. If you still have issues with it, it's probably a different cause than what was affecting a bunch of Intel and Broadcom-based clients. Try the usual:

1) Reset to factory defaults, and manually reconfigure (do NOT reload saved settings)
2) Delete the wireless profile on your affected client
3) Update your wireless driver (some older Intels and older Atheros drivers are quite buggy).

For Intel, there is a more widespread issue at the moment that does not only affect Asus (in addition to the recent issue with the 5.110 driver, that was more specific to Asus). The Intel forums have a lot of posted complains.

 

[RMerlin]

With Asus now switching to that version numbering scheme BTW (3.0.0.4.374.720), that makes it a bit confusing for everyone. Not sure why they felt the need to add ANOTHER digit. So now, 374.xxx can be either an Asus release (374.720) or an Asuswrt-Merlin release (374.33). I don't want to add ANOTHER digit on top of 374.720, so time to figure out a numbering scheme that will be more obvious to everyone

 

[bluepoint]

that is one hell of an update, let us hope Merlin can get the source code as this is a good update.

Initial test used as an AP.

1. 5GHz band signal strength/performance is equal to 374.33
2. 2.4GHz band signal is -10 weaker than 374.33

inSSIDer used to measure above. Both 374.720/374.33 were able to achieve my full service speeds of 60/40Mbps and stability is there. I'll leave other features for others to test.

Edited/added:
After an hour on the same location where I tested, the 2.4GHz band got better signal showing same signal strength as the 374.33. Now that's improvement.

 

[theirongiant]

The Intel forums have a lot of posted complains.

I have read reports online that some people who have complained are having their forum accounts deleted.

 

[uncle.f]

With Asus now switching to that version numbering scheme BTW (3.0.0.4.374.720), that makes it a bit confusing for everyone. Not sure why they felt the need to add ANOTHER digit. So now, 374.xxx can be either an Asus release (374.720) or an Asuswrt-Merlin release (374.33). I don't want to add ANOTHER digit on top of 374.720, so time to figure out a numbering scheme that will be more obvious to everyone

What's with the 3.0.0.4 bit? that seems to never change.
How about numbering Merlin releases like 374.720.xxx without the 3.0.0.4?
And xxx could start with letter 'm' to signify Merlins build.

374.720.m33

 

[PrivateJoker]

With Asus now switching to that version numbering scheme BTW (3.0.0.4.374.720), that makes it a bit confusing for everyone. Not sure why they felt the need to add ANOTHER digit. So now, 374.xxx can be either an Asus release (374.720) or an Asuswrt-Merlin release (374.33). I don't want to add ANOTHER digit on top of 374.720, so time to figure out a numbering scheme that will be more obvious to everyone

Combine the marketing minds at Google & Apple in their version naming departments, put your Canadian heritage into it. . .and go Canadian province capitals as the main build, and cycle through Tim Horton's donut varieties as the sub-builds. . .so like arbitrarily we could start off on codename: Regina Dutchie. Hey, I'm just throwing it out there. . . And no, I've never worked on Madison Avenue if that's what you're thinking.

I have read reports online that some people who have complained are having their forum accounts deleted.

Who do you think is the biggest force behind the whole "big jack" debacle? Intel! They own the NIC game. First they delete your accounts when you complain. . .then they leave an overheated AMD CPU on your car hood.

 

[cmillar6]

what exactly does SDK6 mean?

 

[RMerlin]

What's with the 3.0.0.4 bit? that seems to never change.
How about numbering Merlin releases like 374.720.xxx without the 3.0.0.4?
And xxx could start with letter 'm' to signify Merlins build.

374.720.m33

The base numbering scheme will have to remain the same, so to indicate the basic Asus build on which the code is based. The problem is that currently Asus seems to be working on at least two parallel branches of the 374 code, so the RT-AC56U 374.134 code is newer than the RT-N66 374.257 code. Since I have only one code branch for all devices, I can't go back and forth with that new digit as I switch t newer code - it will confuse everyone. We'd end up with 374.134.33 being newer than 374.257.32.

With any luck, maybe Asus is going with that extra digit until the day where they can merge back both branches. It's certainly doable - I've done it with my own code.

 

[RMerlin]

what exactly does SDK6 mean?

SDK = Software Development Kit. Broadcom creates the chips, and creates basic code and development tools for manufacturers to build their router firmware around it. This is called an SDK.

Broadcom's 802.11n devices were based on version 5.xxx of their SDK. The wireless driver used by Asus in 3.0.0.4.2xx was based on SDK 5.100. With 3.0.0.4.3xx they switched to 5.110. That introduced the major connectivity issues with Intel devices (amongst others).

The 802.11ac devices from Broadcom are based on SDK 6.xxx. Asus tried to resolve the issues with the 5.110 driver, with very limited success. So they decided to simply upgrade the RT-N66U to the same SDK (and therefore same drivers) as used by the RT-AC66U. Chances are Broadcom is more actively developing SDK 6.xxx than the older SDK 5.xxx at this point.