40 mhz fall back to 20 MHz in 2.4 GHZ radio

hi all ,
i am using qcawifi and i am facing a issue that my channel width falls back to 20 MHz in 2.4 GHz radio when i set channel 2-10 , it works fine with channel 1 and 11 . what can be the issue and how to solve that..?

congestion ?

move.

If you live in a congested area, the wifi driver is expected to fall back from 40MHz to 20MHz. This is done to prevent interfering with other networks, because that would reduce the bandwidth for everyone.

There is an option to force the driver to stay at 40MHz, but using it is considered "out is specs".

But in my wifi analyzer there is no other ssid on the same or adjacent channels

Perhaps because of regulations in your country?

I do not have other answers... use the channels where it works, force it if you are sure it's safe, try other device,...

1 Like

Run survey from access point, it has much better antenna than your phone.

I changed in the source of qca-wifi package and it worked for now. I forcefully set it to 40 , so now it wont fallback to 20.

Thats not openwrt.

Its build upon openwrt.

It's built on a lie....

2 Likes

Why would i lie brother.?
Maybe i have misunderstood something.
But the device has the openwrt firmware, it even shows in etc/banner also.

Then please post output of ubus call system board.

	"kernel": "4.4.60",
	"hostname": "***********",
	"model": "*******",
	"release": {
		"distribution": "OpenWrt",
		"version": "Chaos Calmer",
		"revision": "0ea36ba+r49254",
		"codename": "chaos_calmer",
		"target": "ipq\/ipq807x_64",
		"description": "OpenWrt Chaos Calmer 15.05.1"
	}
}```

CC came with kernel 3.18.23, so you tell us. And why would you hide the model?

2 Likes

As it was pointed out by @brada4 ....


It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

4 Likes