Dual Channel Broadcast?

[rljames]

New install of AC66U (firmware v3.0.0.4.266) configured with "Wireless Mode: Auto, Channel Bandwidth: 20/40 MHz, b/g Protection: Checked, Control Channel: Auto" initially showed (via inSSIDer scan) dual channel (1+5) broadcast on 2GHz band and wireless PC (Intel N-2230) connecting at 300Mbps.

However, after connecting all wireless and wired devices, PC connection speed dropped to 144Mbps and AC66 broadcast to single channel. And nothing I reconfigure on the AC66U end will return the broadcast to dual channel. I live in an area with no nearby wireless networks.

(Prior Netgear WNDR3700 consistently stayed in dual channel w/same devices connected)

Any ideas?

 

[mikeg]

First of all , update to the latest firmware .354 and see if your problems are solved with that first.

New install of AC66U (firmware v3.0.0.4.266) configured with "Wireless Mode: Auto, Channel Bandwidth: 20/40 MHz, b/g Protection: Checked, Control Channel: Auto" initially showed (via inSSIDer scan) dual channel (1+5) broadcast on 2GHz band and wireless PC (Intel N-2230) connecting at 300Mbps.

However, after connecting all wireless and wired devices, PC connection speed dropped to 144Mbps and AC66 broadcast to single channel. And nothing I reconfigure on the AC66U end will return the broadcast to dual channel. I live in an area with no nearby wireless networks.

(Prior Netgear WNDR3700 consistently stayed in dual channel w/same devices connected)

Any ideas?

 

[rljames]

Isn't the .354 firmware still in beta/ And if so, not sure I want more problems than I already have...

 

[RMerlin]

Isn't the .354 firmware still in beta/ And if so, not sure I want more problems than I already have...

But it's possible that your issue was resolved in this new beta, especially since it uses a new wireless driver. It's definitely worth trying in your case, you can always revert back to FW 270 (the most recent non-beta) if it doesn't work out.

 

[rljames]

But it's possible that your issue was resolved in this new beta, especially since it uses a new wireless driver.

Upgraded to 354 firmware. No change in broadcast channel behavior.

 

[graison]

Setting channel bandwidth to 40MHz does nothing?

 

[rljames]

Setting channel bandwidth to 40MHz does nothing?

Setting the "Channel Bandwidth" to "40 MHz" exclusively has no effect. AC66 insists on single channel 1 broadcast. Signal strength is about -40 dBm. I did notice this morning another network appear on channel 6 with weak signal.

What are the rules for this setting? For instance, what is the operational difference between "20/40" and "40" MHz? I would haved guessed that "20/40" allowed the AC66 to intelligently choose and "40" forced bandwidth but that doesn't seem to be the case.

How does the "b/g Protection" setting play into channel selection and/or performance to "n" devices? Could some device on my network be limiting channel selection/width?

 

[mikeg]

Have you tried to do factory reset and if that doesn't solve the issue clearing the nvram ?

Upgraded to 354 firmware. No change in broadcast channel behavior.

 

[rljames]

Have you tried to do factory reset and if that doesn't solve the issue clearing the nvram ?

What is the logic behind these two tasks?

I know firmware 354 has installed correctly because new "features" are active and other aspects of router are working OK.

 

[mikeg]

Because I have had issues which was solved with these two tasks,
If you try them and get your issue solved then you have the answer yourself.

What is the logic behind these two tasks?

I know firmware 354 has installed correctly because new "features" are active and other aspects of router are working OK.

 

[RMerlin]

What is the logic behind these two tasks?

I know firmware 354 has installed correctly because new "features" are active and other aspects of router are working OK.

There are some internal settings that have new default values with 354. Not resetting to factory defaults means your router will still use the older values.

 

[rljames]

There are some internal settings that have new default values with 354. Not resetting to factory defaults means your router will still use the older values.

OK, what is the recommended method to "factory reset" and clear NVRAM?

Is there a means to view these "values"?

 

[RMerlin]

OK, what is the recommended method to "factory reset" and clear NVRAM?

Is there a means to view these "values"?

Either keep the reset button pressed for a few seconds while the router is turned on, or power it on while the WPS button is pressed - both work just as well.

The whole nvram content can be dumped through SSH with "nvram show".

 

[rljames]

OK, reset NVRAM and to default config as directed via power on WPS button held.
(Required some manual re-setup via Wizard before access to Administration -> Restore; Saved Config)

Noticed that previous SSID was *partially" remembered. Wireless was displayed as "ASUS" but hard wired reconnected to pre-reset SSID...

Anyhow, no affect on single channel broadcast width when configured at 40MHz.

 

[RMerlin]

OK, reset NVRAM and to default config as directed via power on WPS button held.
(Required some manual re-setup via Wizard before access to Administration -> Restore; Saved Config)

Do not restore your saved settings, otherwise you won't have changed a single thing - you're back with exactly the same settings as before, which totally defeats the purpose of resetting to factory defaults and reconfiguring everything.

 

[rljames]

Do not restore your saved settings, otherwise you won't have changed a single thing - you're back with exactly the same settings as before, which totally defeats the purpose of resetting to factory defaults and reconfiguring everything.

Well that's abit of a pain! (Especially since it appears I'm also experiencing wired connection slowdown as reported in another post) Must be a better way? Is this reset and reconfig process required after every firmware upgrade?

Why was the old SSID remembered by the wired connection?
(Occurred before config restore)

And I'm curious - Does ASUS release new firmware on some set periodic schedule (like every 6 months) or "as needed"?

 

[mikeg]

You should not rely on saved configs only , use paper and pen and write down your settings so you have them available when you need them.
Do factory reset first and try with that , if not ok do the clear nvram.
Manually write in your own settings.
Some users do the clear nvram when updating firmware , I just do it when I run in to problems , just like you have done.
Why your old SSID was remembered I do not know - perhaps you failed when you made either of the tasks.
No set intervalls for Asus to release new firmware - just as you wrote
"as needed".

Well that's abit of a pain! (Especially since it appears I'm also experiencing wired connection slowdown as reported in another post) Must be a better way? Is this reset and reconfig process required after every firmware upgrade?

Why was the old SSID remembered by the wired connection?
(Occurred before config restore)

And I'm curious - Does ASUS release new firmware on some set periodic schedule (like every 6 months) or "as needed"?

 

[rljames]

Do factory reset first and try with that , if not ok do the clear nvram.

Wait a minute, as I understood RMerllin, reboot w/WPS held performed BOTH factory config reset AND NVRAM clearing?

Is there more to the NVRAM part? And if so, is the order important?

 

[RMerlin]

Well that's abit of a pain! (Especially since it appears I'm also experiencing wired connection slowdown as reported in another post) Must be a better way? Is this reset and reconfig process required after every firmware upgrade?

Why was the old SSID remembered by the wired connection?
(Occurred before config restore)

And I'm curious - Does ASUS release new firmware on some set periodic schedule (like every 6 months) or "as needed"?

The SSID was probably a side-effect of your browser cache.

Wiping nvram is usually not needed. However when experiencing issues, it's one of the things that must be attempted. This is even more important with the FW build 354 as there has been some low-level changes to the wireless driver (and to some default settings associated to them).

My RT-AC66U wasn't wiped for months here and I didn't have any issue. I only recently wiped it due to an invalid nvram setting that accidentally got saved while testing something.

Asus doesn't have any fixed schedule. So far they often seem to release something about every 4-6 weeks, but it's not a set schedule - sometimes there are larger gaps between releases.

 

[rljames]

Wasn't using a Browser. noticed old SSID in Windows 8 "Networks" panel as wired connection linked to AC66.

Anyhow, I've downloaded your "RT-AC66U_3.0.0.4_354.27-BETA1" build, might as well move to this firmware if I'm going through the process again.

But, unless I missed something, the recommended method for clearing NVRAM still hasn't been given? And can this process cause problems if done wrong or out of order with the config reset?

I apologize for seemingly beating this thread issue to death with all the cautious questions but experimenting with this sort of thing isn't trivial for me and I don't want to find myself in more trouble.

Thanks to all who have offered help.