Asus .370 F/W released today

[ezhangin]

I am running 3.0.0.4.370_172-g85af9d0 here.

When I click <Check> on the Administration > Firmware Upgrade > Firmware Version I get:

"No Internet connection is detected. The router cannot connect to ASUS server to check for the firmware update. After reconnecting to the Internet, go back to this page and click Check to check for the latest firmware updates."

Obviously this message is bogus as I have full IPv4 and IPv6 Internet connectivity. Comcast is my ISP. Anyone else seeing this?

I'm getting that message as well.

 

[wickedny5]

why check for firmware upgrade via UI? it has never worked anyway. I dont think it is for much concern. Performance and stablility seems to have been fixed for me, im getting much better throughput on 2.4 and 5ghz

 

[RogerSC]

This has been asked above, but not really answered for me. I'd like to know what USB-style dual-band wireless adapters are working at full speed (450Mbps) with this firmware? I have a Linksys AE3000, and while it connects at full speed with the 270.26 firmware, with the new .370 firmware it only will connect at 216Mbps.

Is anyone getting 450Mbps with this firmware that's using a USB-style dual-band wireless adapter? If so, can you please tell me the make and model of it? I'm happy with my wireless adapter otherwise, but it wouldn't be bad to have a backup, too *smile*.

Wondering about the ASUS USB-N66 Dual-band Wireless-N900 Adapter (or USB-AC53)...you'd think that Asus would have tested with at least one of these, anyone using them successfully with this new firmware?

Or I might just wait until Asus puts out a fixed wireless driver for this router.

Thanks much.

 

[sm00thpapa]

Asus replied to me today and stated that the 5 Ghz band is fixed with .370. Only time will tell.

 

[RogerSC]

Asus replied to me today and stated that the 5 Ghz band is fixed with .370. Only time will tell.

I guess that they don't test much, or read here, then. It isn't fixed for several people that have posted already. Apparently some people are seeing an improvement, but some of us still can only get a 20MHz. channel width connection on 5GHz. (216Mbps instead of 450Mbps).

Guess I'll send a report to Jeremy if Asus thinks that 5GHz. wireless is fixed.

 

[dsring]

I tried .370 F/W for about 24 hours. 5 GHz wireless was unstable, and is not fixed for me. I reverted back to .270 F/W.

 

[sm00thpapa]

Just got a reply from Asus and they said their team is currently investigating the issue and will get back with me.

 

[RMerlin]

Asus replied to me today and stated that the 5 Ghz band is fixed with .370. Only time will tell.

My own contact told me last week that they had no news yet regarding the 5 GHz issue, so I doubt that it's fixed in 370.

 

[jlake]

I'm still trying to figure out why a 2 year old Linksys AE2500 USB 2x2 wireless adapter with Broadcom chipset (and I assume Broadcom driver) is no longer compatible with a Broadcom chipset wireless router (Asus RT-N66U) with Broadcom wireless driver on 5Ghz. Puzzled.

Edit:

The crazy thing is the Linksys/Broadcom AE2500 has an advanced setting of "compatibility" which you can choose over the default "performance" setting. Neither of them work well on 5Ghz.

Edit2: Disregard above.. I put the Linksys AE2500 back on "compatibility" with the new 370 firmware and it's now working! So it appears they did something.

 

[sm00thpapa]

This is ridiculous for such a high end company like Asus in which I respect very much to have such a problem with a product that hasn't been fixed in a few months. Totally uncalled for. That's just my opinion.

 

[bmb]

I'm thinking of coming back from Tomato to a stock firmware, (don't need QoS anymore), can I ask if this version has a block website access with keyword feature?

Thank you.

 

[sm00thpapa]

I'm thinking of coming back from Tomato to a stock firmware, (don't need QoS anymore), can I ask if this version has a block website access with keyword feature?

Thank you.

I'm running Merlin's 3.0.0.4.270.26b and it has this feature and this firmware is the most stable I would have to say.

 

[bmb]

I'm running Merlin's 3.0.0.4.270.26b and it has this feature and this firmware is the most stable I would have to say.

Thanks, that's the one I'll go with then.

 

[darkstalker]

Mind you that on fast connections, (url/keyword) filters greatly decreases throughput. I've got 300Mbit/300Mbit fiber connection at home, and when I active the filter with just one keyword/rule, the speed already drops to 185Mbit. When I disable it, the speed goes back to 300Mbit. Of course, on slower connections it might be less noticeable.

 

[RMerlin]

This is ridiculous for such a high end company like Asus in which I respect very much to have such a problem with a product that hasn't been fixed in a few months. Totally uncalled for. That's just my opinion.

The solution already exists: run 3.0.0.4.270. The 5 GHz band works fine on it, therefore there is no emergency there in fixing this.

 

[RMerlin]

Mind you that on fast connections, (url/keyword) filters greatly decreases throughput. I've got 300Mbit/300Mbit fiber connection at home, and when I active the filter with just one keyword/rule, the speed already drops to 185Mbit. When I disable it, the speed goes back to 300Mbit. Of course, on slower connections it might be less noticeable.

That's because this feature is incompatible with hardware acceleration.

 

[Bad Teddy]

This is ridiculous for such a high end company like Asus in which I respect very much to have such a problem with a product that hasn't been fixed in a few months. Totally uncalled for. That's just my opinion.

The solution already exists: run 3.0.0.4.270. The 5 GHz band works fine on it, therefore there is no emergency there in fixing this.

Can't speak for everyone, but if it weren't for my Xbox, I would definitely be on .270 like Merlin said.

 

[RMerlin]

Can't speak for everyone, but if it weren't for my Xbox, I would definitely be on .270 like Merlin said.

Try running the following commands over Telnet/SSH - they might work under 270:

wl -i eth1 ldpc_cap 0
wl -i eth2 ldpc_cap 0

Then go make any change to the Wireless page and apply them (to force the wireless service to be restarted), or run the following (if using my firmware):

service restart_wireless

See if your XBox can connect after that. This is what the XBox option does.

 

[jlake]

When 370 was released, I flashed it and it behaved just like 354 beta on 5ghz. So I flashed back to 270.26b and everything was fine again. Last night, I decided to try 370 again. However, after I flashed 370, it told me that I needed to do a manual reboot of the router. So I power cycled the router (unplugged from electrical outlet for 30 seconds). I put my Linksys AE2500 2x2 wireless adapter on compatibility mode and it worked fine on 5 ghz. I couldn't believe it. Then I decided to change the 2.4 ghz on the router from the default settings to "N-only". When I did this, it started messing up the 5 ghz (link speed dropped and fluctuated between 81Mbps and 108Mbps-- it started behaving like 354 again. This lasted for 30 seconds. Then it jumped back up to 300Mbps and stayed there. So being curious, I went to device manager and uninstalled my wireless adapter (which put it back to its default settings--performance mode and also removed all of my wireless profiles). It's working fine now too......at least it's been working fine for 12 hours.

I'll let anybody draw their own conclusions as to what happened so that it's working fine now. But the chain of events above is exactly what happened.

 

[Bad Teddy]

Try running the following commands over Telnet/SSH - they might work under 270:

wl -i eth1 ldpc_cap 0
wl -i eth2 ldpc_cap 0

Then go make any change to the Wireless page and apply them (to force the wireless service to be restarted), or run the following (if using my firmware):

service restart_wireless

See if your XBox can connect after that. This is what the XBox option does.

Oh, so humble. Why WOULDN'T I be using your firmware

Anywho, thanks for the tip though. I'll definitely check it out if need be (when my 5GHz screws up again)

Decided to tamper around with things pointlessly and wound up updating my CFE the other day and, just for the hell of it, played around with my 5GHz settings. For whatever reason, 40MHz is working right now on .354

I have changed my wireless driver a few times just to find one that allows my bluetooth switch on my laptop to work properly, but I havn't used any driver that I havn't used before and verified as being unstable on the 5GHz frequency. So unfortunately I've added too many variables to really figure out why it's working without intentionally breaking it, and I really prefer it remain working right now haha.