Hostapd throwing warnings

[Bas Mevissen]

On 2020-10-15 19:45, Philip Prindeville wrote:
>> On Oct 15, 2020, at 11:32 AM, Daniel Golle <daniel at makrotopia.org> 
>> wrote:
>> 
>> On Thu, Oct 15, 2020 at 11:18:24AM -0600, Philip Prindeville wrote:
>>> Hi,
>>> 
>>> I have a WLE600VX card in an APU4 running HEAD as of a week ago.
>>> 
>>> My /etc/config/wireless file is straightforward:
>>> 
>>> config wifi-device 'radio0'
>>> 	option type 'mac80211'
>>> 	option channel '36'
>>> 	option hwmode '11a'
>>> 	option path 'pci0000:00/0000:00:02.5/0000:05:00.0'
>>> 	option htmode 'VHT80'
>>> 	option disabled '0'
>>> 
>>> config wifi-iface 'default_radio0'
>>> 	option device 'radio0'
>>> 	option network 'lan'
>>> 	option mode 'ap'
>>> 	option hidden '1'
>>> 	option ssid ‘xyzzy'
>>> 	option encryption 'psk2+aes'
>>> 	option key ‘my-passphrase-here’
>>> 
>>> But I’m seeing the following warnings:
>>> 
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Configuration file: 
>>> /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Line 16: unknown configuration item 
>>> 'ieee80211ac'
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Line 17: unknown configuration item 
>>> 'vht_oper_chwidth'
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Line 18: unknown configuration item 
>>> 'vht_oper_centr_freq_seg0_idx'
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Line 19: unknown configuration item 
>>> 'vht_capab'
>>> Oct 14 18:29:23 OpenWrt2 hostapd: 4 errors found in configuration 
>>> file '/var/run/hostapd-phy0.conf'
>>> Oct 14 18:29:23 OpenWrt2 hostapd: Failed to set up interface with 
>>> /var/run/hostapd-phy0.conf
>>> Oct 14 18:29:23 OpenWrt2 netifd: radio0 (4034): Command failed: 
>>> Invalid argument
>>> 
>>> 
>>> On booting.
>>> 
>>> If I comment out these lines being generated in 
>>> /lib/netifd/wireless/mac80211.sh then WiFi works.
>>> 
>>> Is anyone else seeing this?
>>> 
>>> I’m using:
>>> 
>>> CONFIG_PACKAGE_ath10k-firmware-qca988x-ct-full-htt=y
>>> CONFIG_PACKAGE_wireless-regdb=y
>>> CONFIG_PACKAGE_kmod-ath=y
>>> CONFIG_ATH_USER_REGD=y
>>> CONFIG_PACKAGE_ATH_DFS=y
>>> CONFIG_PACKAGE_kmod-ath10k-ct=y
>>> CONFIG_ATH10K-CT_LEDS=y
>>> CONFIG_PACKAGE_kmod-cfg80211=y
>>> CONFIG_PACKAGE_kmod-mac80211=y
>>> CONFIG_PACKAGE_MAC80211_DEBUGFS=y
>>> CONFIG_PACKAGE_MAC80211_MESH=y
>>> CONFIG_PACKAGE_hostapd-common=y
>>> CONFIG_PACKAGE_hostapd-openssl=y
>>> CONFIG_PACKAGE_hostapd-utils=y
>>> CONFIG_DRIVER_11N_SUPPORT=y
>>> CONFIG_DRIVER_11AC_SUPPORT=y
>>> CONFIG_DRIVER_11W_SUPPORT=y
>>> CONFIG_PACKAGE_iw=y
>>> 
>>> Am I doing anything wrong?
>>> 
>>> Oh, also, in /etc/config/network, do I need to explicitly add wlan0 
>>> to my bridge for “lan” or does that happen automatically?
>> 
>> Looks like CONFIG_DRIVER_11AC_SUPPORT=y isn't really set in the end,
>> usually it should be auto-selected based on the driver you are using,
>> ie. kmod-ath10k in your case. Those CONFIG_DRVIVER_* symbols are not
>> meant to be selected manually.
>> Are you using an out-of-tree WiFi driver or any changes like that?
> 
> 
> I commented out CONFIG_DRIVER_* and reran “make defconfig oldconfig”
> and those 3 got turned back on.
> 
> Is there something else I should be doing?
> 

You might check whether the text strings of the configuration options 
mentioned in the logs are present in the binaries in the rootfs and 
object files in the build folder (assuming they are literally present in 
the source code). Additionally, add some #error statements in a few 
places in code that only gets compiled when CONFIG_DRIVER_11AC_SUPPORT 
is defined to check whether that define is effectively set at compile 
time.

It is a very basic way of debugging source code configuration, but at 
least it gives you certainty about how the code is actually compiled.


> And no, not an out-of-tree build… unless it’s using backports and
> that’s considered out-of-tree?
> 
> -Philip
> 
> 
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel