BUG in 2.4GHz in Firmware Version:3.0.0.4.354

[pigpigxx]

Hi all,

Just upgrade to 3.0.0.4.354 for my AC66U. When trying to change the 2.4GHz setting to the follow,

Wireless Mode : Auto
Channel bandwidth : 20/40 MHz
Control Channel : Auto

press apply and reconnect, the router also change me back to

Wireless Mode : Legacy
Channel bandwidth : 20 MHz
Control Channel : Auto

and my 20/40MHz client can only connect in 20MHz with 54Mbps link speed

But before upgrade, my router using ver .270, I can use 20/40MHz in 2.4GHz and my client can connect in 150Mbps link speed.

is it a bug in the new firmware ? anyone experience the same thing ?

should I downgrade back to .270 to get a faster link speed ?

thx in advance.

pigpig

 

[RMerlin]

You have authentication set to Open System. Not sure if 802.11n allows this. Try setting it to WPA2-AES, which is the usual required security for 802.11n.

 

[pigpigxx]

BUG in 2.4GHz in Firmware 3.0.0.4.354

Hi Merline,

tried all different kind of encryption setting....same, still cannot change to 40 MHz...

does anyone having an AC66u have the same experience ?

 

[RogerSC]

Hi Merline,

tried all different kind of encryption setting....same, still cannot change to 40 MHz...

does anyone having an AC66u have the same experience ?

Generally speaking, being able to use 40MHz. for the 2.4GHz. band depends on having no interfering wireless networks in your area. On the other hand, my laptop connects at 216Mb/s with "20MHz. only" channel width set on 2.4GHz, so you shouldn't need 40MHz. channel width to get 150Mb/s connection. I can see you experiencing instability if you try to connect at 40MHz. and suggest that you change the channel width to "20MHz. only" and use that for a while. Also that you take a look at what networks are around you, and what channels that they're on, using something like inSSIDer. Then set the best channel (least interference) for you, rather than using "auto" channel.

By the way, the 54Mb/s limitation is generally because you can't go any faster than that without using WPA2/AES security. So you're limiting yourself right there.

 

[pigpigxx]

BUG in 2.4GHz in Firmware Version:3.0.0.4.354 Reply to Thread

Thanks Roger,

but still don't understand why 3.0.0.4.270 can setting like this BUT 3.0.0.4.354 cannot.

Also for security setting, I not using any encryption (I just use MAC address filtering), I think it will even faster than WPA2/AES, but my limit for the 2.4 channel is only 54Mbps.

pigpig

 

[RMerlin]

Thanks Roger,

but still don't understand why 3.0.0.4.270 can setting like this BUT 3.0.0.4.354 cannot.

Also for security setting, I not using any encryption (I just use MAC address filtering), I think it will even faster than WPA2/AES, but my limit for the 2.4 channel is only 54Mbps.

pigpig

WPA/AES ensures that traffic is encrypted. Otherwise, anyone sitting next to you can see your whole traffic. That includes unencrypted POP3 passwords, amongst other things.

MAC filter is not a security measure - it's very easy to spoof a MAC address, and bypass your filter. And since you have no encryption, guess how long it would take someone to figure out what MAC to clone...

 

[pigpigxx]

cannot change to Auto or N only

Hi all,

I follow all your advice, now in the 2.4Ghz channel changed to WPA/AES and channel to 11, keep the 20MHz, but I cannot change the "wireless mode" to "Auto" or "n ONLY". NO matter what I change, it will keep change back to "Legacy".

According to the balloon help, "Legacy" means the n connection will fix at 54Mbps.

Is that a bug in .354 ? anyone experience the same ?

see attach screen shot for details...

thanks in advance.

pigpig

 

[bluepoint]

What browser are you using? Have you tried another kind?

 

[pigpigxx]

have tried Win7+IE10, Win7+chrome ver25, Win8+IE10, Win8+Chrome ver25

So, your ac66u can change the wireless mode to "auto" in 2.4GHz ?

pls advice...
pigpig

 

[bluepoint]

have tried Win7+IE10, Win7+chrome ver25, Win8+IE10, Win8+Chrome ver25

So, your ac66u can change the wireless mode to "auto" in 2.4GHz ?

pls advice...
pigpig

Yes but it's an N66. If it seems stuck in legacy mode then there is something triggering it. Re-download a fresh firmware 4.354 copy then reflash the router with all your wireless clients turned off except for the pc you're using to flash. Reset to factory defaults using NVRAM clear(telnet to router) then re-configure the router from scratch. Good luck!

 

[doubleroll]

I have my 2.4 GHz set to with 354 firmware:
Wireless Mode = Auto (b/g Protection enabled)
Channel Bandwidth=40 MHz
Control Channel=3l
Authentication=WPA2-Personal
Encryption=AES

 

[kentk]

Also stuck in legacy with 354

Did anyone find a way out of this?

This is my first post here so please forgive me if I over share. On the chance that this is still an open issue, I have listed some additional steps I took below in the hope what did not work helps narrow down a solution.

I am seeing the issue with fw from both Asus '354 and Asuswrt-Merlin 3.0.0.4.354.29 (Merlin build).

I additionally found that reverting to '270.26b allows setting 2.4ghz wireless mode to Auto and 802.11n was able to go well beyond 54mbps.

I saved the configuration and then reinstalled '.354.29. Although the 2.4ghz wireless mode stayed Auto, the actual rate would now not go beyond 54mbs.

When I hit apply on the 2.4ghz general wireless page the mode went back to Legacy.

As a last step, I restored the '270.26b configuration from above. The wireless mode still showed Auto but the rate remained limited to 54mbps.

My take away from all this is that:
1. I have an ac66u that can do 802.11n in 2.4ghz with '270 fw.
2. Upgrading to 354 fw caps 802.11n at 54mbs independent of what wireless mode shows.
3. Under '354, Applying the general wireless page always sets the mode to legacy.

I really like the increased functionality of Asuswrt-Merlin 3.0.0.4.354.29. Call me greedy but I would like N in 2.4ghz AND the Merlin features

Hope this helps.

Kent

 

[kentk]

With 354.29, the mode will reset to legacy if any legacy (non N) client is connected when apply is clicked.

This can be tested by turning off the 2.4ghz radio (professional), apply, set wireless mode to auto, apply. The mode will remain auto.

Now turn on the radio and apply. The wireless mode spontaneously resets to legacy.
This wireless mode responds normally under 270.

Hope this helps.

Sent from my SGH-I777 using Tapatalk 4 Beta

 

[kentk]

At least part of the answer is here:
http://www.smallnetbuilder.com/wireless/wireless-features/31743-bye-bye-40-mhz-mode-in-24-ghz-part-1

Since the AC66U is listed as one of the few that implements a spectrum check, I think the behavior some of us are seeing is a full implementation of being "neighborly".

I am channel 6 in this scan. Here's what I think is going on: When the AC66U sees this environment, it will not allow 40mhz mode. I think it may also be restricting 802.11N to "legacy" mode to further limit bandwidth and reduce interference.

Not allowing 40mhz in this case makes sense under the new spec.

I don't think limiting N to 54mbs as well is required. N uses multi path and selective cancelation to create multiple information channels on the same frequency. This is the reason for three or more antennas.

Because it is designed to separate multiple information channels on the same frequency, a major feature of N is high tolerance to interface. Restricting the AC66U to 54mbs just hurts it's performance without much reduction to interference.

As it was in .270, please consider allowing Auto and N only modes independent of the detection of signals on nearby channels.

Thanks.

Sent from my SGH-I777 using Tapatalk 4 Beta