on ws-ap3915i htmode for 2ghz defaulted to VHT20 which is not available => how to configure HT20?

[dekarl]

the device logs an error when bringing up the wireless interface

kern.warn kernel: [ 1566.603533] ath10k_ahb a000000.wifi: wmi: fixing invalid VHT TX rate code 0xff

turns out, the htmode in /etc/config/wireless is VHT20, which is not supported on 802.11ac. manually setting it to HT20 fixes it. As small bandwidth and low transmit power on 2GHz is best practice it would be nice to be able to set it.

uci set wireless.radio0.htmode=HT20
uci commit wireless
wifi reload

btw, how do I set the regulatory domain, so 1-5-9-13 can be used later? (and indoor/outdoor operation per AP)

[rubenbe]

Both are not implemented yet because I didn't immediately find a nice/elegant way to do so.

• regulatory domain is kinda global for all radios, so one way would be to make it an environment variable. But then what if the user does not set it on a next run? Although writing this, I could make it a required one, similar to the secret.
• The VHT etc is tricky, since openwisp-monitoring does not report the available modes, so I cannot deduce what is allowed as settings (I could just allow everything, but still it is not super elegant either)

[dekarl]

I think storing some global configuration options would be useful.

E.g. store shared-secret, Url to set in client configuration to reach opensoho and now country. But mandatory environment variables work, too. (thinking about it. why not generate a random shared-secret and store it. Just keep the environment variable for migration / setting a specific secret. Also allows rotating the secret later without having to fiddle with the deployment)

Knowing the url enables to have a page in the controller with values to copy paste into the firmware builder for automated setup of new APs, as tested over in #1 (reply in thread)
(i had to set verify_ssl=0, too (my ACME provider is sunsetting the service... yet another thing to fix)

[rubenbe]

Added the country codes in v0.10.0