FW_RT_N66U_B1_3003144 Released!

[cc666]

ASUS RT-N66U B1 Firmware Version 3.0.0.3.144
Fix bugs:
1. UI related bugs
2. Network map cannot show device name.
3. QoS control for wired connected devices.
4. Special character name/password issue in VPN server.
5. Download master installing issue in AP mode.
6. PPPoE compatibility issue.
7. L2TP compatibility issue.
8. Sonos audio system and network map compatibility issue.

Modified
1. Enable cross night setting in wireless radio on/off setting page.
2. Adjust WDS connection rule
3. Enable Beceem Wimax support.
4. Change default wireless security to WPA-AES in QIS.
5. Add Spanish language.
6. Modify VPN server UI.

At FTP site:


ftp://ftp.asus.com.tw/pub/ASUS/wireless/RT-N66U_B1/

or here:http://support.asus.com/download.as....B1)&p=11&s=2&os=30&hashedid=PZkFHlMrGWzVROxT

Just flashed........

CC

 

[RMerlin]

They're early. I was told it would be released only next Thursday.

 

[AnthonyArmato]

Well, while setting up user defined QoS.... Saving it basically did a factory reset on the router.

Second try didn't do that. Odd.

 

[NeutralGold]

I was really hoping for the nvram fix.
I upgraded and no such luck.
ASUSWRT RT-N66U_3.0.0.3 Fri Jun 15 14:09:13 UTC 2012
admin@RT-N66U:/tmp/home/root# nvram show >/dev/null
size: 32569 bytes (199 left)
admin@RT-N66U:/tmp/home/root#

 

[zbeyuz]

When I tried to put all the popular services and PSP like: BitTorrent eDonkey and eMule together in User Defined QoS mode, my router can't connect anymore after clicking the save button.
I have to reboot the router in order to connect to the router's website again. Anyone encounter this problem ?
P/s: I also tried to clear Nvram before and after flash this firmware but no luck.

 

[AnthonyArmato]

QoS is giving me some problems still when I configure it. Also NVRAM is back to 32K from that one beta that really wasn't discussed, 9.0.0.3/.

 

[NeutralGold]

All of my static assigned ip's do not show up any longer in the UI. They are all still being assigned, I just can't view/edit them. As you see in my previous post, my nvram is full so I don't dare add another right this minute. I will probably just switch to shibby's latest test build with the "ug" fix and latest wireless drivers. I hear good things so far. The only drawback is that wireless throughput isn't as good as the default firmware.

 

[RogerSC]

They're early. I was told it would be released only next Thursday.

From what I'm reading here, they cut their testing time short *smile*. Staying with .108 firmware until I hear something that makes it worth my while to upgrade.

 

[Gitsum]

From what I'm reading here, they cut their testing time short *smile*. Staying with .108 firmware until I hear something that makes it worth my while to upgrade.

Actually, getting it out to us beta testers early, they INCREASED their testing time.

 

[richardeid]

Since the RT-N16 firmwares are (sometimes) being released in parallel with the RT-N66 firmwares, I'm gonna semi-hijack this thread...

So the .144 firmware was also released today for the RT-N16. I updated and had an odd problem. Here's what I did.

1. Was on .108 and started a telnet session to perform: mtd-erase -j nvram
2. Disconnected all other machines, except the one I was going to perform the firmware update from, as well as the WAN connection
3. Rebooted after mtd-erase, still on .108
4. Navigated to the administration page and upgraded the firmware
5. Rebooted and waited about five or so minutes before beginning reconfiguration
6. Manually applied all my old settings; Didn't restore settings from a file

So all seemed well until I got to the last step I usually perform, which is configuring all my port forwarding settings. Once I was done with that, I had no Internet access, neither IP or DNS, from any of my machines. All LAN connections continued to work properly. From a telnet session into the router I could ping www.google.com successfully, but couldn't ping it from any machine behind the router. Though I could browse other machines and even bring up a web page I'm hosting on another machine. I have only five port forwarding rules, so I figured it would be easy to check them one by one to see which one was the cause of the problem.

Now, all but one of those port forwards are just a single port being forwarded. So like...I have four that look like this:

VNC 1234 192.168.0.5 BOTH

However, one of the rules, which has worked on all previous firmware builds, forwards multiple ports like so:

GAMESERVER 7777,7778,7787,55555,55566 192.168.0.6 BOTH

And as soon as I applied the rules with GAMESERVER added, that's when the WAN stopped working. So I tried various combinations to see if anything obvious popped up. First I tried only using 7777:7778(note the : instead of the ,) and not the other three required ports. This didn't halt the operation of the WAN link. So I added the rest of the ports one by one, each with their own separate entry. And all continued to work...and of course the server was then working(read: accepting connections).

So then I experimented a little more. Instead of 7777:7778 I changed it to 7777,7778...and bam, no Internet access. Playing around a little more and trying to combine some of the other rules and I found that if you're using a , in the port forwarding rules then it's going to break. So for now, I'm just giving a separate rule for each of the required ports for that server and that's fine...but for cleanliness I'd like to trim it back down to one rule if possible.

Remember that I said I was using the N-16 and not the N-66? Well it's darn hard to find people with an RT-N16 that I can contact to try to repro this issue. So I'm wondering if any of you who are using the N-66 can try this out to see if the same problem is affecting your routers. Or if any N-16 owners are reading this, can you also please test this out? Pretty much all you'd have to do is add a rule with multiple ports, separated by commas. Then apply that rule and try to refresh a web page you might already have open in your browser.

Thanks for your time.

 

[RMerlin]

However, one of the rules, which has worked on all previous firmware builds, forwards multiple ports like so:

GAMESERVER 7777,7778,7787,55555,55566 192.168.0.6 BOTH

And as soon as I applied the rules with GAMESERVER added, that's when the WAN stopped working. So I tried various combinations to see if anything obvious popped up. First I tried only using 7777:7778(note the : instead of the ,) and not the other three required ports. This didn't halt the operation of the WAN link. So I added the rest of the ports one by one, each with their own separate entry. And all continued to work...and of course the server was then working(read: accepting connections).

That bug was in previous releases of the firmware as well. I fixed it in my custom RT-N66U firmware a few weeks ago:

https://github.com/shantanugoel/asus-rt-n66u-merlin/commit/b11fc266c161e40d5c1a69f1c4f2d80dfe5558bd

 

[richardeid]

Thanks! I try to keep up with the goings on of the N66 because the firmware is the same. It even says something like "built for N66U" in the logs during the startup of the N16. But I guess I missed this one. I appreciate you taking the time to correct it. Hopefully ASUS will fix it up in a coming release.

 

[njweb]

1. I am curious if anyone has compared wifi performance (preferably throughput, if not at least comparative signal strength) before the update to the performance after the update.

I will run some tests before upgrading and then test if afterwards.

2. Another thing is stability.
My RT-N66U has been ultra stable, so I hope that remains the same with firmware v144.
If not I will 'downgrade' to the version I have been using since, given my type of use, I am not affected, to my knowledge, by ANY of the issues v144 resolves.

 

[RMerlin]

Thanks! I try to keep up with the goings on of the N66 because the firmware is the same. It even says something like "built for N66U" in the logs during the startup of the N16. But I guess I missed this one. I appreciate you taking the time to correct it. Hopefully ASUS will fix it up in a coming release.

They did include the Sonos fix I emailed them, so maybe I will also send them that fix as well, for inclusion in a future release.

And you are correct: many devices share the same Asuswrt base code now: N16,N53,N56U,N66U,AC66U, and a few others I forgot. There's also a reference to the N10D in build 144. I wonder what the "D" stands for...

 

[NightOwl326]

Accessing a usb drive is a no go with this firmware my mac.

 

[small_law]

1. I am curious if anyone has compared wifi performance (preferably throughput, if not at least comparative signal strength) before the update to the performance after the update.

I will run some tests before upgrading and then test if afterwards.

2. Another thing is stability.
My RT-N66U has been ultra stable, so I hope that remains the same with firmware v144.
If not I will 'downgrade' to the version I have been using since, given my type of use, I am not affected, to my knowledge, by ANY of the issues v144 resolves.

I only spent a little time with .144 today, but it seemed stable to me. The admin page was faster to navigate and was able to set up Asus' DDNS. I couldn't request an asuscomm.com address with .112. Signal strength looks like the same to me, but I have the tx power set to 120.

I've tried enabling QoS a number of times, both in automatic and user-specified modes. I was messing around with the user-specified mode in .112 last night and the admin page locked up. In the end, I had to restore the router. The only QoS mode I've been able to enable consistently is automatic and it always seems to slow down everything, including activities it supposedly prioritizes. I'm just going to stay away from QoS on this thing for now. Throughput is excellent for me without it.

 

[RMerlin]

I finally had some time to test build 144:

- The router still crashes when my laptop connects to it (bug they introduced when they switched their QoS code to use the bridge_netfilter kernel module)

- The router still crashes if I connect through VPN by using the same subnet as the LAN, and try to access a device sitting behind the firewall

This firmware fixed a few issues, but there's still a lot left to fix I'm afraid

 

[Gitsum]

Been using it today without any problems. They did add a lot of presets for the QOS manual mode. Games, services and whatnot with preset ports. I don't recognize half of the game presets. Must be games popular in other countries. I did notice when adding their Counter Strike -Source presets, it tells you that the string cannot have the "-" character in the name, so you have to still do a little manual editing. (Maybe Merlin can clean that up for us)
The WiFi to LAN QOS issue seems to be fixed now. I wonder if thats what they meant by "QoS control for wired connected devices." in the fix list, or does that mean QOS only worked on wireless connections before??

 

[xrecar]

Forget using two hard drives via usb

/mnt/ is not selectable. Flashed back to 9.0.0.3.128.

I just recommended this router to a buddie too. Wish they hadn't of made that change.

 

[KevTech]

After a while devices not showing in client status anymore.