What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Control Channel region missmatch

winterkiter

New Around Here
Hi there
I found a missmatch between the control channels (5Ghz) that are displayed in the gui and the channels that are actualy supported by the driver for my region
wl -i eth2 chanspecs

nvram get regulation_domain
wl -i eth2 country
Both produce the same output, for me CH, Switzerland.

although i can select for example 40/80 in the gui it is not applied and the router goes back to the default 36/20
wl -i eth2 chanspec 40/80 produces an error (bad channel)

changing my region to Q1
nvram set pci/2/1/ccode=Q1
nvram set wl1_country_code=Q1
nvram set regulation_domain_5G=Q1
nvram set pci/1/1/ccode=Q1
nvram set wl0_country_code=Q1
nvram set regulation_domain=Q1
nvram commit
reboot

-> wl -i eth2 country -> Q1
allows me then to succesfully select the 40/80 channel in the gui or with
wl -i eth2 chanspec 40/80.

I tested an RT-AC66N Router with the most common asus firmware as well as merlin.

I hope i could formulate my the issue clear enough. I found a workaround by setting the country to Q1, however for the future it would be nice to have this solved, does anyone have an idea where to start?
does wl -i eth2 chanspecs communicates with the driver directly (which is closed source ) or is this a part we can modify?

flavio
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top