-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
luci-mod-network: wireless.js: implement method to set Operating Channel Validation #6957
Conversation
For full completeness you should run |
1cc68ad
to
3261157
Compare
Ok, now I've included a commit that updates the translation files. Thanks for the tip, @dannil! |
236b332
to
03023bb
Compare
03023bb
to
6b2bacf
Compare
modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
Outdated
Show resolved
Hide resolved
modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js
Show resolved
Hide resolved
e2a106d
to
38377a7
Compare
51cd534
to
6d50de0
Compare
@huaracheguarache could you rebase your changes please? |
Required for luci to check whether installed hostapd or wpa_supplicant is built with the Operating Channel Validation feature. Signed-off-by: Michael Yartys <mail@yartys.no>
Make it possible to set Operating Channel Validation through luci. Signed-off-by: Michael Yartys <mail@yartys.no>
Update translation files after adding option to set Operating Channel Validation. Signed-off-by: Michael Yartys <mail@yartys.no>
9ac439c
to
1a1b3a5
Compare
@systemcrash Ok, done! |
Setting Operating Channel Validation has long been possible in the wireless config file with the
ocv
parameter, and this pull request implements a method to set it in luci. It is done by adding a drop-down menu below the 802.11w settings in the wireless security tab as seen in the screenshot below:OCV can only be used in conjunction with 802.11w, so I've added a dependency check that makes sure that 802.11w is either set to optional or mandatory. The OCV setting has two enabled values, where one is a workaround mode that allows buggy clients to connect. This setting is only relevant in ap or ap-wds mode, so I've added a validator function that will warn the user if they've selected this option while in sta or sta-wds mode.
I've done some limited testing on my setup with an R7800 running in ap mode with WPA3-SAE+802.11r encryption. It's probably a good idea if more people could take this for a spin to make sure that it works properly. I've also added a commit that updates the associated translation files, as per @dannil's suggestion. I would appreciate any comments about the positioning of the drop-down menu, the text strings I've used etc.
Signed-off-by: <my@email.address>
row (viagit commit --signoff
)<package name>: title
first line subject for packages